Book Image

Software Architecture for Busy Developers

By : Stéphane Eyskens
Book Image

Software Architecture for Busy Developers

By: Stéphane Eyskens

Overview of this book

Are you a seasoned developer who likes to add value to a project beyond just writing code? Have you realized that good development practices are not enough to make a project successful, and you now want to embrace the bigger picture in the IT landscape? If so, you're ready to become a software architect; someone who can deal with any IT stakeholder as well as add value to the numerous dimensions of software development. The sheer volume of content on software architecture can be overwhelming, however. Software Architecture for Busy Developers is here to help. Written by Stéphane Eyskens, author of The Azure Cloud Native Mapbook, this book guides you through your software architecture journey in a pragmatic way using real-world scenarios. By drawing on over 20 years of consulting experience, Stéphane will help you understand the role of a software architect, without the fluff or unnecessarily complex theory. You'll begin by understanding what non-functional requirements mean and how they concretely impact target architecture. The book then covers different frameworks used across the entire enterprise landscape with the help of use cases and examples. Finally, you'll discover ways in which the cloud is becoming a game changer in the world of software architecture. By the end of this book, you'll have gained a holistic understanding of the architectural landscape, as well as more specific software architecture skills. You'll also be ready to pursue your software architecture journey on your own - and in just one weekend!
Table of Contents (14 chapters)
Section 1: Introduction
Section 2: The Broader Architecture Landscape
Section 3: Software Design Patterns and Architecture Models
Section 4: Impact of the Cloud on Software Architecture Practices
Section 5: Architectural Trends and Summary

Mapping cloud services to architecture styles and patterns

To make sure you realize the importance of the ecosystem, I have mapped a few typical cloud architecture styles and design patterns to some cloud services. These services help you achieve results faster and better. You can rely on them to boost your productivity and comply with many NFRs out of the box. This does not mean that you cannot work with similar patterns on-premises, nor that you are restricted to the services depicted in Figures 6.5 and 6.6, but this should give you a solid overview.

To illustrate the mapping between the patterns and the services, I considered Microsoft Azure and Amazon Web Services (AWS) because they are the two leading cloud providers at the time of writing:

Figure 6.5 – Azure services mapped to patterns

The circles with a thick border are the patterns, while the other circles represent the cloud services. For example, if you must build a SAGA (which I will explain...