Monitoring If you have ever seen a shell game play out in a heist movie, you can relate to the monitoring challenges that microservices can present. When dealing with monolithic applications, you typically interact with one deployment and one database. In the movie, this is the jewel thief in the red jacket fleeing the museum; he’s easily identifiable. In the same way, monitoring the monolith is simple, with only a few hosts and log files to analyze. With the microservices architecture, there tends to be many services and databases that are elastic, scaling and disappearing as required. This is where hundreds of jewel thief decoys in red hoodies flood the streets, presenting more red jackets to complicate the scene. In microservices, it becomes harder to keep tabs on everything that is happening within the system and to pinpoint where something is breaking. Monitoring is where leveraging the proper tools becomes necessary. If you can automate monitoring, logging and the aggregation you can significantly simplify the process. Even better, you can take advantage of a user interface (UI) that visualizes your microservice application to watch that automated masterpiece do its thing. Deployment The microservices approach presents many different types of services, often written in different languages and with different dependencies. Various services may require different versions of Python, some might be in Java and be dependant on the JVM, and some might be a simple Go binary. Though we’ve all met a birthday party magician who could prove otherwise, every coin has two sides. This is microservices’ double-sided coin in that the best-suited technology for a service can be used (advantage), but that each of these must be installable and runnable in an environment (challenge). This is why container based technologies such as Docker have become so popular. They act as a wrapper around an application, containing libraries and runtime settings as if a dedicated host. Now, developers can ship a fully executable container, simplifying deployment to a single operational concern.
You can take advantage of a user interface
(UI) that visualizes your microservice application to watch that automated masterpiece do its thing.
© 2017 PROVENIR ALL RIGHTS RESERVED
Made with FlippingBook Digital Publishing Software