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 Paul Blair on Mar 30, 2010
With a recent announcement from Nick Quaranto, RubyGems.org has become the default gem source for RubyGems. The three domains gemcutter.org, gems.rubyforge.org, and rubygems.org now all point to the same place, and gem serving and installation work for all three. RubyGems.org is the main web front end, to which the other two sites redirect. The secure site, https://rubygems.org, also went live on March 23.
Hosting approximately 11,500 Gems, RubyGems.org is now the default Gem host for the community, superseding both RubyForge and GitHub. GitHub announced in October that it would no longer automatically build Gems, and that it would only host existing gems for a year; it recommended Gemcutter for hosting. Shortly thereafter, the teams behind Gemcutter, RubyGems and RubyForge announced that RubyForge would be phased out in favor of Gemcutter, which would take the name RubyGems.org.
Gemcutter appeared last year as a repository aiming to simplify the hosting and release of Gems. With the gemcutter RubyGems plugin, a simple gem push command would publish a Gem to the repository; this functionality has now become part of the RubyGems package manager with the 1.3.6 release. The only change in RubyGems relevant to the downloading and installation of Gems is the use of RubyGems.org as the default repository.
For publishers of Gems, user accounts from RubyForge have been merged over to RubyGems.org; users new to the site but with existing RubyForge accounts can log in with their RubyForge account information.
The focus of RubyGems.org is Gem hosting; other features of RubyForge, such as website hosting, file hosting, bug tracking, forums, and mailing lists, are being retired in deference to other hosting sites that specialize in such features. Support for the RubyGems package manager, however, as well as for the RubyGems.org site as a whole, is available at help.rubygems.org. This site features knowledge base articles, forums, and issue tracking.
While the gem push and gem owner commands have been merged into the RubyGems package manager, the gemcutter plugin continues to exist and makes available several additional commands. The gem yank command will remove a Gem from the RubyGems.org index while leaving it available for download; by using gem webhook a user can be notified about Gem updates by registering a URL to be called each time a gem gets pushed.
Some other features of the RubyGems.org site include a "Metrics" button on each Gem's page that links to Caliper, which generates metric_fu results for every pushed gem. RubyGems.org also makes available a web-based API for creating and querying Gems, for managing owners, and for various other interactions with the site.
Agile Practices to Improve Project Management Organization (PMO) Effectiveness
Agility at scale, become as agile as you can be
SCM best practices for multiple processes, releases & distributed teams
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