g11436719719165

2020 2021 2022 2023 2024

Most companies, like Amazon, start their business with a monolithic application because it's the fastest, easiest system to develop. However, there's a problem with tightly combining processes and running them as a single service. If one process of the application experiences a spike in demand, the entire architecture has to be scaled up to handle the load of that one process.

Moreover, adding and improving features becomes more complex as the code base grows, making it difficult to experiment with and implement new ideas. Monolithic architectures, too, add risk for application availability because many dependent and tightly coupled processes increase the impact of a single process failure.

This is why microservices emerge as companies grow. With a microservices architecture, an application is made up of independent components that run each application's processes as a service. Services are built for business capabilities, such as an online shopping cart, and each service performs a single function. It runs independently and is managed by a single development team, so each service can be updated, deployed, and scaled to meet the demand for specific functions of an application. The shopping cart, for example, can support a much larger volume of users when there's a sale.

Read more: AWS solutions architect associate jobs

As organizations move from monolith to microservices, many developers find that they want to manage dependencies within each service through a pipeline—and they've had to create new ways of packaging applications and running code. Because of these innovations, instances are no longer your only compute option.

2020-04-29 18:09:28, views: 848, Comments: 0