Chapter 11. Scalability Considerations
You’ve covered everything from the architecture down to the endpoint logic and all the way through security and debugging. You’ve made some performance updates to ensure your app is running smoothly, so one of the last touches you can make is getting it ready to scale for more users. That means your backend application is “done.” You’ll add more features, make optimizations, and change things as the product develops and matures, but it’s in a state where the core functionality is stable.
Scaling is something that will start costing your company more money because you’ll need different tiers of third-party services and maybe even more team members. You know it’s time to start considering scaling when your performance enhancements aren’t enough to keep up with usage.
In this chapter, you’ll get more insight on:
-
Types of scaling
-
Scaling strategies
Deciding to scale is a huge undertaking because you might need to split existing data or significantly change resources and services. Take a considerable amount of time to research your options and verify what you have available as well as any business limitations you have. The decisions you make for scaling are an important part of how your systems will work going forward because migrations are harder at scale.
Types of Scaling
There are a few different ways you can tackle scaling a backend app. You can scale horizontally, which is when you increase the number of instances your app runs on. ...
Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
and much more.
Read now
Unlock full access