Reply to post: use a transaction log on disc...

Splice Machine bags $9m to fund RDBMS on Hadoop and Spark


use a transaction log on disc...

That's my point. If you do that then you're not an "in-memory" database. All C/S RDBMS engines have read ahead buffering, LRU page caches and RAM based lock managers. Some also have MVCC (e.g. FireBird) and cache complex structures like views and OLAP cubes. No-one calls them "in memory" databases just as no-one (sane) calls MongoDB ACID.

I'm familiar with some of Stonebraker's papers. I've been using his stuff since Ingres on DEC Ultrix. As far as I know none of his work refutes any of this. Neither does Jim Starkey's stuff, and he disagrees with Stonebraker on many issues.

POST COMMENT House rules

Not a member of The Register? Create a new account here.

  • Enter your comment

  • Add an icon

Anonymous cowards cannot choose their icon