4 ms·
Also relevant: http://www.bailis.org/blog/how-to-make-fossils-productive-again/ http://www.bailis.org/blog/how-to-make-fossils-productive-ag... Choice quote f
by fizwhiz 8y ago
Also relevant:
http://www.bailis.org/blog/how-to-make-fossils-productive-again/ http://www.bailis.org/blog/how-to-make-fossils-productive-ag...
Choice quote from there:
> Kill the reference architecture and rethink our conception of “database.” The article titled “Architecture of Database System” should be considered harmful. If a system doesn’t have a buffer pool, it can still be a database, and, in fact, I’d prefer not to read any more papers on “databases” that have buffer pools. Instead, I’d prefer you shock me with your radical, new (and useful!) conception of a data management platform.
- ignoramous 8y agoYes. And this paper by Stonebreaker et al was the catalyst for that kind of thinking: http://www.vldb.org/conf/2007/papers/industrial/p1150-stonebraker.pdf http://www.vldb.org/conf/2007/papers/industrial/p1150-stoneb... and his presentation: https://youtu.be/DJFKl_5JTnA https://youtu.be/DJFKl_5JTnA Also, see this blog post: http://www.dbms2.com/2008/02/18/mike-stonebraker-calls-for-the-complete-destruction-of-the-old-dbms-order/ http://www.dbms2.com/2008/02/18/mike-stonebraker-calls-for-t...
- js8 8y agoI wonder how this would compare to things like IMS. It's one of few non-relational databases quite widely used for OLTP, and it has a reputation of (possibly) being really fast.
- dvirsky 8y ago> 1. No disks or other persistent storage at all. > 2. No multi-threading. > 3. No locks. > 4. No redo logs (and perhaps not a lot of undo logs either). Well, 3/4 Redis!