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

Myth no.1: Architecture never changes

Users’ needs evolve, the market is changing, competition is tough, technologies evolve and change, and teams’ structures and compositions also vary. On one side, we are lucky to be working in such a dynamic environment where technical evolution happens constantly. Technological evolution and ever-changing user and business requirements keep us in the loop, always giving us the satisfaction of learning something new. We grow as professionals and learn new approaches and technologies. This can become a “learning haven.” The real challenge comes when we have to make decisions that depend on our knowledge. This includes weighing why one technology is better than the other, what risks certain decisions bring, and what the costs of some requested changes are. The challenge is building products that meet our stakeholders’ needs today and are open to evolution for future requests. To make informed decisions, we need to...