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++

# Introduction

Software developers face problems every day during development. These problems are generally one of two types:

-  **Unique problems** that don't follow any specific pattern.
-  **Recurring problems** that follow some sort of pattern.

Design patterns were introduced specifically for the recurring problems faced by the developers. 


# What is a design pattern?
Design patterns are recipes that programmers use to solve a specific set of problems. A design pattern is not a piece of code we can copy into our application to solve the problem. Instead, it's a recipe to tackle the problem. Let's formally define what a design pattern is. Wikipedia says: "In software engineering, a software design pattern is a general, reusable solution to a commonly occurring problem within a given context in software design."

Before moving on, let's answer the question, "Why do we need to use design patterns?"


# Why do we need a design pattern?

There are many reasons to use design patterns, including:

- They provide us with a common vocabulary and well-defined semantics, making inter- and intra-team communication much easier.
- Tackling a problem as a whole is always difficult in programming. Design patterns divide the problem into small, digestible steps that are easy to solve and already proven. 
- Already knowing the steps involved in solving a problem helps us get to our solution faster. 
- They inspire solutions and are not tied to any specific problem, and they can be applied to solve the same problem in various domains/ applications. 
- They discourage reinventing the wheel. One design pattern used by an experienced programmer can be reused in similar projects, increasing the reusability of the code. 

Design patterns are not a mandatory part of software development, but they make our lives a lot easier. From communication to reusability, design patterns can become reliable tools for a programmer in software development. 




Get an overview of why we need design patterns.

Introduction

Introduction to Design Patterns

Deep Dive into Design Patterns

More Design Patterns

Idioms

Architectural Patterns

Patterns for Concurrency

Conclusion

Overview of Design Patterns

Introduction