New-age Transactional Systems - Not Your Grandpa's OLTP
John Hugg discusses high volume transaction processing applications with high and low frequency profiles, and how VoltDB can be used for that purpose.
The content has been bookmarked!
There was an error bookmarking this content! Please retry.
Posted by Werner Schuster on May 24, 2007
I’m really stoked about this. I think rubinius has so much potential that I am really happy to be able to support it. Starting next month Evan Phoenix is going to be working here at EY half time on ey [EngineYard] tools and such and half time on rubinius.He follows with a quick explanation of Rubinius:
For those of your who aren’t familiar with rubinius you can read a bit more about it here. It’s a new implementation of ruby done in a smalltalk style with a small core VM written in C and almost everyting else written in ruby. Really, even String and Array and definied in ruby. Rubinius is going to open up core ruby hacking to the masses as the internals won’t be a bunch of gnarly C code thats really hard to grasp.It's important to point one thing out: with Evan Phoenix being paid to work on Rubinius, all Ruby implementations (Ruby, JRuby, IronRuby, Rubinius) now have paid developers working on them.
18 agile and lean practices for effective software development governance
Agile Maturity Model Applied to Building and Releasing Software
Improve Java Garbage Collection, Runtime Execution, and JVM visibility with Zing
Using Drools? See what you're missing! Get the Power of Drools with the Assurance of Red Hat
If the C core is really small it would be dead easy to reimplement it in say, Java and we'd have JRubinius! or .Net Rubinius!
Awesome!
Don't forget XRuby. The main developer, dreamhead, was also picked up by ThoughtWorks.
Of course. In fact, we are seriously considering including a Rubinius-runtime with JRuby, since that would be quite easy and also yield large benefits.
As a small matter, I was hired by ThoughtWorks with the mandate of working about halftime on JRuby too. =)
Yes... actually, the JRuby team was considering supporting Rubinius bytecodes (because that would allow to re-use Rubinius' Ruby -> Bytecode compiler). I'm not sure what the current status of that idea is.
Yes... actually, the JRuby team was considering supporting Rubinius bytecodes (because that would allow to re-use Rubinius' Ruby -> Bytecode compiler). I'm not sure what the current status of that idea is.
Yes, of course, Thanks for mentioning XRuby.
Yes. Blimey, the group of Ruby implementers is growing by the day.
Is there an official name for a group of Ruby implementers... you know, like "gaggle of geese" or "flock of seagulls"... how 'bout: "a Hashtable of Hackers" ...
all Ruby implementations (Ruby, JRuby, IronRuby, Rubinius) ? all ?
The CLR implementation from Dr Wayne Kelly's team at Queensland University of Technology that's been around quite a long time now.
rubydotnet.googlegroups.com/web/Home.htm
www.infoq.com/news/2008/01/johnlam-responds (to IronRuby v Ruby.NET)
John Hugg discusses high volume transaction processing applications with high and low frequency profiles, and how VoltDB can be used for that purpose.
Kevlin Henney examines code samples to see what can be learned from them starting from the premise that one won’t write great code unless he knows how to read it.
Jason Ayers share the observations he made watching a team of developers collaborating in real time on the same code base, pushing XP, pair programming and continuous integration to their extremes.
Michael Snoyman presents Yesod, a web framework written in Haskell and containing a web server, templating, ORM, libraries (templating, gravatar, etc.).
Richard Kreuter and Kyle Banker on how to avoid classical RDBMS transactional systems by using compensation mechanisms, transactional messaging or transactional procedures.
Attila Szegedi talks about performance tuning Java and Scala programs at Twitter: how to approach GC problems, the importance of asynchronous I/O, when to use MySQL/Cassandra/Redis, and much more.
One category of risk that project teams need to ensure they address is business value failure – delivering a product that fails to provide value for the business investor.
InfoQ spoke to the authors of Software Systems Architecture on a couple of new topics, the System Context viewpoint and Agile, which have been added to the second edition.
10 comments
Watch Thread Reply