3 ms·
Wrap that up and abstract it as a transport system. The users don't need to know the inner workings, they just need a transport API that guarantees exactly-once
by dheera 2y ago
Wrap that up and abstract it as a transport system. The users don't need to know the inner workings, they just need a transport API that guarantees exactly-once.
- magicalhippo 2y agoThe point is you can't wrap that up, because the faults can happen at the edges, ie where the systems interact. The users still need to interact with this wrapped system, and it's those interactions that can fail, thus preventing the overall exactly-once delivery. To flip it around, if this wasn't an issue then what you're suggesting already exists in the form of ACID databases.
- orf 2y ago> they just need a transport API that guarantees exactly-once Which is the same problem, but at a different layer.