8 ms·
Or that one microservice holding up the other 10,000 microservices keeled over :)
by consoomer 3y ago
Or that one microservice holding up the other 10,000 microservices keeled over :)
- ranting-moth 3y agoBut microservices are standalone services. Anyone who correctly implements ms wouldn't make it depend on other ms or get it shipped to prod anyway. Edit: /s
- consoomer 3y agoRight... I'm sure that's what happens.
- sp332 3y agoI would actually love to know if you have done this in prod and what it looked like.
- jdc0589 3y agoI've seen people try and do it. It involves each service replicating copies of the data from every service it's dependent on (via CDC streams on kafka/whatever) in its own datastores and reading directly from its copy of data rather than actually calling the source-of-truth service. There are some instances where that kind of thing is necessary, but...insane amount of clear downsides so your problem statement for doing it had better be pretty compelling.
- nullandvoid 3y agoThis is typically referred to event carried state transfer for anyone curious. The premise being high service availability and low latency to serve requests (no need to talk to source of truth) with the tradeoffs of higher storage / processing costs and from my experience higher complexity.
- btilly 3y agoI'm trying to figure out the odds that you intended this as sarcasm. In the real world, it doesn't work like that.
- ranting-moth 3y agoSarcasm indeed.
- resonious 3y agoAnyone who correctly implements a payment service wouldn't make it go down for 7 hours.
- tklinglol 3y ago[dead]
- kikimora 3y agoThis is brilliant :)