Full Stack JavaScript Strategies

Chapter 11. Scalability Considerations

A Note for Early Release Readers

With Early Release ebooks, you get books in their earliest form—the author’s raw and unedited content as they write—so you can take advantage of these technologies long before the official release of these titles.

This will be the 11th chapter of the final book.

If you have comments about how we might improve the content and/or examples in this book, or if you notice missing material within this chapter, please reach out to the author at [e-mail].

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 ...