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
Programming languages can be divided into two types: 
- **Managed**, in which we have automatic memory management and garbage collection. Java is an example of a managed language.
- **Unmanaged**, in which we don't have automatic memory management and garbage collection. C/C++ is an example of an unmanaged language.

In unmanaged languages, whenever the program acquires memory from the operating system, the program should manually release these resources. For example, in our C++ program, we might allocate some memory for an array at runtime and hold its pointer in a local variable. We might forget to release the dynamically allocated memory portion before the variable holding the pointer goes out of scope. In such a case, the allocated memory isn’t marked as free by the operating system and isn't available for use by other programs. This is called a memory leak.


RAII stands for **resource acquisition is initialization** and is a programming idiom specifically used to handle the situation described above. In RAII, the object that holds a resource release is in its destructor. The destructor of an object always runs when the object goes out of scope.
 

This technique is known as **constructor acquires, destructor releases (CADRe)**. It's not mandatory to allocate the resources in the constructor in this idiom, although that is one option.




Get an overview of resource acquisition in initialization (RAII). 

Introduction

Introduction to Design Patterns

Deep Dive into Design Patterns

More Design Patterns

Idioms

Architectural Patterns

Patterns for Concurrency

Conclusion

RAII Idiom

Overview