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

Design versus Architecture

“The designer is concerned with what happens when a user presses a button, and the architect is concerned with what happens when ten thousand users press a button.”

SCEA for Java™ EE Study Guide by Mark Cade and Humphrey Sheil

As discussed in Chapter 1, The Role of Architecture, architecture is a base structure upon which we build step by step, one component after another, creating relationships between them. All of this is being realized while considering the whole picture of a product.

When we talk about architecture, we can’t avoid discussing design because architecture is confused with design in many cases. This may be because we tend to define architecture abstractly.

Software architecture is a starting point – a base for the system. The decisions we make concerning architecture must fulfill the business and technical requirements while considering quality attributes such as performance...