1 Sentence Summary: Building Microservices allows us the opportunity to tackle software complexity and deliver faster; if (and it’s a big if) we build our services right: choosing the right tech, interfaces, and integration patterns.

Microservices are a way of breaking down applications into their parts so that businesses can deliver the components separately, experiment with distinct technology stacks, and create clear boundaries between business logic.

But building microservices isn’t easy an easy task. With microservices, you need to consider many things, such as how (and where) you split the services, how they talk to each other (integration), and what data they share.

It’s in-vogue at the moment to debate on the virtues of Microservices vs. Monoliths. But ultimately they’re just two different architectural patterns that solve different use cases. Ideally, you should understand both patterns.

Here are my three big takeaways:

• An architect is a town planner
• Microservices are data abstractions
• Independently deploy services