Ask HN: How are you solving the microservices data problem?
I've seen suggestions to use a database/datasource per microservice, even if data is duplicated in those various locations. I'm interested in hearing what people who use many microservices in production are doing to solve this problem. MDM? A database microservice? Cron?
(
7 comments
| 4 points
| on HN
)
So what used to be 4 lines of code with a shared SQL db now requires at least 2 services which have to have corellation Id based logging to give you a fighting chance of working out what goes wrong, centralised log store, separate containers, monitoring, configured orchestration for the containers and some sort of communication between them ... what's not to love?
PS I'm apparently a buffoon and use microservices for even the most trivial side project
What specifically is the problem you're trying to solve?