multi-architecture docker images   docker  

Building a multi-architecture Docker image for Apache Kafka

In the previous post, I described how I configured the CircleCI pipeline for the Eventuate Common project to build test and publish MySQL8 and Zookeeper Docker images In this post, I cover how I changed the eventuate-messaging-kafka project to publish a multi-architecture Apache Kafka image needed by the Eventuate Tram Customers and Orders example.

The other articles in this series are:

Why build a multi-architecture Apache Kafka image?

Eventuate Tram Customers and Orders, like the other Eventuate examples, uses the Confluent Platform Kafka image. Surprisingly, this is an Intel-only image, so I needed to build my own a multi-architecture image. But which Eventuate project should do this?

Changing the eventuate-messaging-kafka project to publish an Apache Kafka image

I decided that it made sense for the eventuate-messaging-kafka project to build the and publish the Apache Kafka Docker image . It’s a Gradle project that defines the Apache Kafka implementations of the Eventuate consumer and producers. Its tests need to run Apache Kafka and they currently use the Confluent Platform Kafka image. By changing this project to build the Apache Kafka image, I can reuse those tests to validate the image.

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 Apache Kafka image locally (using a registry container), and run the Java tests on both Intel and Arm.
  2. Build a multi-architecture Apache Kafka image and push it to Docker Hub with a test-build-* tag
  3. Test the multi-architecture test-build-* image on both Intel and Arm.
  4. Create a manifest in Docker Hub with the desired tag

Viewing the changes

To see the changes I made to the project, take a look at this Github commit and a bug fix commit

Next steps

In the next article, I’ll describe the changes that I made to the eventuate-examples-docker-images project, which publishes the base Docker images for the services in the example applications.


multi-architecture docker images   docker  


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.

MICROSERVICES 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

LEARN about microservices

Chris offers numerous other resources for learning the microservice architecture.

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

Remote consulting session

Got a specific microservice architecture-related question? For example:

  • Wondering whether your organization should adopt microservices?
  • Want to know how to migrate your monolith to microservices?
  • Facing a tricky microservice architecture design problem?

Consider signing up for a two hour, highly focussed, consulting session.

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 MECNPWNR to sign up for $120 (valid until May 16th, 2023). There are deeper discounts for buying multiple seats.

Learn more

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.

Signup for the newsletter


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   ·  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

All content


Posts

24 Jul 2017 » Revised data patterns