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

Practical use case

In this section, we will go through a very simplified use case for the sake of brevity. Here is the business scenario:

Contoso needs to provide a data upload channel for its customers. Uploaded data files may contain errors and must go through a data-cleansing and data-wrangling phase. If errors cannot be automatically fixed, an error file should be returned to the sender through a callback notification. After this first data-check and transformation phase, the resulting validated data is routed to the relevant systems for further handling. In addition, customers require that data can only be processed in Europe for sovereignty reasons, and they are used to File Transfer Protocol (FTP) systems.

The upload channel should always be available, while the actual handling of the data might be deferred in case of a system outage. It is expected by Contoso's customers to be notified back within 24 hours. The total volume of data uploaded by customers is about...