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've written code for an application with many classes. If we develop a large-scale system while following the single responsibility and loose coupling principles, our code will likely have many classes.

But there's one problem. Any client (a piece of code) that interacts with the system will have to interact with a lot of classes, and sometimes that can become messy. How do we handle this situation?

The facade pattern is used to solve this problem. In the facade pattern, we have an extra class through which the client accesses the code (which has a lot of classes). This way, the client won't need to interact with the classes directly. It makes our code look cleaner and is easier to understand. Don’t worry if this sounds confusing. We'll discuss an example in the upcoming lesson, which will define the concept more clearly.



# Type

The facade is a Gang of Four design pattern that falls under structural design patterns.

# Purpose

The facade pattern hides the system's complexities and provides a simpler interface for the client to access the code (system).

# Applicability

Facade makes the client's interaction with classes easy. A facade pattern is applicable where the client is satisfied with a simple view of the complex system provided by the facade. Only those clients that want to interact with classes directly and want greater customization will have to look beyond the facade pattern.

# Structure


Learn about the facade pattern, its applicability, and its purpose. 

Facade Pattern

Learn about the facade pattern, its applicability, and its purpose.

Introduction

Introduction to Design Patterns

Deep Dive into Design Patterns

More Design Patterns

Idioms

Architectural Patterns

Patterns for Concurrency

Conclusion

Facade Design Pattern

Overview