Mainly because I get asked all the time about microservices and I'm tired of having to remember on the spot: What is a microservice? A microservice is a service with a design focus towards the smallest autonomous boundary. What is a service? (From Clemens) A service is software

When you move from monoliths to microservices, and your services aren't 100% isolated from each other, eventually you need your microservices to communicate. They need to expose their capabilities to other applications and systems, and when you get to this point, you need to design their means of

Posts in this series: * A primer * Composition options * Client composition * Server composition * Data composition In the last post, we looked at possible areas of composition: * Client * Server * Database In this post, we'll look at compositional options in the browser. From the outset, I can at least confirm that

Posts in this series: * A primer * Composition options * Client composition * Server composition * Data composition In our previous post, we looked at why we might compose, seeing it's primarily an edge concern, where we're exposing our services to end users. Those end users could be customers, or

Posts in this series: * A primer * Composition options * Client composition * Server composition * Data composition Microservices can be easy, if we never have to compose, orchestrate, or otherwise integrate between multiple services. If our inter-service communication is low, we can piecemeal a solution based on basic integration patterns such as messaging.