Search icon CANCEL
Subscription
0
Cart icon
Your Cart (0 item)
Close icon
You have no products in your basket yet
Save more on your purchases! discount-offer-chevron-icon
Savings automatically calculated. No voucher code required.
Arrow left icon
All Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Newsletter Hub
Free Learning
Arrow right icon
timer SALE ENDS IN
0 Days
:
00 Hours
:
00 Minutes
:
00 Seconds
Arrow up icon
GO TO TOP
JavaScript at Scale

You're reading from   JavaScript at Scale Build web applications that last, with scaling insights from the front-line of JavaScript development

Arrow left icon
Product type Paperback
Published in Jul 2015
Publisher
ISBN-13 9781785282157
Length 266 pages
Edition 1st Edition
Languages
Tools
Arrow right icon
Author (1):
Arrow left icon
Adam Boduch Adam Boduch
Author Profile Icon Adam Boduch
Adam Boduch
Arrow right icon
View More author details
Toc

Table of Contents (17) Chapters Close

JavaScript at Scale
Credits
About the Author
About the Reviewers
www.PacktPub.com
Preface
1. Scale from a JavaScript Perspective FREE CHAPTER 2. Influencers of Scale 3. Component Composition 4. Component Communication and Responsibilities 5. Addressability and Navigation 6. User Preferences and Defaults 7. Load Time and Responsiveness 8. Portability and Testing 9. Scaling Down 10. Coping with Failure Index

Chapter 9. Scaling Down

We tend to think of scaling as a unidirectional problem—we can only scale up from where we are currently. Unfortunately, that doesn't quite work. We can only scale in one direction for so long before the foundation crumbles under our feet. The key is in identifying the scaling limitations, and designing around them.

In this chapter, we'll look at the fundamental scaling constraints faced by JavaScript architects in nearly every browser environment. We'll also look at the customer as a scaling influencer, and how new features conflict with existing features. Scaling down from bloated design is an essential activity as well.

The composition of our application as a whole determines how easy or how difficult it'll be to scale down by turning features off. It all has to do with coupling, and if we look closely, we'll often discover that we need to refactor our components so they can be easily removed later on.

lock icon The rest of the chapter is locked
Register for a free Packt account to unlock a world of extra content!
A free Packt account unlocks extra newsletters, articles, discounted offers, and much more. Start advancing your knowledge today.
Unlock this book and the full library FREE for 7 days
Get unlimited access to 7000+ expert-authored eBooks and videos courses covering every tech area you can think of
Renews at $15.99/month. Cancel anytime
Visually different images