Publishing a multi-architecture Docker image for the Eventuate CDC service

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:

About the Eventuate CDC project

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.

Changing the project’s CircleCI pipeline

I modified the project’s deployment pipeline to follow that the same four step pattern that I used for Eventuate Common:

  1. Build a multi-architecture Eventuate CDC image locally (using a registry container), and test the container it on both Intel and Arm.
  2. Build a multi-architecture Eventuate CDC image and push it to Docker Hub with a test-build-* tag
  3. Test the multi-architecture test-build-* Eventuate CDC image on both Intel and Arm.
  4. Create a manifest in Docker Hub with the desired tag

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.

Viewing the changes

To see the changes I made to the eventuate-cdc project, take a look at this Github commit.

Using the image

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.



Copyright © 2023 Chris Richardson • All rights reserved • Supported by Kong.

About Microservices.io

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.

Learn how to create a service template and microservice chassis

Take a look at my Manning LiveProject that teaches you how to develop a service template and microservice chassis.

New virtual bootcamp: Distributed data patterns in a microservice architecture

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 JUNVCEJE to sign up for $195 (valid until February 1st, 2023). There are deeper discounts for buying multiple seats.

Learn more

Signup for the newsletter


LEARN about microservices

Chris offers numerous resources for learning the microservice architecture.

Training classes

Chris teaches comprehensive workshops, training classes and bootcamps for executives, architects and developers to help 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.

Delivered in-person and remotely.


Get the book: Microservices Patterns

Read Chris Richardson's book:

Example microservices applications

Want to see an example? Check out Chris Richardson's example applications. See code

BUILD microservices

Ready to start using the microservice architecture?

Consulting services

Engage Chris to create a microservices adoption roadmap and help you define your microservice architecture,


The Eventuate platform

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.

ASSESS your architecture

Assess your application's microservice architecture and identify what needs to be improved.

Consulting services

Engage Chris to conduct an architectural assessment.



Join the microservices google group

Topics

Note: tagging is work-in-process

anti-patterns   ·  application api   ·  application architecture   ·  architecting   ·  architecture documentation   ·  dark energy and dark matter   ·  deployment   ·  development   ·  devops   ·  docker   ·  implementing commands   ·  implementing queries   ·  inter-service communication   ·  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   ·  team topologies   ·  transaction management   ·  transactional messaging

All content


Posts

24 Jul 2017 » Revised data patterns