- abstract-document.
- abstract-factory.
- adapter.
- aggregator-microservices.
- api-gateway.
- balking.
- bridge.
- builder.
- business-delegate.
- caching.
- callback.
- chain.
- command.
- composite.
- converter.
- cqrs.
- dao.
- data-bus.
- data-mapper.
- data-transfer-object.
- decorator.
- delegation.
- dependency-injection.
- double-checked-locking.
- double-dispatch.
- eip-aggregator.
- eip-splitter.
- eip-wire-tap.
- event-aggregator.
- event-asynchronous.
- event-driven-architecture.
- event-queue.
- event-sourcing.
- execute-around.
- extension-objects.
- facade.
- faktory-kit.
- factory-method.
- feature-toggle.
- fluent-interface.
- flux.
- flyweight.
- front-controller.
- gaurded-suspension.
- half-sync-half-async.
- hexagonal.
- intercepting-filter.
- interceptor.
- iterator.
- layers.
- lazy-loading.
- marker.
- mediator.
- memento.
- message-channed.
- model-view-controler.
- model-view-presenter.
- module.
- monad.
- monostate.
- multition.
- mute-idiom.
- mutex.
- naked-objects.
- null-object.
- object-mother.
- object-pool.
- observer.
- page-object.
- partial-response.
- poison-pill.
- private-class-data.
- producer-consumer.
- promise.
- property.
- prototype.
- proxy.
- publish-subscribe.
- que-load-leaving.
- reactor.
- read-writer-lock.
- repository.
- resource-acquisition-is-initialization.
- retry.
- semaphore.
- servant.
- service-layer.
- service-locator.
- singleton.
- specification.
- state.
- step-builder.
- strategy.
- template-method.
- thread-pool.
- throttling.
- tls.
- tolerant-reader.
- twin.
- unit-of-work.
- value-object.
- visitor.
work in progress: Kotlin branch
Design patterns are formalized best practices that the programmer can use to solve common problems when designing an application or system.
Design patterns can speed up the development process by providing tested, proven development paradigms.
Reusing design patterns helps to prevent subtle issues that can cause major problems, and it also improves code readability for coders and architects who are familiar with the patterns.
Before you dive into the material, you should be familiar with various Programming/Software Design Principles.
All designs should be as simple as possible. You should start with KISS, YAGNI, and Do The Simplest Thing That Could Possibly Work principles. Complexity and patterns should only be introduced when they are needed for practical extensibility.
Once you are familiar with these concepts you can start drilling down into patterns by any of the following approaches
- Using difficulty tags,
Difficulty-Beginner,Difficulty-Intermediate&Difficulty-Expert. - Using pattern categories,
Creational,Behavioraland others. - Search for a specific pattern. Can't find one? Please report a new pattern here.
If you are willing to contribute to the project you will find the relevant information in our developer wiki. We will help you and answer your questions in the Gitter chatroom.
This project is licensed under the terms of the MIT license.