Latest Posts

Micro services and Containers : 6 Things to know at start time

Micro services are a way to approach complex software designing through small easy services which has a specific role and purpose. These together helps in addressing larger complicated projects. Containers and Micro services are an ideal pair which acts together to perform various tasks like modular services which in turn may be used support different tasks.

6 things to know at start time

A solid plan and some new tools

The first thing to remember before moving on to container based micro services is to modify the existing tools for the purpose. Most of the time the existing tools are not cut out to perform. So a proper plan should have to be implemented before anything else. It is very easy to start a container based programme, however one has to continuously monitor and manage the process with utmost care. One has to keep in mind before implementing the services that it has to run smoothly when the project expands.


To manage the container based micro services one needs to have some sophisticated system like KUBERNETES. This can be got from cloud providers of some public domain or private players. However, it’s best to implement multifunctional tool that has generalised character, so that it is interoperable among various systems.

Service Discovery

Almost as the container based micro service is launched, it starts to search for other services. Manual intervention is minimal. That is why there is no question of IP address or host names. The container based micro service can register itself and is adaptable to changes and replacements.

Greenfield Project

It is very important to remember that it is highly advantageous to launch a brand new project. It is always good to start from scratches instead of remodelling a monolithic application. One is tempted to modify a monolith programme but it is a better option to start with a small Greenfield project. One can innovate and expand in this kind of project as there will be no restrictions from past application.

One micro service per container

The general rule about micro service is that it should function in a single platform and excel in that field. This rule has to be followed regarding the containers as well. There should be a proportionate balance between the micro service and the containers. The ideal condition is to provide one micro service per container. Microservices helps one to deliver in a short time. They also have a short life span, so keeping it clutter free is very important. One has to keep in mind the one-to -one rule as this characterise the combination of microservice and containers. However one has to keep the provision for computing and executing the memory too. The interdependency of the micro service and container helps in providing infrastructure services, along with the micro service and then clear the container in a clean way

Container Security

As the containers have system specific functions, they are very much vulnerable to the modern sophisticated ways of the technology which hinder the security. So much attention has to be given to tighten the loop holes of security.


Subscribe to Email Updates

Recent Posts