Microservices


You may have certainly come across this term, and may be curious what exactly it refers to. Okay I would say, this mainly refers to an architecture, which is used in developing software applications.

It’s more like implementing specific use cases, independently. That is the software is being decomposed into independently deployable, simple services that could cater a specific business need.

Microservice Architecture


These components may use different languages, technologies, frameworks etc. and finally can communicate each other via well-defined interfaces, or rather APIs. That is they communicate each other in a loosely coupled way.

This I would say, is ideal for large applications, providing better agility in the long term software development process. Especially when working with large teams, so now you can assign certain features of the app to certain team members. Also can scale fast unlike the monolithic architecture. 

If not for micro services, how can people like you and me would ever try to learn the code base of which something previously built? Because, this is very easier than learning/adopting to a monolithic code base.

As you see this is completely the opposite of the traditional way of developing a software application, where all the components of the software are interconnected and interdependent (i.e. in a tightly coupled architecture), also known as monolithic architecture.

APIs vs. Microservices


I would strongly say that APIs are not microservices.

By definition an API is an interface, built for the communication between 2 software components. While microservice architecture refers to break down of a software into smaller software components. Hence an API even could be an interface that expose the functionality of such components. And therefore they are 2 different concepts.

Comments

Post a Comment

Popular posts from this blog

What is an API?

Image
What exactly is an API? API stands for A pplication P rogramming I nterface. Perhaps some of you may have already used APIs in your software applications, which you may think that API is an already written piece of code dedicated to perform a specific task. Yes it is, but hold on! The API itself gives the actual meaning when it is read backwards.   an Interface used by Programs to interact with an Application. Essentially, an API could be anything in any form that is used by 2 software components to communicate with each other. Basically an API allows one application to talk to another, directly and securely. Some important facts about APIs will be listed below, No direct human usage of APIs. That is an API is normally invoked by some other code which is running on a computer. Normally this code is written by a developer to talk to the API. APIs expose something useful. You have APIs on your computer itself. (eg: when you type a key in the keyboard it gives
Read more

API Gateway

Image
This is needed when bringing all the microservices together, or rather this can be introduced as the entry point of the requests made by clients for each API service. All requests from clients first go through the API Gateway. Basically this abstracts the complexity behind the application you are going to build, so now the clients simply talk to the gateway to invoke specific services. The API Gateway is responsible for request routing, composition, and protocol translation.  Or rather this is an intermediate layer for the APIs and clients who call them, providing the functions listed below, authentication  authorization of API calls security throttling and rate limiting Proxy vs. API gateway Precisely, an API gateway is so much functionally richer than a proxy. Proxy provides you a new endpoint for an existing API and add some lightweight security and monitoring. The gateway, of course, still offers the same capabilities that an API proxy would offer for
Read more