Microservices at LeanIX - then, now and tomorrow

Fittingly, LeanIX’s Dominik Rose (Director Customer Success Engineering) and Per Bernhardt (Staff Software Engineer) arrived on stage after Nagamalli to share several customer-based perspectives on LeanIX Microservices Intelligence and to share Microservices Enterprise Architecture Examples. The two emphasized that microservices only really work when paired with clear objectives, and by using LeanIX Microservices Intelligence, a clear boundary is scoped to ensure enterprises don’t fall into the trap of “deployment monoliths”.

From a business perspective, Rose made it clear that monoliths are an inevitable element of any fast-growing business and take time to degrade. Because of the many microservices architecture variables, patience is required, and although autonomy is a perennial goal for business efficiency, it takes a long time to establish microservices enterprise architecture systems of observability via iterative software designs. Apart from that, Rose recommended that teams do their best to measure qualities such as "mean time to recovery," "frequency of use," "lead time," and "failure rate.

The two ended their presentation by giving EACD audiences a closer look at LeanIX Microservices Intelligence and how the tool can perform such qualitative measurements on microservices. With ways to conform to the diversity of technologies used by developers, the tool provides visibility for development teams while also guaranteeing that information conforms to data security standards. Rose pointed out how useful this can be when making decisions on the trade-offs common to any microservices development and deployment process.