3 ms·
What about ACID? How far do you plan to divert from it?
by ComodoHacker 10y ago
What about ACID? How far do you plan to divert from it?
- Normal_gaussian 10y agoThis is the most important question in my mind. If it isn't ACID it needs to make a very strong case for itself to even be played with by most DBA's, including myself.
- Ericson2314 10y agoDepending on details, content addressing could make it very hard to not be ACID. Here's to hoping.
- aboodman 10y agoYes, it kind of falls out of content-addressing. See: https://news.ycombinator.com/item?id=12722023 https://news.ycombinator.com/item?id=12722023
- senand 10y agoMore specifically, what isolation guarantee do you make? Are writes linearizable? What consistency guarantees do you claim? How well do you think you will do when reviewed by aphyr (https://aphyr.com https://aphyr.com)?
- aboodman 10y agoYou should understand that Noms is doing something quite a lot simpler than the systems that are usually reviewed on Aphyr. Noms doesn't manage its own storage - it relies on an underlying key/value store that must provide strongly consistent reads for at least one key. In other words, we delegate most of the hard part to somebody else. With that all said... Currently our intent is that: - Transactions that read and write from a single dataset have strong serializability - Transactions that read from multiple datasets and write to a single dataset have snapshot isolation - Transactions that write to multiple datasets aren't possible In the future, we will probably allow additional configuration, such that, e.g., one could choose snapshot isolation within a dataset for additional concurrency, or strong serializability for transactions that span datasets.
- botw 10y agocurious on how the irregular black shape title bar is created?