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

Voxxed Days Microservices: Data Dichotomy

DZone's Guide to

Voxxed Days Microservices: Data Dichotomy

A Confluent engineer talks about handling data in a loosely-coupled, service-based system.

· Microservices Zone ·
Free Resource

Learn why microservices are breaking traditional APM tools that were built for monoliths.

Hi Damien, tell us who you are and what lead you into microservices.

Hi there! I am an engineer and an open-source enthusiast working for Confluent, the company founded by the creators of Apache Kafka. In the past couple of years, I have worked closely with clients of all shapes and sizes — from small startups to Tier 1 banks — on various topics such as designing event sourcing systems and data integration.

I believe that event sourcing and microservices are a good that helps to deal with the growing complexity of software development. I expect that this approach will become a standard in the future. Furthermore, playing Lego with containers is really funny!

What will you be talking about at Voxxed Days Microservices?

I will be talking about one of my favorite topic: how to handle data in a loosely coupled service-based system. While designing microservices, we are taught to encapsulate and decouple one service from another so they can continue to change and grow independently. But on the other side, we still need to manipulate a shared dataset, so we find ourselves faced with a contradiction. A dichotomy: data systems are all about making data available. Services are about hiding it.

In this talk, I will discuss the benefits of an immutable changelog of state and why this approach provides most of the benefits of a data warehouse without the inconvenience of centralization.

We have data on one side, and services on the other side. And now we have streams in the middle. How does all this work together?

A stream of data is an immutable sequence of state, a bus of data that can be accessed by everyone. This is a convenient structure allowing share state between services: each service is in charge of manipulating its local view of the shared data, making it easy to iterate quickly, yet the immutable stream of state is available as a common source of facts. This approach balance the data dichotomy mentioned previously.

Good, see you soon, then.

See you soon!

Voxxed Days Microservices and DZone, Partnering Up

DZoners! Visit Voxxed Days Microservices here to check out ticket info for the show, and use the DZone reader exclusive code: VXDMS_DZONE to get 20% off for the conference and workshop. Grab those tickets while you can, be sure to say hey to our Zone Leaders—Thomas Jardinet and Chris Ward—if you run into them at the show, and enjoy Paris!

Record growth in microservices is disrupting the operational landscape. Read the Global Microservices Trends report to learn more.

Topics:
microservices ,data ,distributed systems ,software architecture

Published at DZone with permission of

Opinions expressed by DZone contributors are their own.

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

{{ parent.tldr }}

{{ parent.urlSource.name }}