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 cloud and cloud-native patterns

Now that you have more clarity on the service models and their high-level impact, let's explore some patterns in more depth.

The Cache-Aside pattern

With cloud and cloud-native patterns, scaling a component is a scale-out/in story, not a scale-up/down one. This means that we multiply the number of instances, instead of adding more compute to a single instance. Scaling up/down is, of course, still possible, but scaling out/in is by design. Multiplying instances is not a neutral thing because it may disturb every in-process thing. Therefore, it has an impact on how we can handle data caching, user sessions, and so on. When considering a scale-out story, you should try to avoid in-process caching/sessions. Therefore, the Cache-Aside pattern should be implemented with an external cache system, such as Azure Redis Cache or AWS ElastiCache. The goal is to share cached data across instances and to prevent inconsistencies. The following...