AWS App Mesh

AWS App Mesh

  • May 18, 2019
Table of Contents

AWS App Mesh

AWS recently released a new service App Mesh during the 2019 summit which has generated a lot of interest from developers world-wide. This service is a great example of how Amazon is highly customer-focused in delivery of products/features to the market. Besides that, there is no additional charge for using the service!:-)

With the advent of cloud, the importance of microservices has increased tremendously. In microservices architecture, large monolithic code-bases/architectures are broken down into smaller, more independent modules. Responsible for highly defined and discrete tasks, these individual modules communicate with each other using APIs.

To name a few, the most significant benefits of a microservice architecture are as follows: Software built as microservices can be broken down into multiple component services, so that each of these services can be deployed and then redeployed independently without compromising the integrity of an application. Better fault isolation; if one microservice fails, the others will continue to work. Code for different services can be written in different languages, and maintained in different repositories.

Better, and more contained CI-CD flows; each service can be built and deployed in its own separate pipeline, without affecting others. Increase the autonomy of individual development teams within an organization, as each service can be architected and managed in isolation. This leads to faster delivery, as the effort in co-ordination is reduced significantly.

Source: medium.com

Share :
comments powered by Disqus

Related Posts

Sidestepping Dependency Ordering with AppSwitch

Sidestepping Dependency Ordering with AppSwitch

We are going through an interesting cycle of application decomposition and recomposition. While the microservice paradigm is driving monolithic applications to be broken into separate individual services, the service mesh approach is helping them to be connected back together into well-structured applications. As such, microservices are logically separate but not independent.

Read More
Amazon S3 Path Deprecation Plan

Amazon S3 Path Deprecation Plan

Last week we made a fairly quiet (too quiet, in fact) announcement of our plan to slowly and carefully deprecate the path-based access model that is used to specify the address of an object in an S3 bucket. I spent some time talking to the S3 team in order to get a better understanding of the plan. We launched S3 in early 2006.

Read More
When AWS Autoscale Doesn’t

When AWS Autoscale Doesn’t

The premise behind autoscaling in AWS is simple: you can maximize your ability to handle load spikes and minimize costs if you automatically scale your application out based on metrics like CPU or memory utilization. If you need 100 Docker containers to support your load during the day but only 10 when load is lower at night, running 100 containers at all times means that you’re using 900% more capacity than you need every night. With a constant container count, you’re either spending more money than you need to most of the time or your service will likely fall over during a load spike.

Read More