DEV Community

Discussion on: Don't code your microservice like a monolith, keep it maintainable not over-engineered

Collapse
 
bgadrian profile image
Adrian B.G.

Thank you for the TLRD.

Speaking of the subject, I saw a talk recently
in which gave an example of monolith-services, which had only 1 instance and communicating sync with the other monoliths. It was a horror image, never thought that someone could achieve that :)

Also like the talk said, micro services were created to scale an organization, and less about the code (See Amazon 15yrs ago). If you have less then 100s developers the operational overhead of services will be a big % of your workforce, that if you do not use managed services like AppEngine and such.

Collapse
 
geshan profile image
Geshan Manandhar

There are multiple ways to look at it. In my previous work we were 10 backend devs and 2 devops/SRE people responsible for ~150 microservices running on k8s. At the end it is generally about code ;).

Collapse
 
bgadrian profile image
Adrian B.G.

Sounds great, is there an article or talk about it somewhere? Sounds like a good win over a complex problem. Most of the stories I know had 10devs only for operational glue at that scale.

Thread Thread
 
geshan profile image
Geshan Manandhar

I can write a talk if this topic deserves more attention :) thanks!