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

What is design?

A system’s design shapes things more at the code level – the way each component works, the purpose of each element, and concerns of this kind.

A solid system design helps the development team be more efficient and organized in understanding the responsibilities of functions, modules, and classes and what they can or can’t do. All of this is made possible by identifying the design of a system to later decide which design patterns we should use in specific contexts.

Extending the discussion about design and architecture, Grady Booch nicely discusses how architecture represents the significant design decisions that shape a system, where the cost of the changes necessary correspond to the significance of these decisions.

Significant decisions are architecture, and the rest is design. Later on, we will go a bit deeper into the decision-making subject. Still, before we get there, we can summarize that software architecture is focused on...