Point-to-Point Messaging Architecture - The Reactive Endgame

October 4, 2018
What's next after Microservices Architecture? Can we do better than "WebHooks" over HTTP? Should distributed systems grow more complex every year? Can we start thinking beyond Cloud Computing? A majority of modern distributed softwares is built on the assumption that HTTP is the [only] standard communication protocol. The implications are deep as entire solutions standardize around HTTP including service meshes or messaging with gRPC over H2. Efficient systems also make use of a message broker such as Kafka, RabbitMQ or SQS to enable data distribution, streaming and event-driven architectures. Sadly, there is a hard semantic boundary between HTTP and these messaging solutions. The primary consequence is an uncontrolled request backlog, usually mitigated by a strong Observability story in the platform to assist elastic scaling. In this session, we will try to explore those many questions and will provide our R&D perspective on the future of distributed systems. Speakers: Ryland Degnan Co-founder and CTO, Netifi Stephane Maldini Reactive Engineering Cook, Pivotal Filmed at SpringOne Platform 2018
Previous
Knative and riff for Spring Developers
Knative and riff for Spring Developers

From Java function source to running pod in 5 minutes ... Simplifying the work for the developer building ...

Next Video
Springing into Kotlin: How to Make the Magic Even More Magical
Springing into Kotlin: How to Make the Magic Even More Magical

Slides: https://www.slideshare.net/SpringCentral/springing-into-kotlin-how-to-make-the-magic-even-more-magi...

Enter curious. Exit smarter.

Learn More