115
Death by a thousand microservices
(renegadeotter.com)
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 12 Sep 2023
115 points (96.0% liked)
Programming
17326 readers
239 users here now
Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!
Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.
Hope you enjoy the instance!
Rules
Rules
- Follow the programming.dev instance rules
- Keep content related to programming in some way
- If you're posting long videos try to add in some form of tldr for those who don't want to watch videos
Wormhole
Follow the wormhole through a path of communities !webdev@programming.dev
founded 1 year ago
MODERATORS
Microservices are a reflection of Conway's law. You can bend it with multiple services masquerading as a monolith. But you can't break it and when you need to decouple deployments, data releases, and development across a fairly large org: they're hard to beat. Of course OP is right, just call them services too. One per team is about as much as you want to break out, don't go micro