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

 



# Purpose

Sometimes a class only needs to have one pointer. For example, a system should only have one printer spooler, even though there may be several printers. Similarly, we can have multiple users on a website, but we don't create a new server for every user. The server remains a singleton. 


How can we make sure a class only has one instance and is easily accessible? To ensure that we can't make multiple class objects, we make its constructor private. This means we won't be able to create an object for the class. But there is one question we need to solve first: how do we make the first object if we can't make an object?

For this, we define a static method `getInstance()` inside the class. This method will be able to access the private constructor so that we can create an object through this static method. But there is still one problem. How do we make sure we only create one object of a class? 

For this, we create a static object inside the class. Initially, it will be null. The first time we call `getInstance()`, it will instantiate this object. If we call it again, it will simply return the already-created object.

Let's take a look at its skeleton code.
 






Learn about the singleton pattern along with its structure, participants, and use cases. 

Introduction

Introduction to Design Patterns

Deep Dive into Design Patterns

More Design Patterns

Idioms

Architectural Patterns

Patterns for Concurrency

Conclusion

Singleton Pattern

Purpose