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 Scott Ambler on Jun 07, 2006
The Essential Unified Process (Ess UP) is a streamlined version of the UP which, as the name implies, captures the essential practices required to be successful on a UP project. At the Rational Software Development Conference (RSDC) this week Jacobson overviewed the work being done within his company. The Ess UP describes an agile approach to development following the UP. As Jacobson succinctly put it: "These days, saying that you're not agile is like saying that you're not potent".
Seriously though, key points which Jacobson made about the Ess UP:
Case Study: IBM's Agile Transformation
A Guide to Branching and Merging Patterns
agility@scale eKit: 10 Principles, Scaling Model, Metrics, Collaboration
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!
We also need intelligent agents, such as what we see with JacZone's Waypointer, to help guide and mentor IT professionals as they do their job.
I watched Ivar's presentation on Intelligent Agents at the excellent JAOO conference in Norway last year. The vision of having a little agent helper guy training you on your computer didn't seem like something people would want to do. Ivar claimed however that using an agent could allow for having a very huge process, because the agent would simply present parts of it when necessary only, making use of the process more consumable.
Hi Floyd, I was at JAOO too, although I was in Denmark, not sure about you ;-).
I agree with what you say. When Ivar mentioned these Intelligent Agents I wrote "Microsoft clippy?" in my notes. If I remember rightly, he didn't think that they would be just for coders, but for all parts of the project. I had visions of a little character popping up and saying "Hey, it looks like you're project managing a J2EE project, would you like help with that?".
Speaking with other delegates and speakers, I didn't find anyone who thought it sounded a good idea. So I don't think this idea will fly.
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.
2 comments
Watch Thread Reply