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


In this chapter, I tried to give you more concrete examples of trendy architecture styles, because I already introduced the theoretical part in the previous chapter. The purpose of the two examples provided in this chapter was to demonstrate how quickly you can get started with cloud and cloud-native applications. Both examples relied on Infrastructure as Code. The remaining manual steps were there to keep things simple but rest assured that this can be fully automated in the real world.  

Both examples showed that the ecosystem plays an important role when building new solutions. For the serverless application, we relied on Azure Functions and Azure Event Grid, and we leveraged K8s's built-in scaling capabilities to load test our function handler. In the microservices example, we used Dapr, yet another great framework that comes from the K8s ecosystem. Both demos were intended to highlight the importance of this ecosystem, which you should never neglect as...