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

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
Packets-per-second limits in EC2

Packets-per-second limits in EC2

While evaluating the performance of a server application, we eventually (and hopefully) run up against the most fundamental constraining factor: the network. Cloud providers tend to offer somewhat handwavy guidance on networking constraints, especially when compared to the exhaustive literature explaining the quotas for RAM, CPU, and I/O. While working on an unrelated stress test in EC2, we were surprised by some results that led us down the path of investigating EC2 network capacity claims, resulting in this writeup. EC2 documentation describes network performance in terms of maximum available bandwidth.

Read More