The Eventuate CDC Service is a key part of the Eventuate Platform.
It plays the role of a Message Relay in the Transaction Outbox pattern.
It reads messages that are inserted in an
OUTBOX table and sends them to the message broker.
It also reads inserted into an
EVENTS table, which is part of Eventuate’s Event Sourcing implementation, and publishes them to Apache Kafka.
The Eventuate CDC service is a Spring Boot application that’s packaged as a Docker image.
This post describes how I changed the Eventuate CDC project to publish a multi-architecture Docker image.
The other articles in this series are:
The Eventuate CDC service supports multiple databases (MySQL 5, MySQL 8, Postgres, and MS SQL) and multiple message brokers (Apache Kafka, ActiveMQ, RabbitMQ and Redis). What’s more, for some databases, the CDC service supports both the Transaction log tailing and Polling publisher patterns.
In order to test all these variations, the project has a complex CircleCI deployment pipeline. The pipeline consists of two main sets of jobs. The first set of jobs test the various CDC modules with different databases and message brokers. The second set of jobs that build the CDC’s Docker image and test it with different databases and message brokers.
I modified the project’s deployment pipeline to follow that the same four step pattern that I used for Eventuate Common:
test-build-*Eventuate CDC image on both Intel and Arm.
It’s important to note, however, that the pipeline only tests the multi-architecture image against MySQL 8 in order to minimize its execution time. Moreover, the pipeline jobs that run on an Arm machine only test against MySQL 8 and Apache Kafka because the project uses Intel-specific images for the other databases and message brokers.
To see the changes I made to the
eventuate-cdc project, take a look at this Github commit.
Once the project’s CircleCI pipeline was successfully publishing the multi-architecture image, I changed the Eventuate Tram Customers and Orders example application to use it. After making this change, my Apple M1 MacBook was able to successfully run the application’s tests. It can finally be used for development.
Microservices.io is brought to you by Chris Richardson. Experienced software architect, author of POJOs in Action, the creator of the original CloudFoundry.com, and the author of Microservices patterns.
Chris helps clients around the world adopt the microservice architecture through consulting engagements, and training workshops.
Chris teaches comprehensive workshops for architects and developers that will enable your organization use microservices effectively.
Avoid the pitfalls of adopting microservices and learn essential topics, such as service decomposition and design and how to refactor a monolith to microservices.Learn more
Chris offers numerous other resources for learning the microservice architecture.
Want to see an example? Check out Chris Richardson's example applications. See code
Got a specific microservice architecture-related question? For example:
Consider signing up for a two hour, highly focussed, consulting session.
My virtual bootcamp, distributed data patterns in a microservice architecture, is now open for enrollment!
It covers the key distributed data management patterns including Saga, API Composition, and CQRS.
It consists of video lectures, code labs, and a weekly ask-me-anything video conference repeated in multiple timezones.
The regular price is $395/person but use coupon MECNPWNR to sign up for $120 (valid until May 16th, 2023). There are deeper discounts for buying multiple seats.
Take a look at my Manning LiveProject that teaches you how to develop a service template and microservice chassis.
Engage Chris to create a microservices adoption roadmap and help you define your microservice architecture,
Use the Eventuate.io platform to tackle distributed data management challenges in your microservices architecture.
Eventuate is Chris's latest startup. It makes it easy to use the Saga pattern to manage transactions and the CQRS pattern to implement queries.
Engage Chris to conduct an architectural assessment.
Note: tagging is work-in-process
anti-patterns · application api · application architecture · architecting · architecture documentation · assemblage · beer · containers · dark energy and dark matter · deployment · design-time coupling · development · devops · docker · eventuate platform · glossary · hexagonal architecture · implementing commands · implementing queries · inter-service communication · kubernetes · loose coupling · microservice architecture · microservice chassis · microservices adoption · microservicesio updates · multi-architecture docker images · observability · pattern · refactoring to microservices · resilience · sagas · security · service api · service collaboration · service design · service discovery · service granularity · service template · software delivery metrics · success triangle · tacos · team topologies · transaction management · transactional messaging