Zephr Coffee Club #8 - Micro-Service vs Monolith - May 21, 2020

It's Thursday, 3pm BST and 10am EDT, so that means the Zephr Coffee Club was back up and running! This week we were talking about everything Micro-Service, Best of Breed and Monolith - well anything you could get into a 30 minute coffee club!

Monolithic - in this context, means composed all in one piece. Monolithic software is designed to be self-contained; components of the program are interconnected and interdependent rather than loosely coupled as is the case with modular software programs. In a tightly-coupled architecture, each component and its associated components must be present in order for code to be executed or compiled.

Micro-Service - solve the same challenges of monolithic systems but by being as modular as possible. In the simplest form, they help build an application as a suite of small services, each running in its own process and are independently deployable. These are best-of-breed approaches and enable flexible and agile deployment.

Is a Monolith the right call?

For some people, and some businesses, a monolith is the right approach - it’s simpler, and easy for a small team with low budgets and who are short on time to manage. 

However...

- FAILED IMPLEMENTATION RISKS THE BUSINESS
- GETTING STUCK WITH BAD TECH ISN'T GOOD
- FIXING SOMETHING THAT’S ALWAYS BROKEN SUCKS

Basically net-net, it's a trade-off needed between simplicity and flexibility. To find out more, we've just released a whitepaper on this very subject - Do you need a Micro-Service or a Monolith?

Topics: Coffee Club

   

Comments