> There's a lot of cool things you can do when you treat documents as > state machines. Also, getting a view of "complete" bookings will be > easy. > > Docs as state machines also works well in a multi-master environment, > where you want to watch for "events" to be replicated to redundant > storage.
I've been using document state to allow some operations to be idempotent - this has been working well. But I felt less comfortable using state to effectively demarcate transactions. Your reply has given me greater confidence with this approach. Thanks Chris. Paul
