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

Collaboration

There’s a difference between management and leadership. Management is about the tasks and concrete steps to achieving the end goal.

Leadership is about people, who you are and how you get to those people, how to inspire them, and how you show up for them.

An architect should be a leader that has a better overview, experience in diverse areas, and insights into both functional and non-functional requirements in order to contribute to the growth of the team around them. An architect should understand that each team member comes with different levels of knowledge about architecture, as it’s their responsibility to ensure common understanding.

Everyone on the development team needs to see the essence of software architecture and the consequences of not thinking about it before they start talking about things such as architecture description languages and evaluation methods. My own experience has empowered me to say that I even see the need for the...