Operations | Monitoring | ITSM | DevOps | Cloud

Consider an E-Commerce Application with millions of users, built with various microservices. Since these microservices are decoupled, highly scalable, the communication and data sharing should be more reliable and seamless for business continuity. Here comes the Enterprise Service Bus technology. An enterprise service bus implements a communication system between mutually interacting software applications in a service-oriented architecture (SOA).

Nowadays APIs are the de facto method of communication between services. With all the connections points, setting up environments to efficiently build and test can be difficult. Also, in lower environments, 3rd party APIs can be unreliable, incorrect or non-existent.

Sometimes, as these 4 incidents highlight, major failure results from a mere typo or configuration oversight.

This post was written by Michael Knighten, Founder & COO of Sleuth There are some similarities between deploying continuously and driving in the fast lane. When driving, you need to be always on the alert, proactively looking down the road for potential hazards. When you see them, you need to be able to react immediately, hit the brakes, and change course nimbly.

When we talk about metrics in software delivery, a lot of developers think of execution metrics — things like throughput, delivery and number of deploys. But in reality, those metrics don’t motivate anyone — at least not without connecting them to a bigger picture. I’ve worked in software for 23 years. I’m a three-time founder and four-time CTO, responsible for leading a 200+ member distributed engineering organization.