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 Feb 18, 2010
Less than a year since the last Ruby on Rails release and over 4000 commits later, the beta of Rails 3.0 has been released.
The increase in the version number from 2.3 to 3.0 is well-deserved, considering that Rails 3 is not just a bunch of enhancements but actually a merge of Rails 2.3 with its former rival Merb, to combine the best of both worlds:
There are all the good ideas brought over from when the Merb team joined the party and brought a focus on framework agnosticism, slimmer and faster internals, and a handful of tasty APIs.
Besides the many internal cleanups, there are of course also new features. From the release notes:
Another area that got much attention is security, as Yehuda Katz explains in an interview with SD Times:
We went through the known remaining security vulnerabilities based on having spoken to Twitter and having them say 'your security tools are too manual right now.' [To prevent cross-site-scripting vulnerabilities ..] we went through all of Rails' internals and marked the form tags as safe, which means that for the vast majority of cases, users won't have to do a lot. [..] it's now almost impossible to have an accidental XSS attack.
To read more on Rails 3.0, the detailed release notes cover the changes in great detail. Yehuda also wrote a retrospective over the last year, giving a high-level summary (compared to the release notes) of the changes. Jeremy McAnally started a series in his blog "about moving your skills and migrating your code to Rails 3". The first part starts with a high-level view on the changes Rails has undergone; the second part is called "approaching the upgrade". RubyInside has a collection of 36 links on Rails 3.0.
Rails 3.0 works both with Ruby 1.8.7, 1.9.2, as well as JRuby. Rails 3 on IronRuby doesn't work yet because the current IronRuby trunk (which will soon be released as 1.0) is focused on 1.8.6 support - Rails needs some 1.8.7 features. After IronRuby 1.0, the project will switch to 1.9 support which should then support Rails 3. At the moment there's a discussion on the IronRuby-core mailing list whether to add 1.8.7 support to IronRuby 1.0 to get Rails 3 to work.
To find out whether you could try to upgrade your applications to 3.0, the new RailsPlugins.org maintains a directory of plugins and their 3.0 compatibility.
A date for the final release has not yet been announced. What do you think about Rails 3? Have you already tried to upgrade your applications?
Federated Identity Management and Single Sign On
Agile Development: A Manager's Roadmap for Success
Complimentary Gartner (Hype Cycle for Cloud Security) Report
Agile Practices to Improve Project Management Organization (PMO) Effectiveness
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