#Design-Patterns
30 notas · última:
Devs: Don’t Just Read About Design Patterns, Implement Them
The post argues that design patterns are more useful as examples you build than as theory you read. A contrived C# animal-mission setup shows how decoupling lets missions, heroes, and lairs vary independently.
Design Patterns Are Temporary, Language Features Are Forever
The post argues that visitor starts to make more sense once you know pattern matching, and that newer Java features like sealed types and switch pattern matching can replace some old OO patterns.
8 Must-Know Distributed System Design Patterns
The page lists common distributed system patterns and what each one addresses: offloading cross-cutting tasks, handling failures, separating reads and writes, partitioning data, coordinating services, and replaying state changes.
The Best Microservices Design Patterns Explained Like You’re Ordering Pizza
The article explains 11 microservices design patterns with a pizza analogy, showing how each one maps to service boundaries, requests, data storage, failures, workflows, legacy migration, and frontend-specific backends.
Five Design Patterns to know in Node.js
The text presents five common patterns in Node.js — Singleton, Factory, Observer, Decorator, and Dependency Injection — and shows how each helps organize creation, extension, and the use of dependencies.
Proxy Design Pattern in C# - Code Maze
The Proxy pattern adds a wrapper around a real object to control access and add logic without changing the original service. The article shows a caching proxy in C# and mentions logging, protection, remote, virtual and selection proxies.
Chain of Responsibility Design Pattern in C#
The article explains the Chain of Responsibility pattern in C#, shows the middleware case in ASP.NET Core, and refactors a book loan flow into chained handlers.
The Publish Pattern
A concurrency pattern for decoupling producers and consumers using a const shared_ptr, avoiding mutex bottlenecks while keeping the consumer always on the latest published version.
Four Layer Architecture
A pattern from the c2 wiki splits client-server apps into View, ApplicationModel, DomainModel and Infrastructure, extending MVC to cover persistence and the outside world.
Visitor Pattern
Represent an operation to be performed on elements of an object structure without changing the classes.
Strategy Pattern
Define a family of algorithms, encapsulate each one, and make them interchangeable at runtime.
Proxy Pattern
Provide a surrogate or placeholder for another object to control access to it.
Prototype Pattern
Create new objects by cloning an existing instance.
Memento Pattern
Capture an object's internal state so it can be restored later without violating encapsulation.
Mediator Pattern
Define an object that encapsulates how a set of objects interact, promoting loose coupling.
Iterator Pattern
Access elements of a collection sequentially without exposing its underlying representation.
Facade Pattern
Provide a simplified interface to a complex subsystem.
Decorator Pattern
Attach additional responsibilities to an object dynamically, as an alternative to subclassing.
Chain of Responsibility Pattern
Pass a request along a chain of handlers until one processes it.
Adapter Pattern
Convert the interface of a class into another interface clients expect.
Gang of Four Design Patterns
The 23 design patterns catalogued by Gamma, Helm, Johnson and Vlissides in Design Patterns: Elements of Reusable Object-Oriented Software (1994).
CQRS
CQRS — Command Query Responsibility Segregation — is a pattern first described by Greg Young. At its heart is the notion that you can use a different model to update information than the model you…
Mastering the Decorator Pattern in PHP
The page shows how the Decorator Pattern avoids class explosion in PHP by wrapping a base object with small decorators that add features at runtime. It contrasts this with inheritance-heavy combinations and a large factory switch.
The Structure of Patterns
The post explains the three-part definition of a pattern and walks through the 13-step structure used in classic pattern books, using the Strategy pattern in C++ as the example.
SOLID Principles: The Beauty of Design Pattern Series
The page presents SOLID as a set of OOP concepts for making software easier to change, and links poor design to rigidity, fragility, duplication, slow modules, and unnecessary complexity.
Patterns That Every Developer Should Know
The post presents four design patterns every developer should know—Singleton, Builder, Factory, and Facade—showing how each one simplifies a common problem and when it becomes useful.
Software Engineering Principles
The post introduces core software engineering and OOP ideas, then ties them to SOLID, composition, DRY, KISS, YAGNI, and UML-based modeling for cleaner, more maintainable code.
3 Design Patterns Every Developer Should Learn
The article presents design patterns as reusable approaches to recurring software problems and recommends Strategy, Singleton, and Observer as patterns every developer should know, while warning against overusing them.
Books to Read as a Developer
The post lists books a developer should read for programming practice, code quality, design patterns, legacy code, team work, and software design principles across languages.
Padrão de projeto de software - JavaScript: Observer
O texto explica o padrão Observer em JavaScript, compara os modos push e pull, mostra exemplos de código e aponta usos comuns em eventos DOM e plugins jQuery.