Book Image

Software Architecture for Web Developers

By : Mihaela Roxana Ghidersa
Book Image

Software Architecture for Web Developers

By: Mihaela Roxana Ghidersa

Overview of this book

Large-scale web applications require you to write code efficiently following business and architectural considerations. They require web developers to understand the impact of their work on the system and how they can evolve the product. With this handbook, every developer will find something to take away. This book will help web developers looking to change projects or work on a new project in understanding the context of the application, along with how some design decisions or patterns fit better in their application’s architecture. It acts as a guide, taking you through different levels of professional growth with a focus on best practices, coding guidelines, business considerations, and soft skills that will help you gain the knowledge to craft a career in web development. Finally, you’ll work with examples and ways of applying the discussed concepts in practical situations. By the end of this book, you’ll have gained valuable insights into what it means to be a web architect, as well as the impact architecture has on a web application.
Table of Contents (15 chapters)
1
Part 1 – Getting the Grasp of Architecture
7
Part 2 – Architect: From Title to Role
10
Part 3 – From Developer to Architect

Consider how your application can scale in time

The usage of software products has gone through the roof. Our need to work quickly through our daily tasks has increased, and our patience has decreased just as much. At the same time, the market evolves, and since the competition develops, we must create quality and up-to-date products. This is why we must always be ready to change and extend our architectural direction, starting with the mindset that we need our application always to be prepared to scale.

Ignoring scalability is one of the most dangerous things regarding the application life cycle because the consequences can be disastrous. As we discussed, as architects, we need to understand the direction of the application and what we want to achieve in the best-case scenarios. Not considering scalability will eventually push us to make uninformed decisions since we lack data about the next step and find ourselves needing to consume many resources to change some areas just because...