By Cameron McKenzie
via theserverside.com
Published: May 12 2011 / 20:11
When I talk to people that have high performance, highly transactional systems, there’s often this embarrassed pause when I ask how they are doing these many, many, many thousands of transactions per second. And all too often the answer is that it’s a hash table with a lot of RAM and a log file. And people tend to not think of RAM and Hash Tables as a database; but it is, and it works really, really well. And it’s not embarrassing.
Comments
zynasis replied ago:
server crashes. data lost.... yay...
a1programmer replied ago:
Write better software ?
Cameron McKenzie replied ago:
@zynasis
That was my original thought too, that this scenario is great say for data where perhaps it's just temporary, like perhaps Terracotta's BigMemory object store or something like that where you're tracking runtime objects, but certainly the suggestion is for highly transactional systems. My assumption is the log file Gosling talks about is used to track changes, manage consistency and recover from failures?
Cameron McKenzie replied ago:
Here's more insight from Gosling. It's a somewhat amusing rant on Java 1.4.2 users. Check it out and give it a +1.
http://www.dzone.com/links/james_gosling_tells_java_142_users_to_get_with_th.html
Cameron McKenzie replied ago:
ooops...
Voters For This Link (8)
Voters Against This Link (1)