Building, testing, containerizing, deploying, and monitoring distributed microservices is difficult, but using Lightbend technologies can make it a lot faster and easier to be successful. In this four part blog series, we walk you through a working Proof of Concept (PoC) built using Lightbend’s open source distributed toolkit, Akka. This PoC delivers a resilient, highly performant, elastic, distributed, and consistent state solution that provides an automatic in memory cache with a persistent backing. Here is the breakdown:
- Part 1 - Getting Started: we walk through building, testing, and running the PoC locally, with instrumentation and monitoring wired in from the very beginning using Lightbend Telemetry.
- Part 2 - Docker and Local Deploy: here we cover containerizing our PoC, and then deploying locally in Docker. Then, we’ll load test and monitor our PoC as we did in the first installment.
- Part 3 - Kubernetes and Monitoring: in this part,we introduce Lightbend Console for Kubernetes (K8s), and then deploy our PoC in Minikube (desktop version of K8s) using YAML files provided in this repository. Again, we’ll load test with Gatling, but this time we’ll monitor our PoC in Lightbend Console.
- Part 4 - Source Code: In our final installment, we do a deep dive into our Scala source code.
- Move to Java 21
- upgrade all Akka Dependencies to release v24.05.3
- upgrade Gatling to v3.12.0, and rewrite as Java from Scala
- fixed bug in Gatling scenario
- migrate docker-compose & nonsup-docker-compose to use Akka Cluster Bootstrap w/ DNS instead of using Seed nodes for Akka Cluster formation.
- fixed NPE bug in client/ArtifactStateForEach example.
- made sure that Maven can properly create docker images with "mvn clean compile package docker:build"
- created a nonsup.pom.xml for those that don't have a Lightbend Subscription and thus access to commercial options such as Lightbend Telemetry.
- added missing POM dependency for cluster bootstrap on K8s
- added JAVA_TOOL_OPTIONS to Microk8s deployments to accommodate difference when passing environment variables with Maven / Fabric8 to the container.
- created a new branch (mread-multi-dc-common-journal), which supports Akka's Replicated Event Sourcing "Common Journal" running on Multi-Data Center / Microk8s and Yugabyte. README.md can be found here.
- update Akka related dependencies to latest
- Learned that
sbtuses the env variableJAVA_OPTSto pass configs to Java whereas Maven w/ Fabric8 usesJAVA_TOOL_OPTIONS.
- Moved to Java 17: converted Actor Protocols and Events to Records
- Akka DNS cluster formation on Docker w/ Yugabyte. Doc here.
- Complete multi-node testing: integration tests for cluster formation, and gRPC, and http endpoints running under Maven.
- Upgrade Akka, Akka Http, and Akka gRPC to latest.
- multi-node testing defaults to Cassandra, but commenting change be changed to use Yugabyte instead.
- This repository is the Java version of the original Scala version found here.
- Testing Lightbend's Akka Persistence Plugin for R2DBC.
mvn clean akka-grpc:generate
docker compose -f docker-compose-cassandra.yml up
mvn compile exec:exec -Dapp.configfile="cluster-application.conf"
mvn exec:exec -Dapp.configfile="endpoint-application.conf"
docker compose -f docker compose-yugabyte.yml up
docker exec -i yb-tserver-n1 /home/yugabyte/bin/ysqlsh -h yb-tserver-n1 -t < https://raw.githubusercontent.com/akka/akka-persistence-r2dbc/main/ddl-scripts/create_tables_yugabyte.sql
mvn compile exec:exec -Dapp.configfile="cluster-application-yugabyte.conf"
mvn exec:exec -Dapp.configfile="endpoint-application.conf"
- Start Cassandra first (above)
- Start the test
mvn test