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

Reviewing the GoF

The GoF originated from the unforgettable book, Design Patterns: Elements of Reusable Object-Oriented Software, published in 1994 and written by four authors— hence the name. This book popularized the notion of design patterns and proposed 23 of them. Many other patterns have been added since then. A good source to check most of the available patterns is this Wikipedia page: Here, you can find the original patterns proposed by the GoF as well as more recently added ones. The first thing to know as a software architect is the different categories of design patterns, outlined as follows:

  • Creational: Patterns in this category relate to the instantiation of objects. They mostly impact performance and scalability. They help prevent the waste of computing resources. Creational patterns, especially the dependency injection (DI) pattern, also improve the testability and maintainability of your code.
  • ...