multi-architecture docker images   docker  

Developing the Eventuate Common library on an M1/Arm MacBook

After enhancing the microservicesio/plantuml project to publish a multi-architecture Docker image for Intel and Arm, I moved on to the eventuate-common project. It’s a Gradle project that publishes some foundational Java libraries and some Eventuate-flavored Docker images for Zookeeper, MySQL, Postgres and SQL server. These libraries and images are used by the Eventuate examples including the Tram Customers and Orders example application I described in my first post on this topic.

This post describes my experiences developing Eventuate Common on my M1/Arm MacBook. Specifically, I describe how I was able to build a MySQL image and run the related tests. Later posts describe how I changed this project to build and publish multi-architecture images.

The other articles in this series are:

Gradle behaves differently!

After running git clone on my M1 MacBook, I ran ./gradlew testClasses. As I described in this Twitter thread, I immediately encountered a Gradle issue that broke the build. A plugin from the eventuate-plugins-gradle project that ran a Git command failed to determine the current branch. Surprisingly, the command’s current working directory was no longer a project directory. Instead, it was some internal Gradle daemon directory. This could very well be a bug in the plugin rather than a Gradle issue. I fixed the problem by explicitly specifying the project.rootDir: e.g. git -C ${project.rootDir} rev-parse --abbrev-ref HEAD.

Later on while running the tests, I encountered another problem that was also related to the Gradle daemon. Gradle appeared to not always pass environment variables from the shell to the Gradle daemon. This behavior caused Docker containers to be incorrectly configured and/or tests to fail. I eventually solved the problem by replacing environment variables with Gradle projects properties that are specified on the command: ./gradlew ... -P x=y. Not only did eliminating environment variables fix this problem, but it improved the Gradle build logic since Gradle could now track changes to the project properties.

Finding a MySQL image that runs on Arm

As I mentioned above, the Eventuate Common project builds various database images that contain the Eventuate schema. I decided to first work on supporting MySQL on ARM. The project builds MySql 5 and MySql 8 Docker image using the mysql:5.7.13 and mysql:8.0.22 base images. These base images are Intel specific and so I needed to find multi-architecture replacements.

When I searched Docker Hub, I found the mysql/mysql-server image. The MySql 5 tags are still Intel-specific but the MySql 8 tags support both Arm and Intel. I decided, therefore, to focus on enhancing the Eventuate Common to run MySQL 8 on Arm.

Building the Eventuate MySQL 8 image

The mysql/mysql-server:8.0.27-1.2.6-server is generally a drop in replacement for mysql:8.0.22. The notable difference is that by default, root access is limited to localhost. In Eventuate applications, other containers, such as the Eventuate CDC, need root access. This behavior is overridden by the MYSQL_ROOT_HOST environment variable but I didn’t want to add that setting to every Eventuate example. Therefore, I changed Dockerfile-mysql8 to run an additional configuration script - 0.configure-root-user.sh - that allowed root access from anywhere.

Building a Zookeeper image for Arm

This project also builds a Zookeeper image. It used the Intel-specific java:openjdk-8u91-jdk as the base image. I changed the Dockerfile to use the multi-architecture amazoncorretto:17.0.1-al2 image.

Running the tests

Once I’d made these changes, I was able to run build-and-test-all-mysql8.sh, which builds and starts the Zookeeper and MySQL 8 images and runs the tests. I also updated my local copy of the Eventuate Tram Customers and Orders example application to use these images. As expected, the MySQL and Zookeeper containers ran without a problem. However, most of the containers images were either flakey or slow. There’s still more work to do.

Viewing the changes

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

Next steps

The next post describes how I changed this project to build multi-architecture images.


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.

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