Skip to content

Quick challenge to focus on design patterns and keep notes. Short implementation included.

Notifications You must be signed in to change notification settings

krasdav/Design-Pattern-a-Day

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

31 Commits
 
 
 
 
 
 

Repository files navigation

Design pattern per day

Study design patterns and implement short examples


Creational Design Patterns

Day 1 - Factory Method

package org.learn.david.creational.factorymethod;

Factory Method is a creational design pattern that provides an interface
for creating objects in a superclass, but allows subclasses to alter the
type of objects that will be created.

Day 2 - Builder

package org.learn.david.creational.builder; package org.learn.david.creational.builder2;

Builder is a creational design pattern that 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.

Day 3 - Abstract Factory

package org.learn.david.creational.AbstractFactory;

Abstract Factory is a creational design pattern that lets you produce families
of related objects without specifying their concrete classes.

Day 4 - Singleton

package org.learn.david.creational.Singleton;

Singleton is a creational design pattern that lets you ensure that a class has
only one instance, while providing a global access point to this instance.

Structural Design Patterns

Day 5 - Adapter

package org.learn.david.structural.adapter;

Adapter is a org.learn.david.structural design pattern that allows objects with
incompatible interfaces to collaborate.

Day 6 - Bridge

package org.learn.david.structural.bridge.nobridge; - Without Bridge Pattern
package org.learn.david.structural.bridge.bridge; - Bridge Pattern used

Bridge is a structural design pattern that 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.

Day 7 - Composite

package org.learn.david.structural.composite;

Composite is a structural design pattern that lets you compose objects into
tree structures and then work with these structures as if they were individual objects.

Day 8 & 9 - Decorator & Facade

package org.learn.david.structural.decorator;

Decorator is a structural design pattern that lets you attach new behaviors
to objects by placing these objects inside special wrapper objects that contain
the behaviors.

package org.learn.david.structural.facade; Facade is a structural design pattern that provides a simplified interface to a
library, a framework, or any other complex set of classes.

Day 10 - Flyweight

package org.learn.david.structural.flyweight;

Flyweight is a structural design pattern that 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.

Day 10 - Proxy

package org.learn.david.structural.proxy;

Proxy is a structural design pattern that 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.

Behavioral Design Patterns

Day 11 - Chain of Responsibility

package org.learn.david.behavioral.chainofresponsibility;

Chain of Responsibility is a behavioral design pattern that 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.

Day 12 - Command

package org.learn.david.behavioral.command;

Command is a behavioral design pattern that turns a request into a stand-alone object that
contains all information about the request. This transformation lets you pass requests as
a method arguments, delay or queue a request’s execution, and support undoable operations.

Day 13 - Iterator

package org.learn.david.behavioral.iterator;

Iterator is a behavioral design pattern that lets you traverse elements of a collection without
exposing its underlying representation (list, stack, tree, etc.).

Day 14 - Mediator

package org.learn.david.behavioral.mediator;

Mediator is a behavioral design pattern that 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.

Day 15 - Memento

package org.learn.david.behavioral.memento;

Memento is a behavioral design pattern that lets you save and restore the previous state of an object
without revealing the details of its implementation.

Day 16 - Observer

package org.learn.david.behavioral.observer;

Observer is a behavioral design pattern that lets you define a subscription mechanism to notify multiple
objects about any events that happen to the object they’re observing.

Day 17 - State

package org.learn.david.behavioral.state;

State is a behavioral design pattern that lets an object alter its behavior when its internal state
changes. It appears as if the object changed its class.

Day 17 - Strategy

package org.learn.david.behavioral.strategy;

Strategy is a behavioral design pattern that lets you define a family of algorithms, put each of them
into a separate class, and make their objects interchangeable.

Day 18 - Template Method

package org.learn.david.behavioral.templatemethod;

Template Method is a behavioral design pattern that defines the skeleton of an algorithm in the
superclass but lets subclasses override specific steps of the algorithm without changing its structure.`

Day 19 - Visitor

package org.learn.david.behavioral.visitor; Visitor is a behavioral design pattern that lets you separate algorithms from the objects on which they operate.

About

Quick challenge to focus on design patterns and keep notes. Short implementation included.

Topics

Resources

Stars

Watchers

Forks

Releases

No releases published

Packages

No packages published

Languages