Enterprise Caches Versus Data Grids Versus NoSQL Databases
RedHat/JBoss Manik Surtani:
[…] If you want to compare distributed systems, both data grids and NoSQL have kind of come from different starting points, if you will. They solve different problems, but where they stand today they’ve kind of converged. Data grids have been primarily in-memory but now they spill off onto disk and so on and so forth and they’ve added in-query and mapreduce onto it while NoSQL have primarily been on disk, but now cache stuff in-memory anyway for performance. They are starting to look the same now, or are very similar.
One big difference though that I see between data grids and NoSQL, something that still exists today, is how you actually interact with these systems. Data grids tend to be in VM, they tend to be embedded, you tend to launch a Java or JVM program, you tend to connect to a data grid API and you work with it whereas NoSQL tends to be a little bit more client server, a bit more like old-fashion databases where you open a socket to your NoSQL database or your NoSQL grid, if you will, and start talking to it. That’s the biggest difference I see today, but even that will eventually go away.
They seem to converge, but:
- spilling off to disk is not equivalent to optimized disk access
- distributed, sometimes even transactional caches are not equivalent with single node caches
Original title and link: Enterprise Caches Versus Data Grids Versus NoSQL Databases (©myNoSQL)
