We are R\u00e9gina ten Bruggencate and Linda van der Pal both Java developers at Trailblazers and Java Champions. We attend and speak at a lot of conferences and heard a lot about microservices, but most of the talks were about framework X or Y and how they would allow you to build microservices lightning fast. This got us to wondering how we could split up our big old monoliths. Linda attended a workshop at the XPdays Benelux by Koen Metsu and Erik Talboom. It was a lovely workshop with a great concept, but it didn’t quite go into the level of details she had hoped for. Since the best way to learn is to teach, she asked their permission to use their idea and work it into a workshop of her own. R\u00e9gina liked the idea too, and so we set out together to submit the workshop to a couple of conferences.<\/p>\n
My name is Gunnar Morling; I\u2019m a software engineer working at Red Hat, where I\u2019m leading the Debezium<\/a> project. Debezium is a platform for change data capture (CDC), allowing you to react to all the changes in your database in near real-time. CDC is not only very useful for use cases like replication or updating full-text search indexes, but also comes in handy for microservice architectures where it for instance can be used to propagate data between different services.<\/p>\n I\u2019m Emmanuel Bernard and am a Hibernate contributor, Java Champion and Chief Architect, Data at Red Hat middleware. I\u2019ve always been involved in improving how to process data from within applications. With microservices, the challenge is more complex because it involves inter system data communication. Even more fun.<\/p>\n During the first half of the workshop we will talk about actually splitting up a real life problem and how you accomplish that. We will give a brief introduction into Domain Driven Design and how you can use that to track down the borders along which you can split your problem. After that we will split up into pairs and get cracking. We will start by looking at a real world problem, and then we\u2019ll have a brainstorm session to determine what could be the microservices. Then we split up the group into pairs and will start coding. The participants can use whatever framework they like to build a microservice.<\/p>\n Of course different microservices don\u2019t exist in isolation, very often they\u2019ll have to exchange data. That\u2019s an interesting challenge, esp. as you\u2019d like to avoid a tight coupling between services and make sure you don\u2019t create a \u201cdistributed monolith\u201d. This is what we\u2019ll deal with in the second part of the workshop: attendees will learn how microservices can produce and consume data streams using tools such as Kafka, Debezium and Kubernetes. They\u2019ll also learn how easy it is to set up streams with the changes from a database, without any application changes needed. This all helps with creating loosely coupled microservices. We\u2019ve also planned to discuss some operational aspects such as setting up Kafka on Kubernetes\/OpenShift using the Strimzi project, monitoring etc.<\/p>\n People should leave the workshop with a solid understanding of how DDD can be used to model microservices and define their boundaries and how streaming-based communication approaches can help different microservices to cross these boundaries.<\/p>\n Indeed, using a single database for multiple services is something we\u2019d usually not recommend, as it\u2019ll create a tighter coupling between services than desirable. E.g. a database upgrade could impact multiple services instead of just a single one, giving away one of the advantages of microservice architectures.<\/p>\n Thanks a lot! We\u2019re very happy to be part of the first VoxxedDays Microservices and look forward very much to the conference and our workshop. See you in Paris!<\/p>\n #DDD #SplittingMonoliths #DataStreaming #Debezium<\/strong><\/p>\n Twitter: @reginatb38<\/a> Twitter: @DuchessFounder<\/a> Twitter: @gunnarmorling<\/a> Twitter: @emmanuelbernard<\/a> Hi all, tell us who you are and what lead you into microservices? We are R\u00e9gina ten Bruggencate and Linda van der Pal both Java developers at Trailblazers and Java Champions. We attend and speak at a lot of conferences and heard a lot about microservices, but most of the talks were about framework X […]<\/p>\n","protected":false},"author":1301,"featured_media":1373,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":[],"categories":[12],"tags":[23,26,57,56],"acf":[],"yoast_head":"\nDuring this one day workshop, what should the attendees expect? What would they learn?<\/h3>\n
So people come to your workshop, create teams, model microservices, implement them, and deal with data synchronization? So will they come out convinced that having a single database for all microservices is bad?<\/h3>\n
Sounds good, see you soon then<\/h3>\n
\nLinkedIn: https:\/\/www.linkedin.com\/in\/reginatb<\/a><\/p>\n
\nLinkedIn: https:\/\/www.linkedin.com\/in\/lvdpal<\/a><\/p>\n
\nBlog: http:\/\/in.relation.to\/gunnar-morling<\/a>
\nGitHub: http:\/\/github.com\/gunnarmorling<\/a><\/p>\n
\nBlog: https:\/\/emmanuelbernard.com<\/a>
\nLinkedIn: https:\/\/fr.linkedin.com\/in\/emmanuelbernard<\/a>
\nGitHub: http:\/\/github.com\/emmanuelbernard<\/a><\/p>\nCheck the other workshops<\/a><\/h3>\n","protected":false},"excerpt":{"rendered":"