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 Oct 26, 2006

"[the responses to similar questions] 2 or 3 years ago would primarily would have been from small teams - we've seen an uptake in the size of teams adopting or considering adopting Agile... roughly a third of responses were from organizations of 250 or more. [size of software organization]."Holler suspects that we're not yet nearing the end of this increase in adoption:
I think any time you're talking about a fundamental change in the way people do business, we're talking at least a double-digit time frame, at least ten years. ...maybe five years ago it was primarily developer-led, and then two or three years ago, team-led, now we're seeing a lot of management- and project-management-led, and I think the future is going to be executive-led.In fact, this survey seems to show that, in contrast to the early years of the Agile movement, Agile methods are now almost as likely to be championed by a member of senior management as by grass roots leaders like team leads and architects:
What role most closely identifies the initial champion of Agile development within your organization?The full results of the survey are available online, as well as in a .pdf download, on the VersionOne site.
28% VP / Director of Development 18% Project Manager 13% Team Lead 11% President / CEO 7% Architect 5% CIO 5% Consultant
18 agile and lean practices for effective software development governance
Agility at scale, become as agile as you can be
A practical guide to choosing the right agile tools
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!
There's a question I don't see anyone asking on surveys yet: How many have "unadopted" Agile?
This might be difficult to ask on a survey - it's a retrospective-style question which is best asked in an open-ended manner: "What didn't work?" However, information about teams that either throw out Agile wholesale, tweak it beyond recognition, or no longer want to use the term Agile could be interesting, if we want to learn about what's happening with adoption.
deb
Deb,
That's an interesting thought. Maybe the questions should try and highlight how much teams value agile principles. For example, one question may be "Does your whole team sit together?" This might identify how teams value communication. Another question might be "How often do you deploy working software". This might identify how teams value delivery working software as opposed to documention. These questions might invoke an honest answer which would then give a deeper insight as to how agile teams really are.
Warren
Lets try that again.
Deb,
That's an interesting thought. Maybe the questions should try and highlight how much teams value agile principles. For example, one question may be "Does your whole team sit together?". This might identify how teams value communication. Another question might be, "How often do you deploy working software?". This might identify how teams value delivering working software as opposed to documentation. These questions might invoke an honest answer which would then give a deeper insight as to how agile teams really are.
Warren
I would love to hear suggestions such as this for questions. I'm going to repeat my agile adoption survey in the new year and definitely intend to rework the questions. It will make comparisons difficult but I hope to get better quality data.
It's really hard to design a good survey, and an evolutionary approach is a good strategy in the long run.
- Scott
Practice Leader Agile Development, IBM Methods Group
Note: there's further conversation on this subject at the ScrumDev list
groups.yahoo.com/group/scrumdevelopment/message...
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.
5 comments
Watch Thread Reply