Microservices API Gateway Introduction

Microservices architecture approach provides opportunity for multiple services to work together to create a cohesive application. Since, all the services interact with each other via different APIs hence it requires an entity to manage all the api interaction across services. This entity is called API Gateway and is one of the most important entities in microservices architecture. In this article, we are going to discuss about API Gateway and its importance in microservices architecture approach.

Please check Introduction to Microservices Architecture for more information.

(more…)
Microservices API Gateway Introduction Read More

Microservices Design Best Practices

Microservices architecture is a software development approach allowing breaking down of large complex applications into smaller and independent modules which are called a service. These services are designed in a way to be loosely coupled and can be deployed independently which allows flexibility in scalability and faster deployments. This approach also increases the resiliency of the system. In this article we are going to talk about Microservices design best practices which must be considered while designing.

Please check Introduction to Microservices Architecture for more information.

(more…)
Microservices Design Best Practices Read More

Introduction to Microservices Architecture

Microservices architecture style is a way to design software applications by breaking down the complex software into multiple smaller, independent services. These small services are called microservices and software applications are built by combining multiple smaller services (or microservices) where each microservice will perform a specific function and it can communicate with other services as well.
In this article, we are going to discuss about the various advantages and disadvantages of microservices architecture.

(more…)
Introduction to Microservices Architecture Read More

Difference between TCP and UDP

UDP or User Datagram Protocol is the simplest connectionless transport layer protocol which simply sends packets between applications. It has very less overhead as UDP doesn’t require any session to transfer packets between applications.
Generally Real time protocols (RTP), DNS etc application uses UDP protocol.

TCP or Transmission Control Protocol is a reliable, connection-oriented protocol. TCP maintains a session between application and uses this session to send data across applications. TCP has support of acknowledgements of every packet being transferred and hence it’s reliable protocol but has higher overhead compared to UDP.
Generally FTP, HTTP etc application uses TCP protocol.

(more…)
Difference between TCP and UDP Read More

Network Address Translation Explained With Simple Example

Network Address Translation or NAT is a method to map multiple local private IP address to one or more public IP addresses. To achieve this generally a network device for eg: Router which is sitting in the private network, changes the source IP and port field of the IP header in a packet.

Since IP Addresses are limited (IPv4) and as internet devices are too large in number. Hence, NAT is used to apply one or more public IP addresses to a pool of devices present in a private network to save IP addresses.
Theoretically using NAT one public IP Address is sufficient for an ISP hosting a large number of subscribers.

(more…)
Network Address Translation Explained With Simple Example Read More

Diameter Agents Simple Explanation

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 Agents Simple Explanation Read More

Diameter Protocol Message Structure

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

Diameter Protocol Message Structure Read More