4 ms·
I guess in memory means that it never writes data to the disks. So what happens when the machine reboots?
by braindead_in 16y ago
I guess in memory means that it never writes data to the disks. So what happens when the machine reboots?
- cx01 16y agoFrom the FAQ: "Durability: VoltDB provides both replication of partitions (known as K-safety) and periodic database snapshots to ensure the availability of the data."
- mmagin 16y agoTheir FAQ states: Durability: VoltDB provides both replication of partitions (known as K-safety) and periodic database snapshots to ensure the availability of the data. I suppose it depends on your definition of "D". Seems like this might be acceptable if you had different replicas on different power sources, etc.
- jws 16y agoI expect there is a persistent store of some sort, you'll have to register to find out. I'm also unable to find a license without registering. It does appear from the FAQ that you build your transactions as Java stored procedures. Constraining a generic SQL database that way will make it much easier to distribute and scale.
- deleted 16y ago[deleted]
- tlack 16y agoIn-memory DBs can take a lot of excellent shortcuts but I have to wonder if their usability is limited. After all, I'd think most interesting data sets end up quickly eclipsing the available RAM in most off the shelf/affordable servers.
- cx01 16y agoKeep in mind that VoltDB targets the OLTP market, where datasets tend to be not that large. If you build a small cluster of 50 nodes with 256GB RAM each, you have about 4.3TB of storage (with a replication factor of 3).