Over a million developers have joined DZone.
{{announcement.body}}
{{announcement.title}}

SpringOne Platform 2016 Replay: Reactive Kafka [Video]

DZone's Guide to

SpringOne Platform 2016 Replay: Reactive Kafka [Video]

Merging Reactive Streams with Apache Kafka can help you simplify the process of building asynchronous systems while incorporating microservices.

· Java Zone ·
Free Resource

Build vs Buy a Data Quality Solution: Which is Best for You? Gain insights on a hybrid approach. Download white paper now!

Apache Kafka is a distributed, scalable, high-throughput messaging bus. Over the last few years, Kafka has emerged as a key building block for data-intensive distributed applications. As a high-performance message bus, Kafka enables the development of distributed applications using the microservices architecture.

Reactive Streams simplifies the development of asynchronous systems using non-blocking back pressure. The reactive framework enables the development of asynchronous microservices by providing a side-effect free functional API with minimal overhead that supports low latency, non-blocking end-to-end data flows.

After an introduction to Kafka and reactive streams, we will explore the development of a Reactive Streams interface for Kafka and the use of this interface for building robust applications using the microservices architecture.

Recorded at SpringOne Platform 2016.

Speaker: Rajini Sivaram

Slides: http://www.slideshare.net/SpringCentral/reactive-kafka

Build vs Buy a Data Quality Solution: Which is Best for You? Maintaining high quality data is essential for operational efficiency, meaningful analytics and good long-term customer relationships. But, when dealing with multiple sources of data, data quality becomes complex, so you need to know when you should build a custom data quality tools effort over canned solutions. Download our whitepaper for more insights into a hybrid approach.

Topics:
kafka ,java ,reactive programming ,microservices

Published at DZone with permission of

Opinions expressed by DZone contributors are their own.

{{ parent.title || parent.header.title}}

{{ parent.tldr }}

{{ parent.urlSource.name }}