Book Image

Software Architecture with C++

By : Adrian Ostrowski, Piotr Gaczkowski
Book Image

Software Architecture with C++

By: Adrian Ostrowski, Piotr Gaczkowski

Overview of this book

Software architecture refers to the high-level design of complex applications. It is evolving just like the languages we use, but there are architectural concepts and patterns that you can learn to write high-performance apps in a high-level language without sacrificing readability and maintainability. If you're working with modern C++, this practical guide will help you put your knowledge to work and design distributed, large-scale apps. You'll start by getting up to speed with architectural concepts, including established patterns and rising trends, then move on to understanding what software architecture actually is and start exploring its components. Next, you'll discover the design concepts involved in application architecture and the patterns in software development, before going on to learn how to build, package, integrate, and deploy your components. In the concluding chapters, you'll explore different architectural qualities, such as maintainability, reusability, testability, performance, scalability, and security. Finally, you will get an overview of distributed systems, such as service-oriented architecture, microservices, and cloud-native, and understand how to apply them in application development. By the end of this book, you'll be able to build distributed services using modern C++ and associated tools to deliver solutions as per your clients' requirements.
Table of Contents (24 chapters)
1
Section 1: Concepts and Components of Software Architecture
5
Section 2: The Design and Development of C++ Software
6
Architectural and System Design
10
Section 3: Architectural Quality Attributes
15
Section 4: Cloud-Native Design Principles
21
About Packt

Chapter 4

  1. What is event sourcing?
    • This is an architectural pattern that relies on keeping track of events that change the state of the system instead of keeping track of the state per se. It brings benefits such as lower latency, free audit logs, and debugability.
  2. What are the practical consequences of the CAP theorem?
    • As network partitions happen, if you want a distributed system, you'll need to choose between consistency and availability. In cases of partitions, you can either return stale data, an error, or risk timeouts.
  3. What can you use Netflix's Chaos Monkey for?
    • It can help you prepare for unexpected downtime of your services.
  4. Where can caching be applied?
    • Either on your client's side, in front of web servers, databases, or applications, or on a host near your potential client, depending on your needs.
  5. How should you prevent your app from going down when an entire data center does?
    • By using geodes.
  6. Why should you use an API gateway?
    • To simplify...