olivermrbl

4 ms·

1.
ACID transaction orchestration in composable architectures(medusajs.com)
5 points by olivermrbl 3y ago|0 comments
2.
We designed an API with a Git-like control flow(medusajs.com)
10 points by olivermrbl 4y ago|0 comments
3.
by olivermrbl 4y ago
> What would happen if the orchestrator was unable to update the remote shared cache outbox after a local exception/rolled back transaction To be sure, I understand your question, you are referring to the following scenario: - Start
4.
by olivermrbl 4y ago
Thanks for chiming in! Although I appreciate your detailed walkthrough of Inngest (sounds amazing), I wonder if it is the right fit for us. One of our guiding product principles is to always build framework agnostic solutions, allowing our
5.
by olivermrbl 4y ago
On the alternative solution, it's worth stressing, that it does not have to be a cache service. Any key/value store would do.
6.
by olivermrbl 4y ago
Yes indeed. Attaching below a couple of references from my exploration: Transactional outbox pattern: - https://microservices.io/patterns/data/transactional-outbox.... - https://softwaremill.com/mi
7.
Ask HN: What are best patterns for events in distributed transactions?
42 points by olivermrbl 4y ago|12 comments
8.
by olivermrbl 4y ago
Don't hesitate to reach out. We are amid extending our B2B capabilities, so it would be super interesting to learn about your client's requirements. And your own.
9.
by olivermrbl 4y ago
Medusa is a headless API, so you are free to consume it from wherever you want whether it be a React-based storefront, a C# backend, or something third - there's really no limitations. But the source code of the open-source project is
10.
Ask HN: What are essentials elements in an enterprise commerce stack?
1 points by olivermrbl 4y ago|1 comments