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 Mirko Stocker on Mar 17, 2010
The revised schedule for the Ruby 1.9.2 release has been announced today (an earlier schedule targeted December 2009 for a release, but had to be delayed because of various RubySpec failures). A few weeks back, Ruby 1.9.2 finally passed all RubySpec tests. The new schedule now looks as follows:
The spec freeze that is due in two weeks will freeze the list of features that might get included in the release. These features then need to be implemented before the code is frozen at April 30, otherwise the feature will be excluded from the release. After that, another month is spent on stabilizing the release, eventually resulting in the preview2 release. The following release candidate will be delayed "as long as any bug tickets remain". If everything goes well, that is, if no new bug reports appear after 1.9.2-p0, the final release should be due in mid-August.
so what is the estimated release date of ruby 2.0, will it take 2 more years?
I promise to write about it as soon as I have any information on it :-)
But it might happen sooner than expected, Ruby 1.9.3 could already be 2.0: twitter.com/yugui/status/5739171454
"p0" means the official release. What do you mean by "the final release"?
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.
3 comments
Watch Thread Reply