Link Details

Link 598677 thumbnail
User 772253 avatar

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.
  • 8
  • 1
  • 2616
  • 0
User 211643 avatar

zynasis replied ago:

1 votes Vote down Vote up Reply

server crashes. data lost.... yay...

User 200690 avatar

a1programmer replied ago:

0 votes Vote down Vote up Reply

Write better software ?

User 772253 avatar

Cameron McKenzie replied ago:

0 votes Vote down Vote up Reply

@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?

User 772253 avatar

Cameron McKenzie replied ago:

0 votes Vote down Vote up Reply

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

User 772253 avatar

Cameron McKenzie replied ago:

0 votes Vote down Vote up Reply

ooops...

Add your comment


Html tags not supported. Reply is editable for 5 minutes. Use [code lang="java|ruby|sql|css|xml"][/code] to post code snippets.

Apache Hadoop
Written by: Piotr Krewski
Featured Refcardz: Top Refcardz:
  1. Play
  2. Akka
  3. Design Patterns
  4. OO JS
  5. Cont. Delivery
  1. Play
  2. Java Performance
  3. Akka
  4. REST
  5. Java