> …until you need to market to people who didn't get a shipping last month, delay shipping until at least one recharge attempt, or ship before charging for customers you're reasonably sure will pay anyway.
These are all very simple things to handle when services encode processes instead of entities
> Business changes
Yes, and then you throw away the code for that outdated process and encode the new one.
> One global database buys you a lot
Absolutely, this is the correct choice for probably 95+% of companies. I will always argue in favour of a monolith and single database.
If someone is dead set on microservices though, they'll avoid a world of pain by actually designing them properly
These are all very simple things to handle when services encode processes instead of entities
> Business changes
Yes, and then you throw away the code for that outdated process and encode the new one.
> One global database buys you a lot
Absolutely, this is the correct choice for probably 95+% of companies. I will always argue in favour of a monolith and single database.
If someone is dead set on microservices though, they'll avoid a world of pain by actually designing them properly