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 Ryan Slobojan on Nov 06, 2007
The first release candidate of Spring 2.5, formerly known as version 2.1, was recently released. InfoQ spoke with Spring framework lead developer Juergen Hoeller to learn more about this release.
Hoeller told InfoQ that the final release of Spring 2.5 is currently scheduled for November 19th. The major features of this release are:
A comprehensive changelog is also available.
With Spring 2.5 nearing release, some people have compared it's performance to Google's Guice framework. Solomon Duskis compared the performance of Spring against Guice, and determined that Spring 2.5 was 200% faster than 2.0 for concurrent access, and faster than Guice when changing the default bean instantiation behaviour to singleton. Duskis also created a Guice-style Spring 2.5 application, and discussed his experience in detail. William Louth expanded upon this by doing a detailed comparison of Guice and Spring under several different configurations including concurrent access and singleton factory. Louth's analysis reveals that, in some configurations, Spring 2.5 is now faster than Guice, and overall the two frameworks are now much closer in performance.
Hoeller also discussed the plans for Spring 3.0 - a 2.6 release has been dropped, and 3.0 will be the next major release. The first milestone is expected to be available in May 2008, with a final release targeted for October 2008. The mimimum requirements will be Java 5 and J2EE 1.4, and Java 7 support is also possible. For Java 5 usage of Spring 2.5, the transition to Spring 3.0 should be seamless - however, older features such as Commons Attributes will be dropped since they are no longer relevant to Java 5. Spring 3.0 will also be repackaged, with possible inclusion of the Spring Web Services/OXM package and the binding/expression language package from Spring Web Flow in the core framework.
Improve Java Garbage Collection, Runtime Execution, and JVM visibility with Zing
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
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.
No comments
Watch Thread Reply