4 ms·
Most likely by not providing data safety and a bunch of features. The classic example with databases is that the super fast ones will report your writes are fin
by Strom 8y ago
Most likely by not providing data safety and a bunch of features. The classic example with databases is that the super fast ones will report your writes are finished even before the database starts thinking about writing the data to disk, not to mention flushing it.
- bobwaycott 8y agoAccording to this comment[0], it is ACID-compliant. What other data safety features are you thinking might be sacrificed? 0: https://news.ycombinator.com/item?id=18569031 https://news.ycombinator.com/item?id=18569031 More info on ACID & transactions here: https://golang.objectbox.io/transactions https://golang.objectbox.io/transactions
- Strom 8y agoBased on safety research [1][2] I’ve read on numerous databases, I’ve learned that there is almost always a big difference between vendor promises and reality. Thus when reading claims of order of magnitude performance gains against one of the most well tested databases in the world, I lean towards the assumption that the gains are due to shortcomings, whether intentional or not. — [1] https://aphyr.com/tags/jepsen https://aphyr.com/tags/jepsen [2] https://jepsen.io https://jepsen.io