This video would focus on building the microservices with the containers. Mr. Anup Gupta, the principal open-source technologist, Amazon Web Services would brief on the concept of building the microservices with the containers.
At 2:40, Mr. Anup briefs on the idea of two-pizza teams that are followed at Amazon which would eventually result in full ownership, accountability, DevOps and also focussed innovation. At 4:25, the disadvantages of having a monolithic architecture is listed. Some of them include coordination overhead, poor modularity, high impact of change, poor scalability as well as the long build time. He also adds that monolith is when a single thing does all jobs, while microservices do one common thing.
Benefits Of Microservices
At 8:02, Mr. Anup briefs that microservices are minimal functional services that are deployed separately. The microservices can communicate with each other to perform the functionalities. At 9:27, he elaborates on how the Application Programming Interfaces (API’s) is managed with the API Gateway.
He also briefs on how the workflow moves from the Amazon CloudFront and then the API gateway cache, Amazon CloudWatch monitoring. The services correlated to these include endpoints on Amazon EC2, AWS Lambda functions, and other services. At 10:32, he briefs that the Amazon Simple Queue Service is for managing the message queues while the Amazon CloudWatch Events is responsible for the synchronization.
At 12:28, Mr. Anup points out the AWS services for the containerized microservices. It is also mentioned that when it comes to computing functionality, services like Amazon EC2S, Amazon EKS, Fargate, and AWS Elastic Beanstalk can be used. Then under the storage and database category, Amazon DynamoDB, Amazon Simple Storage Service (S3) services are grouped. At 14:15, the other services for the containerized microservices include developer tools, application integration, networking, API Proxy, logging, and monitoring.
Performance Of Microservices With Containers
At 22:34, Mr. Anup shows the way how the logic can be incorporated within each of the microservices. Application code, monitoring the SDK’s, routing, discovery, deployment logic are related to having the microservices with the containers.
At 26:07, he also elaborates on how the DevOps have been developing to achieve lower failure rate and code deployments. He then points out to the screen that briefs on how the lifecycle of the microservices is, indicating the services and the delivery pipelines. At 34:09, it is emphasized that the new deployment pipelines get built on the Jenkins and the Puppet.
At 44:09, it is briefed that microservices can sometimes be expensive to run in which case the automation and the process abstraction would save a lot of time. At 48:03, it is mentioned that fewer steps to start running a new service in production was made possible since microservices were being built on the containers. At 52:34, it is summarized that the integration of the developed services to a templated Jenkins pipelines is vital. It is summarized that by having the microservices with the containers, scalability, availability and supportability is achieved to a great extent.