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

Introducing cloud service models, the cloud, and cloud-native systems

The prevalence of cloud ecosystems is a game-changer, and you should take this into account from the start when you design applications, should you envision the cloud as a hosting platform. As per my real-world observations, this fact is often misunderstood or overlooked by software architects, who tend to neglect the ecosystem their code is running in and focus too much on the code itself. The reason why it is important to grasp the ecosystem is that it comes with pre-built services and functionalities, which can boost your productivity. The type of service model you work with tends to steer your design choices. The following diagram shows the most important service models:

Figure 6.1 – Cloud service models

In the preceding diagram, from left to right, the level of operations increases. For example, the Software as a Service (SaaS) model is a fully managed off-the-shelf software...