Gain insights into software design patterns and architecture in C++. Learn about C++ idioms, concurrency patterns, and apply the right solutions to improve code quality and productivity.

Design Pattern and Architectural Pattern with C__.png

cpp.tar.gz

Thread_sanitizer

Thread_sanitizer-copy

Thread_sanitizer-copy-copy

reactor

Software engineering researchers and practitioners noticed that parts of software projects could often be solved using approaches that were discovered earlier to solve similar problems. This led to the documentation of software design and architectural patterns, which are known solution approaches to a class of problems. 

This course starts by putting software patterns into perspective by answering the question, “What is a software pattern, and how is it different from an algorithm?” You will then learn about the two classes of patterns—software design and architecture patterns. Next, you’ll learn common C++ idioms. Finally, you will learn about software patterns for concurrency. 

By the end of the course, you will have useful and practical tools to improve the quality of your code and productivity. You’ll also be able to analyze a given part of your software project, pick the right pattern for the job, and apply it.

Master Software Design Patterns and Architecture in C++

# Overview
Suppose that we have a class with the name `Weather`. Let's assume that this class is used by many other classes with hundreds of lines of code. Any changes made to the `Weather` class (even if they are just to one line) will cause recompilation of the `Weather` class, plus all the classes (that have hundreds of lines of code) that use the `Weather` class. As we can see, this behavior is undesirable and can waste a lot of time. PImpl is the idea we use to tackle this situation.

# PImpl
The C++ programming technique **pointer to implementation**, or **PImpl**, is used to remove the implementation details of a class from its object representation by placing them in a separate class. 

In our example, we place the implementation code of `Weather` in a separate class and access this implementation through a pointer from a `Weather` class. This pointer is generally called an opaque pointer. The classes that use the  `Weather` class don't need to be recompiled if the implementation changes. 

On large projects, this significantly reduces the compilation time. The **compiler firewall** idiom is another name for this concept.



Learn about PImpl (pointer to implementation).

Introduction

Introduction to Design Patterns

Deep Dive into Design Patterns

More Design Patterns

Idioms

Architectural Patterns

Patterns for Concurrency

Conclusion

PImpl

Overview