just so we're clear. I did read the article, but not the linked paper.
> I spent a fair amount of time visiting engineering teams that have built internet auctions, most of which were transactional systems where taking a position on an item involved starting a transaction, running an auction round and committing the changes.
That sounds pretty straight forward, where are the pain points?
>In contrast, we chose to deliver a simpler, eventually consistent system on top of MongoDB, in which all data is immutable and where some level of serialization occurs within a single background process.
why was that simpler? what was stopping you from just inserting records instead of updating them? and why did it matter that serialization occurs in a single background process?