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 Apr 06, 2009
RunCodeRun is a hosted continuous integration service for Ruby projects on GitHub and is developed by Relevance.
Why a hosted continuous integration service? Rob Sanheim in his announcement blog post:
Social source control has been a major factor in open source for a long time, but GitHub really elevated the game. It makes setting up source control for your project dead simple, and eliminates the front-end IT pain of managing a project. That still leaves continuous integration, the back-end IT pain, up to the team. We want CI to be as automatic, and as easy, as source control, and the way to do that is a hosted solution.
RunCodeRun is still in a private beta, but you can take a look at various open source projects that are being built or apply for an invite.
InfoQ talked to Rob Sanheim to learn more about RunCodeRun: The public projects all seem to use GitHub. Is RunCodeRun only usable with a GitHub project?
We're dogfooding RunCodeRun, starting first by building the system we want to have and use. We are all huge users and supporters (and paid users!) of GitHub, so that led us to starting with them. We have plans to go beyond GitHub and Git itself, but for right now its just GitHub.
Can you tell us something about how RunCodeRun is implemented?
We use Rails on the front end, with our own custom builders on the back end. We are using Amazon's EC2 to scale builders up and down as need dictates.
Is it possible to build a project with different Ruby versions? And when will it be available for the general public?
Yep, all these things are coming as soon as we can get to them.
Besides just building and running tests (even against multiple Rails versions), RunCodeRun can also measure code coverage with rcov.
For more information, subscribe at the site or read the RunCodeRun blog.
Transforming Software Delivery: An IBM Rational Case Study
Case Study: IBM's Agile Transformation
SCM best practices for multiple processes, releases & distributed teams
Maximize your business-responsiveness with Mingle. Provide your global development team a shared space that adapts to the way they work.
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