Getting into microservices seems easy at first glance. You may have a feeling that behind the horizon stands new danger for your ROI. Code becomes obsolete and hard to maintain. But you, reader, should know best that requirements always change. Those small, pretty small pieces of software that conquered the Monolith, split it into pieces and made changes to software easy again. And then out of nowhere Microservices arrived. The Monolith, the big, the scary, the unchangeable, the breakable, the Return of Investment (ROI) eater. We have no idea which was first: the chicken or the egg, but we know that the Monolith was the igniter of changes that we observe every day in IT. When properly used, ELK has the potential to reduce these risks and help you deliver quality in an efficient way. Microservices bring plenty of opportunity for a more efficient approach to creating software products, along with some drawbacks and potential risks.
In the following article we will explore the capacity of the ELK stack to get the most from a microservices approach to software development.
