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 Jul 15, 2008
New Relic announced that 37signals—the company behind Ruby on Rails—uses their Ruby on Rails performance management solution RPM to keep the performance of their applications humming.
Since April 2008, 37signals has relied on New Relic RPM to standardize performance management for all its applications. With New Relic, 37signals isolates and fixes any performance problems fast—before customers find them. "After we installed New Relic, we learned that Highrise [their web based CRM] response times were considerably higher on a few key actions than we'd like," said Rails inventor and 37signals partner David Heinemeier Hansson. "We spent some time optimizing and confirmed through RPM that we had achieved a 50% speedup on those key actions."
We wanted to know, if their findings led to changes in Rails. David Heinemeier Hansson answered:
None of the findings caused any changes in Rails. It was merely pointing out that we were doing some inefficient things, which once highlighted were obvious to rectify. I don't have any more information than we received an overall 50% speedup on those affected actions.
More information, including an interview with Lew Cirne—New Relic's CEO—can be found in this InfoQ article on Rails performance analysis with New Relic.
Rails developers can try RPM for free, and upgrade to a paid subscription when the application enters production.
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