Facade Design Pattern Explained With Simple Example: Structural Design Pattern Category

The Facade design pattern provides a simple interface to a complex code in order to make the product easier to understand and use. This design pattern reduces the dependency of client code on the implementation of internal objects and since most of the product code uses the facade to hide the complexity of the system, thus allows the flexibility in developing the system. In this pattern, a single wrapper class known as “Facade” is implemented which contains a set of objects required by client. For Design patterns basic explanation see (Design Patterns Simplified Version).

(more…)

Facade Design Pattern Explained With Simple Example: Structural Design Pattern Category Read More

Diameter Protocol Basics

Diameter protocol is an AAA(Authentication, Authorization and Accounting) protocol vastly used in core network nodes in 3G and LTE architecture. Diameter protocol evolved from RADIUS Protocol with additional functionalities in multiple aspects. Diameter protocol is defined by IETF and is known as Diameter Base Protocol (RFC 6733 (older one RF 3588)) which provides framework for applications like network access, IP mobility etc. Diameter Applications extend the Diameter base protocol by adding new AVP’s, commands etc to provide extended functionalities.

(more…)

Diameter Protocol Basics Read More

Composite Design Pattern Explained With Simple Example: Structural Design Pattern Category

The Composite design pattern solves the problem via partitioning the various modules of the product.This design pattern treats a combination of objects as if they are an instance of an object. This design pattern sets up a tree structure in which each element performs a specific task. In this pattern every element of a tree can be of composite type which can have child or elements below them or leaf element which can’t have any elements below them. For Design patterns basic explanation see (Design Patterns Simplified Version)

(more…)

Composite Design Pattern Explained With Simple Example: Structural Design Pattern Category Read More

Bridge Design Pattern Explained With Simple Example: Structural Design Pattern Category

The Bridge design pattern is used to separate out interface details and implementation details to reduce the dependency on each other which will provide the flexibility of changing one part without affecting the other part. This design pattern is useful in cases where the class and its function both changes frequently.  For Design patterns basic explanation see (Design Patterns Simplified Version)

(more…)

Bridge Design Pattern Explained With Simple Example: Structural Design Pattern Category Read More

Adapter Design Pattern Explained With Simple Example: Structural Design Pattern Category

The Adapter design pattern converts the interface of a class into another interface which is expected by the client. This design pattern is mostly used to make already existing classes work with each other without modifying it’s implementation. This design pattern is useful in cases where an existing class does all the required stuff but uses a different interface which is different from the client interface. For Design patterns basic explanation see (Design Patterns Simplified Version)

(more…)

Adapter Design Pattern Explained With Simple Example: Structural Design Pattern Category Read More