Different approaches to scaling front-end applications

When it comes to architecting software, it’s essential to think of what you are building, what it can grow into, what the context is, and who will work on it. Depending on these parameters, you’ll want to create an architecture that’s flexible enough to grow and adapt without overengineering it, making things more complex and time-consuming than needed.

For example, if you’re building a simple website for a small family-owned business, you don’t need elaborate architecture and complex design patterns; this will make things more complex and time-consuming than they need to be. The needs for the website will probably stay mostly the same, and the code base will remain small and manageable. But when you’re building enterprise software comprised of multiple applications, the needs and utility of those applications will change quite a bit, and you’ll want to ensure that the software...