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 Nov 05, 2009
Caliper provides metrics for Ruby projects, and it couldn't be any easier: just point Caliper to your Git repository, wait for a few seconds, and see how fit your code is.
Caliper is a free service provided by Devver, the company known for their test acceleration service (see Faster Ruby Test Execution With Devver on InfoQ). The calculation of the various metrics is done by metric_fu, wich in turn uses tools like Roodi (warns about design issues) and Saikuro (a cyclomatic complexity analyzer). Caliper aggregates all these data and provides a nice overview. For an example, take a look at these Sinatra hot spots.
Benjamin Brinckerhoff from Devver told us that they plan to integrate even more metrics:
We're not entirely sure which ones we'll add yet. This largely depends upon the responses we hear from our users. However, here are some ideas.
When we add these tools, we plan to add them to metric_fu as well (assuming the metric_fu teams agrees they would be good additions!). In the meantime, we're working hard to make the existing metric_fu data easier to understand and work with.
- Towelie, detects duplication, similar to Flay.
- rcov, already included in metric_fu, but not yet supported by Caliper.
- Railroad, class diagram generator.
- TODO detector, determines which files have the most instances of TODO (or other strings that serve as programmer notes). The exact strings would be customizable, we'd likely build this ourselves (it should be fairly easy).
Just calculating the metrics isn't enough, the code should also be refactored afterwards. This blog on Devver shows how Caliper's metrics were used to improve its own code base. Caliper also integrates well with other services like GitHub and rdoc.info via post-commit hooks.
The service is free for open source projects, a paid service for private projects is being considered.
Case Study: IBM's Agile Transformation
Five Key Practices to Agile ALM
In today’s hyper-competitive world, later may be too late to adopt Agile development and this Roadmap for Success will help you get started. Download "Agile Development: A Manager's Roadmap for Success" now!
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