– Janis Kondrats, CTO at Anatomy Next
In short, a microservice architectural style is an approach to developing a single application as a suite of small services, each running in its own process and communicating with lightweight mechanisms, such as HTTP API. These services are built around business capabilities and independently deployable by fully automated deployment machinery. There is a bare minimum of centralized management of these services, which may be written in different programming languages and use different data storage technologies.
Whereas the system as a whole may live for a long time, its components – the containers – do not. They live and die quickly.
This new situation presents new challenges to many areas of software engineering. One of them is monitoring – how can an operator make sure that a system remains healthy if existing monitoring tools are unable to function in this new reality?
In this case, we were challenged to develop a service for real-time monitoring environments that are built on the principle of microservice architecture. Environment Overseer’s functionality includes configuring the environments, builds and micro-services, as well as user managing and monitoring of micro-services’ status in the media pane.
Service finds the root cause of the microservice architecture problem and allows to solve it as soon as it possible.