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 Peter Cooper on Sep 07, 2006
Charles Nutter reports that he and JRuby co-developer Thomas Enebo are becoming employees of Sun Microsystems later this month. JRuby is a pure Java implementation of the Ruby interpreter and Nutter reports that Java are backing a "Ruby-on-JVM" strategy:
The potential for Ruby on the JVM has not escaped notice at Sun, and so we'll be focusing on making JRuby as complete, performant, and solid as possible. [..] I'm also making it a personal priority to continue growing the JRuby community, foster greater cooperation between the Java and Ruby worlds, and work toward a "whole-platform" Ruby-on-JVM strategy for Sun.
Nutter also reports that JRuby will remain open-source, despite being under Sun's custodianship, although Sun is rapidly becoming a proponent of open-source software with Sun's process of open-sourcing Java itself.
InfoQ has also just released a video / slide presentation of Nutter and Enebo demonstrating and showing off the power of JRuby.
Getting Started with Stratos - an Open Source Cloud Platform
Fair Trade Software Licensing - A Guide to Neo4j Licensing Options
Improve Java Garbage Collection, Runtime Execution, and JVM visibility with Zing
In today’s hyper-competitive world, later may be too late to adopt Agile development and this Roadmap for Success will help you get started. Download "Agile Development: A Manager's Roadmap for Success" now!
How do you think this move will affect groovy's fate?
Well, if Sun does the right thing they'll let a thousand flowers bloom.
If they'd endorse jruby more than groovy I'd understand that: ruby's momentum is undeniable.
It is god from Sun to do this, but I whish thy add done the same for Jython
I don't think something good for JRuby has to be bad for Groovy. It's likely that dynamic languages on the JVM are a growth area. And competition is good and should be encouraged in general.
I think this is a very encouraging move from Sun. The JVM is bigger than Java.
Btw Spring 2.0 supports the authoring of components in both JRuby and Groovy, as well as other languages (and the mechanism is extensible). See the chapter on dynamic language support from the reference manual.
Well, I did not imply that Groovy will die a horrible death because Sun hired JRuby core developers.
But in our fast moving world, full of hype and shadows, a delay of one single year in delivering a solid platform could mean much. Remember that Rails is related to (J)Ruby as Groovy is related to Grails. Groovy and Grails are younger and imature but IMHO Sun could help here at least as much as they go with JRuby.
Floyd Marinescu has an argument for this desirable support for Groovy( Grails ) here: www.infoq.com/news/groovy-jsr6-interview#view_1245. But no luck yet.
Maybe some Google employees could help Groovy because they can spend 1 day in a week working on pets projects, right?
"making JRuby as complete, performant, and solid as possible"
I've been giving talks about SOA, XML and performance to developer audiences and when it comes to an adjective to describe a software application's ability to deliver good performance I've found myself saying "performant"... As in, the software is functional and performant.
Unfortunately performant is not in dictionary.com or any of the other dictionaries I use. A performant is a noun describing someone on stage, like an actor. But it is not yet recognized as an adjective for offering good performance.
I'd like to promote the use of performant because it seems like a natural use of the root word performance.
-Frank
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.
6 comments
Watch Thread Reply