3 ms·
The problem with monoliths is that they're written fast and chock full of business logic that isn't reusable anywhere else. With microservices, if done correct
by lubesGordi 5y ago
The problem with monoliths is that they're written fast and chock full of business logic that isn't reusable anywhere else. With microservices, if done correctly a la hasura, your business logic is abstracted to config, or to the highest level of abstraction your business allows.
- sparker72678 5y agoI have never been in an environment where business logic could come even remotely close to being definable via config, even if config was some kind of fancy DSL. Every product I've worked on had deep interdependencies between major parts of the code _at least logically_, because _that was the product_. At some point you can't factor out the business logic anymore without factoring out the entire business, in my experience. This is a major reason software is so tricky. Still, I'm fascinated that this could exist somewhere. Have you seen it in the wild?