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)
1
Section 1: Introduction
3
Section 2: The Broader Architecture Landscape
6
Section 3: Software Design Patterns and Architecture Models
9
Section 4: Impact of the Cloud on Software Architecture Practices
11
Section 5: Architectural Trends and Summary

Summary

It is a no-brainer that design patterns must be mastered by software architects because they are part of their toolbox. However, I also tried to stress the fact that you should always exercise your own judgment in your own specific context. I advocate for a pragmatic software architecture practice. Remember that, contrary to some of the clean architecture rantings, the code is not the only place to look. A good software architect aims to achieve both fit for purpose (where clean architecture can certainly play a role), and fit for use, which is most of the time ensured by non-code layers.

In our next chapter, we will see that most modern applications are often heavily distributed and rely on existing components. This is what I call the growing importance of the ecosystem.