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 Abel Avram on Aug 23, 2008
In this presentation filmed during Agile 2008, David Anderson talks about the history of Agile, the current status of it and his vision for the future. The role of Agile does not stand in just having a practice, but in finding ways to implement the principles contained by the Agile Manifesto.
Watch: Future Directions for Agile (1h 32min).
David presents the paradigms behind the principles of the Agile Manifesto and Lean. He is not content with just doing what the Manifesto says, but he wants to understand why it makes sense doing it. One such example is related to the principle "Working software over comprehensive documentation". In the past, people wanted to document everything ending up with huge amounts of documentation which could not possible be efficiently used. For example, he says that the RUP documentation amounts to 11,000 pages, while the Fujitsu process documentation covers 100,000 pages, all of that in order to create the perfect process. We need to discover processes and practices which do not rely so heavily on documentation.
David discusses a great deal about Lean, Kanban, Real Options, and CMMI, comparing them with Agile. His purpose is to draw attention to other ideas, in an attempt to make the audience aware of other options available to us, so we don't get stuck with some practice, but use new ways to extract more value from the original Agile principles.
Case Study: IBM's Agile Transformation
18 agile and lean practices for effective software development governance
Agility at scale, become as agile as you can be
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!
I liked Anderson's query at the end: when people make proposals to this conference for these new ideas... will we let them in? or not?
Good question.
This is really 4 or 5 presentations in one. Extremely dense and high quality. David explains the real values behind the Agile manifesto (he "modelizes" Agile), compares Agile with Lean, then sells Kanban and finally CMMI. Definitely fine food for thought. I had to listen to it twice to start getting the key messages. Highly recommended presentation for whoever wants to understand where Agile is/should be heading.
Great talk! Would love to work with a David and others to develop these principles, practices, and community and take them to new areas of innovation, leadership and management outside the software practice. Please see a 90% Transcript of David Anderson's Future Directions for Agile.
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.
3 comments
Watch Thread Reply