SimpleTechTalks

Chain-of-Responsibility Design Pattern Explained With Simple Example: Behavioural Design Pattern Category

The Chain-of-Responsibility design pattern basically consists of a source of command objects and a hierarchical series of processing objects. Every processing unit will process only typical kind of commands and it will pass rest of the command to next processing unit, thus creating a chain of processing units and that’s why the name of this design pattern is Chain-of-Responsibility pattern. This pattern provides the idea of one of the best programming practice which is “loose coupling”. For Design patterns basic explanation see (Design Patterns Simplified Version).

(more…)

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

by Sandeep Kumar

The Proxy design pattern allows to define a “proxy” class which will act as a wrapper object which will be called by the client to access the product object without exposing the details. This proxy class can also be used to add extra functionality without changing the product behavior. This design pattern can be used in cases to provide additional security access to an existing product or providing an interface for remote resources. For Design patterns basic explanation see (Design Patterns Simplified Version).

(more…)

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

by admin

The flyweight design pattern allows to greatly reduce memory footprint of any product by dividing an object into basically two parts. If multiple objects have some internal part as common then all these objects can share these memory to reduce memory consumption. The other part which varies from object to object will still be part of final object. The common part of various object is stored and shared via a “Flyweight” object. For Design patterns basic explanation see (Design Patterns Simplified Version).

(more…)

Diameter Agents Simple Explanation

by Sandeep Kumar

Diameter protocol defines various nodes for specific purposes which are often known as Diameter Agents. These agents are designed to distribute administrations of a system including maintenance of security mechanism. These Agents can also be used for load balancing via routing the diameter protocol messages based on some routing algorithms.
They can also do some sort of processing of diameter protocol messages to forward messages towards the target in a complex network which contains a large number of nodes.

Diameter Agents can be divided into two groups:

(more…)

Diameter Protocol AVP Structure

by Sandeep Kumar

Diameter Attribute-Value-Structure (AVP) are the data units inside the diameter messages which contains all the information. There has to be atleast one AVP in every diameter messages. A Diameter message can contain multiple sets of different AVPs. For basic information related to Diameter protocol read article (Diameter Protocol Basics). Structure of an AVP is shown in below image:

(more…)

Diameter Protocol Message Structure

by Sandeep Kumar

Diameter protocol is basically a Request/Response kind of protocol, hence this diameter protocol follows client/server model to communicate between nodes. In Diameter protocol, for every request message there will be an answer message for sure. For basic information related to Diameter protocol read article (Diameter Protocol Basics).

A Diameter protocol packet consists of Diameter message header along with variable number of AVP’s (Attribute-Value Pairs). Diameter message data is stored in form of AVP’s in the message.

(more…)

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

by Sandeep Kumar

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…)

Diameter Protocol Basics

by Sandeep Kumar

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…)

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

by admin

The Decorator design pattern allows behavior addition to an object either statically or dynamically without affecting the core behavior of other objects from the same class. This design pattern allows us to change the behavior of any specific object which is achieved by a wrapper class to the original class known as Decorator class. The original class is divided into two parts, one is with the essential basic features of the original class while the other one is the decorator base class which implements the same interface as the original class but allows to create several concrete decorator class having their own additional methods. For Design patterns basic explanation see (Design Patterns Simplified Version)

(more…)

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

by Sandeep Kumar

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…)