This post is from an on-going series from our engineering blog, Shift6, which features developer-focused content. For the first part of the Redox Microservices Journey series, click here; for the second, click here.
At Redox, we're taking a pragmatic approach to building microservices, especially in how we handle cross-cutting concerns. Most refer to this part of a microservice ecosystem as the chassis—things that every microservice needs to have in order for us to be confident that it's a quality product. The chassis includes: