Partially 3 of this collection, we explored the fashionable utility stack for early-stage startups, together with a frontend internet hosting platform, a serverless API backend, and a serverless relational database tier. This highly effective mixture has taken us far past what we used to have the ability to do with a single server.
As visitors continues to scale, this contemporary stack will ultimately attain its limits. On this closing a part of the collection, we look at the place this contemporary stack would possibly begin to disintegrate, and discover methods to evolve it to deal with extra visitors.
At a sure threshold, dealing with the size and complexity of the appliance requires a completely new method. We mentioned microservice structure briefly earlier within the collection. We’ll construct on that with an exploration of how hyper-growth startups can progressively migrate to a microservice structure by leveraging cloud native methods.
As visitors continues to scale, the fashionable utility stack will begin to run into points. Relying on the complexity of the appliance, the stack ought to be capable of deal with low a whole lot of 1000’s of each day energetic customers.
Properly earlier than we run into efficiency points, we must always have a sturdy operational monitoring and observability system in place. In any other case, how would we all know when the appliance begins to disintegrate on account of rising visitors load?
There are various observability options out there. Constructing a sturdy system ourselves isn’t any easy activity. We strongly advise shopping for an answer. Many cloud suppliers have in-house choices like AWS Cloud Operations that is likely to be adequate. Some SaaS choices are…
