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 Robert Bazinet on Jun 02, 2008
Ruby on Rails 2.1 was released this past week at the annual Ruby on Rails conference, RailsConf. This year the event was held in Portland, OR and the announcement came as many people expected.
The announcement was made official by Jeremy Kemper, Rails core team member, at the end of his talk at RailsConf. Details of the release are outlined on the Riding Rails blog and include the following:
None of these features stand out as the killer feature for this release but instead represents a group of steady, solid improvements focusing on pain points for many developers. Installing the update is straightforward and should go without issues.Rails 2.1 is now available for general consumption with all the features and fixes we’ve been putting in over the last six months since 2.0. This has been a huge effort by a very wide range of contributors helping to make it happen.
Over the past six months, we’ve had 1,400 contributors creating patches and vetting them. This has resulted in 1,600+ patches. A truly staggering number. And lots of that has made it into this release.
New features
The new major features are:
- Time zones (by Geoff Buesing): Tutorial | Introdction | Railscast
- Dirty tracking: Introduction (partial updates) | Railscast
- Gem Dependencies: Introduction | Railscast
- Named scope (by Nick Kallen): Introduction | Railscast
- UTC-based migrations: Introduction | Railscast
- Better caching: Introduction
Thanks to Ryan Daigle for the feature introductions and Ryan Bates for the Railscasts. It makes writing the release notes so much easier :).
As always, you can install with:
gem install rails...or you can use the Git tag for 2.1.0.
The announcement includes Railscasts to show the main new updates which gives developers a visual look at what is new, before they update their Rails installations.
More information about this release are available on the Ruby on Rails web site.
Agile Development: A Manager's Roadmap for Success
Agile Practices to Improve Project Management Organization (PMO) Effectiveness
18 agile and lean practices for effective software development governance
there aren't any killer features in this release...
I disagree.. I think the time zone stuff is amazing. Any time you build a web app that shows when things happen, and have more then one timezone, life gets very hard. And I think the time zone support that Ruby has is pretty rough (www.opensourceconnections.com/2007/04/09/figuri.... So putting a great timezone layer into Rails seems to me to be one of those great "Why I use Rails: Time Zones!" kind of features.
Well, this is a killer feature for someone needing it but it is not a huge feature for everyone, only when it's a pain point for some users. Each feature here seems to be that type of update, but that is my opinion.
Probably there are no killer features, but they really help a distributed development team. Especially the "gem dependencies" and the "utc-based migrations" will make things much easier as soon as more than one developer is working on a project (as well as deployment).
Personally, my favorite feature are "named scopes" (aka has_finder). I love them! ;)
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.
4 comments
Watch Thread Reply