Microservices Chain Pattern
These days lightsweight containers like Docker are getting traction, as more and more API services are developed for docker containers and deployed to the cloud. In this environment, traditional heavy weight containers like Java EE and Spring are losing ground as it doesn’t make sense to have a heavy weight container wrapped with a light weight docker container. Docker and container orchestration tools like Kubernetes and Docker Swarm are replacing all the functionalities Java EE provides without hogging resources.
There is an article published by Gartner indicates that both Java EE and .NET are declining and will be replaced very soon.
Another clear trend is standalone Gateway is phasing out in the cloud environment with docker containers as most of the traditional gateway features are replaced by container orchestration tool and docker container management tools. In addition, some of the cross cutting concerns gateway provided are addressed in API frameworks like light-4j and related light*4j frameworks.
This tutorial shows you how to build 4 services chained together one by one. And it will be the foundation for our microservices benchmarks.
API A -> API B -> API C -> API D
It is a very long tutorial as we want to package as much info as possible. So we have separated it into the following steps.