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 want to buy some electronic items from a store. The store near us often puts items on sale or gives special offers. But when we visit the store, we find out that there's no sale going on. We could visit the store every day and check for discounts and offers, but we can quickly see the problem: we're making lots of pointless visits to the store. How can we solve this problem?

One solution would be to give our contact information to the store, and the storekeeper could contact us once the sale starts. This would be beneficial because we wouldn't need to make pointless visits to the store. This is the crux of the observer design pattern.

# Definition 
The observer design pattern defines 1-to-n dependencies between objects so that changes to one object cause all dependent objects to be notified.

# Explanation
To understand this definition, let's map it to our example. The person (buyer) buying electric equipment depends on the shop. We can safely assume that there will be multiple buyers in the same store. The observer pattern defines a relationship from one shop to many buyers so that buyers will be notified about sales. 
# Type
The observer is a software design pattern that falls into the behavioral design.





# Structure


Get an overview of the observer design pattern.

Introduction

Introduction to Design Patterns

Deep Dive into Design Patterns

More Design Patterns

Idioms

Architectural Patterns

Patterns for Concurrency

Conclusion

Observer Design Pattern

Overview