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 Scott Delap on Jan 03, 2007
Groovy is a dynamic language for the JVM that integrates seamlessly with the Java platform. It offers a Java-like syntax, with language features inspired by Smalltalk, Python or Ruby, and lets your reuse all your Java libraries and protect the investment you made in Java skills, tools or application servers.
Uses of Groovy include the Grails web application framework, XWiki, and Spring 2.0 scripting integration.
2007 is shaping up to be a important year in the evolution of the Groovy language. A number of books either have been released (Groovy in Action) or a slated for publication this year. Last month Big Sky Technologies announced the launch of the aboutGroovy.com portal and the funding of Jochen Theodorou to work full time on Groovy development.
Monitor your Production Java App - includes JMX! Low Overhead - Free download
Using Drools? See what you're missing! Get the Power of Drools with the Assurance of Red Hat
Improve Java Garbage Collection, Runtime Execution, and JVM visibility with Zing
I really wonder, why you've removed RIFE from the enumeration as found in the original press release (while preserving the comma ;))?
RIFE's wonderful and it's nice integration of Groovy is really worth to be mentioned.
RIFE has been a long time user of Groovy, and Geert's feedback has also always been very interesting. He even helped us test drive this final release, to be sure no nasty bugs were lying around. RIFE is a great framework that deserve the good press and increased usage that arose the past year. Congrats Geert for such a great framework!
Thanks a lot for your kind words Guillaume, but this announcement is about Groovy!! You finally made 1.0, CONGRATULATIONS!!!
You've come a long way and since you're leading the show, Groovy has steadily improved to what it is now. It's a pity that 3 years ago things were announced too early and too soon so that some people nowadays have the wrong impression. Actually, you should have named this GroovyNG (next generation) ;-)
Actually, you should have named this GroovyNG (next generation) ;-)
I trademarked the "NG" suffix in the Java world, my lawyers will be in touch shortly.
--
Cedric
Actually, you should have named this GroovyNG (next generation) ;-)
I trademarked the "NG" suffix in the Java world, my lawyers will be in touch shortly.
--
Cedric
hehehe
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.
5 comments
Watch Thread Reply