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

Myth no.3: Architecture is not about coding

From what we’ve discussed, maybe with some exceptions, architecture is a part of the development process, the part that is later taken over and implemented by the team. Architecture is not about forgetting about implementation details and getting drowned in abstractions but about keeping them balanced. I think we become good architects when moving carefully from one to the other.

Software architecture is all about understanding how the system works as a whole. Going from contributing to the architecture to being responsible and making decisions to grow a product is a process. The first step of this process is being honest with our experience level and what areas we need to focus on to proceed to the next level as professionals.

We need to be aware of the differences that help us to evolve. For example, as a programmer, your constant focus is on details, while architects focus most of their time on the whole picture, and most...