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

All in all, it is helpful to note that to become great leaders, we also have to see what our own characteristics are and what we are best at. We must know ourselves, be willing to understand others, and start building with the information we gather from the books we read, from the experiences of others, and the projects we work with.

I’ll sum up by leaving you with two ideas: for developers, a concept called generative resistance states that good ideas do not come if everyone agrees on everything or has the same experiences. Be open and confident enough to give feedback to, challenge, and collaborate with the decisions of your technical leader and architect when you are sure your perspective can bring value. At the same time, ask, research, and be curious.

On the other side, for our architects: try deciding on and creating team dynamics regarding technical matters and decisions that make the team feel that great ideas result from the group. Bet on shared thinking...