logoalt Hacker News

jmulltoday at 6:27 PM1 replyview on HN

This is an excellent idea who's time has come.

But this is too vague for me. I'm not seeing my questions answered in the landing page or FAQ either.

E.g.,... what's the pricing?

How does atomic commit really work? E.g., if one write to S3 succeeds but the update to a git repo fails?

Does this use optimistic locking or something else? What happens if I commit changes to a resource that was updated since it was imported?

Where/how is it hosted?


Replies

ozkatztoday at 6:35 PM

Regarding pricing - that's indeed a great question and we don't have an answer yet. It will very likely be based on consumption and should be competitive to similar solutions.

Atomic commits are based on snapshotting done by lakeFS under the hood. Each sandbox run produces a new atomic commit to a hidden "main" branch. Updating that branch is optimistically concurrent, with lakeFS checking for conflicts - multiple writers updating the same object.