Data in a Microservices world: from conundrum to options by Emmanuel Bernard, Madou Coulibaly

Microservices are great, problems arise when you start to have two of them and when you want to deal with data :)

Pun aside, data and state is a big subject that is largely ignored when discussing Microservices.

Conundrum #1 : What is the aimed data architecture in a perfect Microservices architecture?
Conundrum #2 : How do you share state between instances of a given Microservice in a stateless 12 factor approach?
Conundrum #3 : how to echange state between Microservices that must remain independent?
Conundrum #4 : how do I go from my brownfield database to a fleet of Microservices IRL without a Big Bang? Conundrum #5 : with many Microservices touching many data sets, how do I guarantee uniformed security (GDPR anyone)?
And the list goes on. This presentation is an opinionated answer to these questions. And yes we do demo these concepts.

Emmanuel Bernard
From Red Hat
Emmanuel Bernard is Chief Architect, Data at Red Hat. He oversees how data and middleware interact and is involved in open source communities like Hibernate, Infinispan, Teiid, Debezium (Change Data Capture) and more. To sum up, everything data :) He is a Java Champion and a Java Community Process expert group member (JPA) and former spec lead (Bean Validation). He co-hosts two podcasts Les Cast Codeurs and JBoss Community Asylum.

You can follow him on twitter at @emmanuelbernard.

Madou Coulibaly
From Red Hat
Hello, my name is Madou Coulibaly and I am a EMEA Specialist Solution Architect at Red Hat since 2016 with a strong focus on Data. With 8+ years experience in Data & information management (BI, DW, Big Data, …), I am now working with customers across EMEA for providing expertise, guidance and knowledge about these Data products. Microservices is a new journey Data has to embark on with the big challenge to “live” in a distributed and complex environment. So to help it, Data brings me into this new adventure.

[Gaurjain]

Hmmm... what about one database per service principle, isn’t data virtualization along with the monolith breaking that principle from the get go. Please clarify if the monolith app has write permission over the monolith dB

[Gaurjain]

How about isolation in space ...another broken principle of microservices