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 Deborah Hartmann Preuss on May 31, 2006
SirsiDynix best practices are similar to those observed on distributed Scrum teams at IDX Systems, radically different than those promoted by PMBOK, and counterintuitive to some practices advocated by the Scrum Alliance. This paper analyzes and recommends new best practices for globally distributed Agile teams... It is extremely easy to integrate Scrum with XP practices even on large distributed teams. This can improve productivity, reduce project risk, and enhance software quality. What is new in this paper is that single teams with members distributed across sites can enhance code ownership and improve autonomy essential to team self-organization.This is a very informative case-study. The article briefly reviews the history of Scrum, including the some historical "hyperproductive teams" made possible by use of Agile practices. It then outlines the practices used on the SirsiDynix project, including the way progress was measured. He finishes with some comparative productivity statistics on Waterfall, Scrum and SirsiDynix projects, using function points. You can read Adaptive Engineering of Large Software Projects with Distributed/Outsourced Teams online in the Proceedings of the 2006 International Conference on Complex Systems.
Transforming Software Delivery: An IBM Rational Case Study
Agile Development: A Manager's Roadmap for Success
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