In this blog I will explain how you can migrate Java applications from a monolithic application that is deployed directly onto instances with no containerization or orchestration, to a containerized and orchestrated microservices architecture.
Being able to ship the exact the same container through all four stages of the process makes delivering a high quality, reliable application considerably easier.
The EC2 Container Service provides orchestration for your containers. It automates the process of launching containers across your fleet of instances according to rules you specify. It then automates keeping track of where those containers are running, so that you can use a load balancer to get traffic to them. It also has built in features to roll out deploys with zero downtime, gather metrics and logs from your containers, and auto scale the number of containers you are running based on metrics.
The below image, published by Amazon Web Services, provides a concise overview of the setup for Amazon ECS.
This graphic provides an overview of the container deployment on EC2.
In the case of separate modules, I recommend simply:
Moving from having monolithic apps to microservices have significant benefits, both for developers and the business. As I mentioned earlier, being able to ship the exact same container every time, means you can much more easily and reliably deliver a high quality application.
October 10 / 2019
October 03 / 2019
November 19 / 2014
In light of some of the major changes occurring at the moment within Microsoft, the forthcoming release of Visual Studio 2015, along with .NET 2015, promises to be particularly...Read post