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

Summary

Being an architect is not something you simply read about. You can’t memorize 10 rules and then be ready to change the world. Most of the time, it is a tedious path with many challenges.

In this chapter, we learned that as an architect, you need to make your influence felt in the team and collaborate with the people that work on the same product as you do. As a role that influences a wide range of stakeholders, you need to learn to communicate effectively and manage the information you get from each to make the best decisions for the product.

Holding a leadership position within the technical field does not spare us from being there for our team, raising our colleagues by giving feedback or mentoring. Maybe one of the ideas we need to get out of our systems is that while you are an engineer or a tech person, you don’t need to collaborate or have expertise in working with people. Great teams deliver great products. You can have a group of superstars owning...