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

How do design and architecture work together?

Although treated as two stages in the development process, architecture and design work together. While software architecture focuses on a system’s structure and high-level components, software design concentrates on a system’s details and implementation. We can consider that design combines the inner workings of components and implementation details, algorithms, and data structures.

The architecture is created in the initial stage of the system’s development. Later, as we evolve through the development phase, the design surfaces. Along the way, architecture and design overlap and work together, and as we soon realize over time, developers need to understand both. Sometimes, teams have to make critical technical decisions. By understanding both design and architecture, they can also understand how the design decisions they make will help build the architectural vision in the end.

Grady Booch nicely expresses...