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

Decisions and risk management

As business evolves, so does our software, depending on the context and domain. What we need is to think in terms of building tolerance to change within the system. Observe where and what kind of changes appear through iterations. You can expect these changes and be prepared to meet them. Why so much analyzing?

Every time we make a final decision, we also say no to further details we might receive over time, which could help us make more informed decisions.

Making decisions concerning architectural aspects is very sensitive because these decisions have a huge impact. One of the best practices in software development is to avoid making decisions until the very last moment because there is a high level of uncertainty, especially in architecture. This makes the future hard to predict. When things are hard to predict, we tend to speculate. We are aware of this and trying to push the moment of deciding the limit forward is essential to building a system...