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.
Although ''microservices'' might seem like a buzzword, I suggest taking advantage of the modernized techniques that the microservices movement is generating.
Uncle Bob's Clean Architecture keeps your application flexible, testable, and highlights its use cases. But there is a cost: No idiomatic framework usage!
Spring Boot and Swagger 2 play together very well. Just add the dependencies, one configuration file, and a bunch of annotations, and you're ready to go!
With cloud-native microservices, you can develop, test, deploy, and maintain independent lightweight services while combining various other technologies.
CORE
