Reactive Summit 2016 Conference: Reactive Microservices and Staging Data Pipelines

| by Srini Penchikala Follow 22 Followers on Oct 08, 2016. Estimated reading time: 2 minutes |

A note to our readers: You asked so we have developed a set of features that allow you to reduce the noise: you can get email and web notifications for topics you are interested in. Learn more about our new features.

Reactive microservices, data center scale operating system (DCOS), and staging reactive data pipelines were the highlighted topics at the Reactive Summit 2016 Conference held this week.

Jonas Boner, co-founder and CTO of Lightbend and author of the Reactive Microservices Architecture report, gave the keynote presentation at the conference.

He cited Gartner’s report saying that traditional application architectures and platforms are obsolete. Microservices architecture, defined as a system of autonomous collaborative distributed services, is the core part of the new architecture model. Distributed systems is the architectural context of microservices which calls for a different way of developing and deploying the applications. Some of the guidelines are: isolate all the things, use bulkheading and go asynchronous.

Asynchronous communication allows decoupling in space and time and this model embraces the constraints of distributed systems.

The microservices should be designed in such a way that they own the state exclusively because managing the state is a crucial part of microservices design. Boner said there is no such thing as a "stateless" architecture; it's just someone else's problem. Developers need to think in terms of consistency boundaries and Bounded Contexts. He also talked about other patterns like Event Sourcing and CQRS.

Reactive microservices should also be mobile but addressable. Virtual addressing helps with Load-balancing between stateless services, state replication of stateful services and relocation of a stateful service.

Microservices come in systems so we should strive to minimize coupling and communication. We have to rely on eventual consistency, but don't be surprised, it's how the world works.

He suggested developers to consider using microservices patterns like API Gateway and Circuit Breakers and always apply back-pressure in the design because a fast system should not overload a slow system.

In another keynote presentation, Edward Hsu, VP of Enterprise DC/OS at Mesosphere, spoke about developing modern applications with containers and microservices technologies. Mesosphere’s community and enterprise versions of the data center operating system (DC/OS). He discussed the case study of ESRI using this solution for geo-spatial data analytics purposes.

Helena Edelson also spoke at the conference about reactive distributed systems for streaming big data, analytics and machine learning. She said that being reactive in distributed systems is critical and discussed how we can build resilient, scalable systems that can learn from system failures and errors. She described the architecture where the failure context is routed to a message topic to process through the machine learning streams. Developers should bake fault tolerance and error handling strategies and route awareness into every application and node in the cluster. Helena also talked about adaptive load balancing and cluster metrics API.

Jaakko Pallari and Simon Souter from Cake Solutions spoke about the staging reactive data pipelines. Staged reactive data pipelines based on the Staged EDA (SEDA) architecture where the processes are separated by queues and the processing is done in stages. Microservices are used as the processing components and the messaging middleware can help with resilient data distribution between microservices. This model, with Apache Kafka as the backbone, gives the basic architecture to perform distributed data pipelines.


Rate this Article

Adoption Stage

Hello stranger!

You need to Register an InfoQ account or or login to post comments. But there's so much more behind being registered.

Get the most out of the InfoQ experience.

Tell us what you think

Allowed html: a,b,br,blockquote,i,li,pre,u,ul,p

Email me replies to any of my messages in this thread
Community comments

Allowed html: a,b,br,blockquote,i,li,pre,u,ul,p

Email me replies to any of my messages in this thread

Allowed html: a,b,br,blockquote,i,li,pre,u,ul,p

Email me replies to any of my messages in this thread


Login to InfoQ to interact with what matters most to you.

Recover your password...


Follow your favorite topics and editors

Quick overview of most important highlights in the industry and on the site.


More signal, less noise

Build your own feed by choosing topics you want to read about and editors you want to hear from.


Stay up-to-date

Set up your notifications and don't miss out on content that matters to you