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

Who Codes and Who “Architects”?

Sometimes, when we are in a high-level role with great expectations on our shoulders, it might seem difficult to lean toward someone from the team and ask for an opinion. At the same time, we sometimes give particular importance to some high-level roles or to our tech “heroes”, which blocks us from being honest, asking for mentoring or for some clarifications, or giving suggestions when we could contribute. In this chapter, I would like us to open our mind and leave behind all preconceived ideas in order to be able to grow, learn, and make great products that we are proud of.

The architect role is challenging, and the expectation is to have a lot of knowledge and expertise. But the confusion starts here: you don’t need to be an expert in all software areas to become an architect. This is an unrealistic expectation. Considering the speed with which the technology stack has evolved in the last decade, there is enormous...