nut-pipe npm package is an implementation of Chain of Responsibility Pattern. We can encapsulate or wrap every aspect of code in separate module or class or function, etc. So that, separated aspect modules would implement Single Responsibility Principle(SRP) and Seperation of Concern Principle(SoC) properly.
🙂 so if you want to implement OOP basics and principles, then you can use nut.pipe npm package.
This design provides to developer clean business logic code. They don't need to think about Error, Exception, Log handling business logic. Before their business logic code is called, pipeline is called and it means first middleware is triggered then first middleware will trigger next one, but no middleware knows about next middleware. Middleware should know about its business logic then should call next one.
I know too much words but developers want to see code 🙂 same code will be developed in different ways.
Code example v1
I wrote a greeting service with sayHello() and sayGoodbye() functions. They include all business logic in their body. This is not good approach definitely. Code duplications are everywhere 🙂 For example, every functions have try/catch, console.log('ENTRY: …'), console.log('SUCCESS: …'), console.log('ERROR: …'), etc. Notice that getFullName doesn't contain these business logics. So, we can't know whether it is called or not. If developer like me 🙂 doesn't write these kind of aspects(logging and exception handling is kind of aspect) then we never understand that that method is called in run-time.
I read Head First Design Patterns book shown as below. It is pretty good reference of Design Patterns. If you want to familiar of Design Patterns, i recommend it definitely. This post contains some examples of this book but in a different presentation. When I want to remember fundamentals of Design Patterns, this post will remind me 🙂 I hope that you will benefit from this post.
I will create a class diagram and implementation of it together. I will create a very simple class diagram and improve it step by step. That's why, I named Step 1, Step2 etc.
If you don't want to read all paragraphs, you just view class diagrams and code samples step by step. But, i heavily recommend to read and think of this post 🙂
Creational patterns are ones that create objects for you, rather than having you instantiate objects directly. This gives your program more flexibility in deciding which objects need to be created for a given case.
Abstract factory: provide an interface for creating families of related or dependent objects without specifying their concrete classes.
Builder: separate the construction of a complex object from its representation, allowing the same construction process to create various representations.
Factory method: define an interface for creating a single object, but let subclasses decide which class to instantiate. Factory Method lets a class defer instantiation to subclasses.
Prototype: specify the kinds of objects to create using a prototypical instance, and create new objects from the 'skeleton' of an existing object, thus boosting performance and keeping memory footprints to a minimum.
Singleton: ensure a class has only one instance, and provide a global point of access to it.
These concern class and object composition. They use inheritance to compose interfaces and define ways to compose objects to obtain new functionality.
Adapter: allows classes with incompatible interfaces to work together by wrapping its own interface around that of an already existing class.
Bridge: decouples an abstraction from its implementation so that the two can vary independently.
Composite: composes zero-or-more similar objects so that they can be manipulated as one object.
Decorator: dynamically adds/overrides behaviour in an existing method of an object.
Facade: provides a simplified interface to a large body of code.
Flyweight: reduces the cost of creating and manipulating a large number of similar objects.
Proxy: provides a placeholder for another object to control access, reduce cost, and reduce complexity.
Most of these design patterns are specifically concerned with communication between objects.
Chain of responsibility: delegates commands to a chain of processing objects.
Command: creates objects which encapsulate actions and parameters.
Interpreter: implements a specialized language.
Iterator: accesses the elements of an object sequentially without exposing its underlying representation.
Mediator: allows loose coupling between classes by being the only class that has detailed knowledge of their methods.
Memento: provides the ability to restore an object to its previous state (undo).
Observer: is a publish/subscribe pattern which allows a number of observer objects to see an event.
State: allows an object to alter its behavior when its internal state changes.
Strategy: allows one of a family of algorithms to be selected on-the-fly at runtime.
Template: method defines the skeleton of an algorithm as an abstract class, allowing its subclasses to provide concrete behavior.
Visitor: separates an algorithm from an object structure by moving the hierarchy of methods into one object.