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

Chapter 5: Design Patterns and Clean Architecture

Although software architecture is not only about coding, a software architect is still required to have a vast knowledge about development in general and about design patterns in particular. In this chapter, we will explore some of the most frequent design patterns. We will be looking closely at code-related concerns.

We will more specifically cover the following topics:

  • Understanding design patterns and their purpose
  • Reviewing the Gang of Four (GoF)
  • Delving into the most recurrent patterns and applying them to a use-case scenario
  • Looking at clean architecture
  • My top 10 code smells

This chapter should help you grasp the most recurrent design patterns and how to make use of them in your software architecture practice. These patterns must be well understood because they impact quality attributes such as modifiability, extensibility, reliability, maintainability, testability, scalability, and everything...