Because there's not predefined architecture that you can apply directly to your projects, choosing an architecture for your system can prove very difficult.
You've got three ways. The first one is the standard one following docker-compose conventions. The other ones can be used for defining reusable pieces for your tests.
See an overview of an application that can be tuned with Akka, the load tests and tools that can be used to measure app performance, and some test results.
We link Docker containers with each other to enable communication between them or to be sure that all of the tools and microservices are running on the same machine.
If you’re using Docker, the combination of Prometheus and Grafana offers an extremely enticing option to explore for reasons of ease of use and functionality.
Clean Architecture gives a clear No! to mixing frameworks and business rules. But that doesn't mean we have to resign from all cool technologies. We just have to adapt.
Clustering and high availability configuration with RabbitMQ are pretty simple. Its UI management console offers good s support in the cluster monitoring process.
I'm positively surprised by Apache Camel. Before I started working on this example, I didn’t expect it to have so many features for microservice solutions.
Data, Context, and Interaction — the way to move your object-orientation to the next level. Unfortunately, there's no good way to implement it in Java yet.
