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

Which NoSQL technology should I use?

The answer to this question depends on several factors. A few are listed here:

  • If you want to store time series (save increments at small, regular intervals), then the best option would be to use InfluxDB or VictoriaMetrics.
  • If you need something similar to SQL but could live without joins, or in other words, if you plan to store your data in columns, you can try out Apache Cassandra, AWS DynamoDB, or Google's BigTable.
  • If that's not the case, then you should think about whether your data is a document without a schema, such as JSON or some kind of application logs. If that's the case, you could go with Elasticsearch, which is great for such flexible data and provides a RESTful API. You could also try out MongoDB, which stores its data in Binary JSON (BSON) format and allows MapReduce.

OK, but what if you don't want to store documents? Then you could opt for object storage, especially if your data is large. Usually, going...