Ask HN: How do you deal with atomicity in microservice environments?
We run a small SaaS where users are able to create accounts, submit billing information and upload/call ML artefacts. In order to not reinvent the wheel we use external services where possible: Auth0 for authentication, Stripe for handling billing, etc. For this question, I am considering this a 'microservices' architecture. I am aware that this definition will spark its own discussion, but I believe that the problem generalises to a lot of the other (better, more complete, etc.) microservice definitions. So please, bear with me. Now, in the lifecycle of a customer (createAccount, addBilling, deleteAccount, ...) at various points we expect operations to occur atomically. By which I mean (simplified) that upon creating a new account, I also need to ensure a customer is created in Stripe as well as register the user in Auth0 - but if either of these subtasks fail, the operat
Why it failed
We run a small SaaS where users are able to create accounts, submit billing information and upload/call ML artefacts. In order to not reinvent the wheel we use external services where possible: Auth0 for authentication, Stripe for handling billing, etc. For this question, I
- Kind
- startup
- Status
- Shut down
- Inventor
- c89X
- Ended
- 2019
- Source
- hackernews