Traffic & Scalability in Composable Systems

This is perhaps the most clear-cut ease in current challenges when moving from a monolithic application to a composable one. Each piece in the system exists decoupled from the rest. If it needs to scale, it can be done independently of the rest of the system.

Delegating scale management to providers

In many cases, your service providers need to worry about scale. Your CMS provider needs to be able to handle millions of records without sacrificing API performance. You don’t. You just need to make sure you can access the content and pass it to your frontend code.

Handling increased traffic

One of the cornerstones of the composable pattern is serving content from the edge, cached and as close to the user as possible.

There are servers on the edge, but if you can use a deployment platform to handle these, then they will scale seamlessly as needed.

In other words, increased traffic in a composable world doesn’t have anywhere near the effect it did for monolithic applications.