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 Rob Thornton on Feb 01, 2007
Stephen Colebourne has announced JSR 310, a new Date and Time API, to be based on Joda-Time and hopefully shipping in Java 7. As the JSR reads, the goal is to provide a more advanced and comprehensive model for date and time than those found in the Date and Calendar APIs.
Colebourne is the Project Lead for Joda-Time, and he states that while the JSR will be influenced by Joda-Time, it will not be a rubber stamp of it. Alex Miller lists some of the problems of the current API, from the perspective of working with JDBC drivers.
Colebourne has solicited input in a thread on JavaLobby. Some of the feedback that has already come in includes:
The question of compatibility with existing Date and Calendar classes has also come up, with some saying it is necessary and others saying that at the most there should be a helper class for conversions.
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
Monitor your Production Java App - includes JMX! Low Overhead - Free download
I think this is long overdue. Joda-Time is a very good library and we have suffered for so long at the hands of the JDK Date classes.
As long as this includes good JDBC integration this should be a win for everyone. We have used joda-time almost exclusively but having to perform conversions to and from JDBC calls is awkward.
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.
2 comments
Watch Thread Reply