Loading repository data…
nemanjarogic / repository
A comprehensive design patterns library implemented in C#, which covers various design patterns from the most commonly used ones to the lesser-known ones. Get familiar with and learn design patterns through moderately realistic examples.
A transparent discovery signal based on current public GitHub metadata.
This score does not audit code, security, maintainers, documentation quality, or suitability. Verify the repository and its current documentation before adoption.
In software engineering, a design pattern is a general, repeatable solution to a commonly occurring problem in software design. A design pattern isn't a finished design that can be transformed directly into code. It is a description or template for how to solve a problem that can be used in many different situations. In addition, design patterns allow developers to communicate using well-known, well-understood names for software interactions.
Know when to use a certain design pattern, and when not to. No design pattern is a 42 - the answer to life, the universe, and everything. There are situations in which every design pattern easily becomes an antipattern.
Design patterns can be separated into three main categories:
Creational design patterns are design patterns that deal with object creation mechanisms, trying to create objects in a manner suitable to the situation. The basic form of object creation could result in design problems or added complexity to the design. Creational design patterns solve this problem by somehow controlling this object creation.
Structural design patterns are design patterns that ease the design by identifying a simple way to realize relationships among entities. Structural patterns are concerned with how classes and objects are composed to form larger structures.
Behavioral patterns are concerned with algorithms and the assignment of responsibilities between objects. Behavioral patterns describe not just the patterns of objects or classes but also the patterns of communication between them.
This repository contains a comprehensive design patterns library implemented in C#, which covers various design patterns from the most commonly used ones (Gang of Four) to the lesser-known ones. It enables you to get familiar with and learn design patterns through moderately realistic examples.
| Design Pattern | Type | Description | Introduction |
|---|---|---|---|
| Abstract Factory | Creational | Provides an interface for creating families of related or dependent objects without specifying their concrete classes. |
Selected from shared topics, language and repository description—not editorial ratings.
andredarcie /
The "design-patterns-in-csharp" repository is a comprehensive guide featuring practical implementations of various design patterns in C#, ideal for enhancing software architecture skills.
43/100 healthaboubakr-jelloulat /
A comprehensive contacts management system built with C# following a clean 3-tier architecture pattern. This project demonstrates enterprise-level software design principles with clear separation of concerns across presentation, business logic, and data access layers
38/100 health| Adapter | Structural | Allows objects with incompatible interfaces to collaborate. |
| Bridge | Structural | Lets you split a large class or a set of closely related classes into two separate hierarchies—abstraction and implementation—which can be developed independently of each other. |
| Builder | Creational | Lets you construct complex objects step by step. The pattern allows you to produce different types and representations of an object using the same construction code. |
| Chain Of Responsibility | Behavioral | Lets you pass requests along a chain of handlers. Upon receiving a request, each handler decides either to process the request or to pass it to the next handler in the chain. |
| Command | Behavioral | Turns a request into a stand-alone object that contains all information about the request. This transformation lets you parameterize methods with different requests, delay or queue a request’s execution, and support undoable operations. |
| Composite | Structural | Lets you compose objects into tree structures and then work with these structures as if they were individual objects. Treat individual objects and compositions of objects uniformly. |
| Decorator | Structural | Lets you attach new behaviors to objects by placing these objects inside special wrapper objects that contain the behaviors. Extend or alter the functionality of objects at runtime. |
| Facade | Structural | Provides a simplified interface to a library, a framework, or any other complex set of classes. This makes a complex body of code simpler to use and consume. |
| Factory Method | Creational | Provides an interface for creating objects in a superclass, but allows subclasses to alter the type of objects that will be created. |
| Flyweight | Structural | Lets you fit more objects into the available amount of RAM by sharing common parts of state between multiple objects instead of keeping all of the data in each object. It reduces storage costs for a large number of objects. |
| Iterator | Behavioral | Lets you traverse elements of a collection without exposing its underlying representation (list, stack, tree, etc.) |
| Mediator | Behavioral | Lets you reduce chaotic dependencies between objects. The pattern restricts direct communications between the objects and forces them to collaborate only via a mediator object. |
| Memento | Behavioral | Lets you save and restore the previous state of an object without revealing the details of its implementation. |
| Observer | Behavioral | Lets you define a subscription mechanism to notify multiple objects about any events that happen to the object they are observing. |
| Prototype | Creational | Lets you copy existing objects without making your code dependent on their classes. |
| Proxy | Structural | Lets you provide a substitute or placeholder for another object. A proxy controls access to the original object, allowing you to perform something either before or after the request gets through to the original object. |
| Singleton | Creational | Ensures that a class has only one instance, while providing a global access point to this instance. |
| State | Behavioral | Lets an object alter its behavior when its internal state changes. It appears as if the object changed its class. This pattern is close to the concept of finite-state machines. |
| Strategy | Behavioral | Enables an algorithm’s behavior to be selected at runtime. The pattern defines a family of algorithms, encapsulates each algorithm and makes the algorithms interchangeable within that family. In other words, this pattern is used when we have multiple algorithms for a specific task and we want the client to decide which actual impl |
aboubakr-jelloulat /
A comprehensive contacts management system built with C# following a clean 3-tier architecture pattern. This project demonstrates enterprise-level software design principles with clear separation of concerns across presentation, business logic, and data access layers
38/100 healthStavLobel /
A lightweight automation framework built with C# and Playwright implementing Clean Architecture principles. Supports both UI and API testing with Page Object Model design, utility functions, and comprehensive HTML reporting.
34/100 healthggwozdz90 /
A modern C# client library for speech-to-text API integration. Clean architecture design with comprehensive error handling and logging for reliable audio transcription services.
39/100 healthTejszerska /
A comprehensive desktop application designed to manage the daily operations of a Pawn Shop. Built with C#, WPF, and Entity Framework, the project heavily focuses on clean architecture, adhering strictly to the MVVM (Model-View-ViewModel) design pattern and Object-Oriented Programming principles.
53/100 health