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

Stakeholder management

Before we fully understood how vital architecture and its evolution were within a product’s life cycle, we felt that architecture wasn’t something that teams should consider. Once the AGILE method of doing things gained popularity, how we shaped a system’s structure changed. If in most cases, architecture was discussed from the start in the first place and followed carefully during development, things evolved in a more organized direction. The need for change was perceived more and more. Products changed while being developed. There were two main reasons for this:

  • The tech stack changes terribly fast. Approaches and tools evolve quickly and we must create the best user experiences and solid systems for our stakeholders.
  • Alongside the evolution of the tech stack, requirements also evolved. Users change their minds, the competition in the same market is enormous, and new features appear constantly.

Considering this, we...