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 Dec 29, 2008
In this original presentation from the Communitech Agile Event, Jeff Patton, winner of the Agile Alliance’s 2007 Gordon Pask Award, explains why one needs to embrace uncertainty in order to succeed with his/her Agile project and how to avoid some of the common mistakes leading to project failure.
Watch: Embrace Uncertainty by Jeff Patton (1 hour)
After a quick introduction to Agile, Jeff presents some practices, what they actually mean and how they are supposed to be used, in an attempt to counteract the failure of Agile projects due to misconceptions and misunderstandings. One of the first misunderstood practices to address is iteration. Iterate is not increment, says Jeff. Increment requires having a complete idea about the final product, like in this image:
Iterate allows one to “build a rough version, validate it, then slowly build up quality”, as in the image below:
Jeff takes a stand against “possible shippable product at the end of an iteration” approach. He considers it frightening, freezing creativity and the positive development of a product.
Jeff quotes Fred Brooks, author of the article No Silver Bullet: Essence and Accidents of Software Engineering, developing his conception: “The hardest single part of building a software system is deciding precisely what to build.”
The conclusion of the presentation, accompanied by famous singers’ photos and song clips, is the recommendation to embrace uncertainty.
Transforming Software Delivery: An IBM Rational Case Study
Agile Development: A Manager's Roadmap for Success
18 agile and lean practices for effective software development governance
Maximize your business-responsiveness with Mingle. Provide your global development team a shared space that adapts to the way they work.
wanted to know how could i start wit a project regarding online shopping
as i need to use asp or jsp and all possible details..
plz do reply to this
i would be very thankful to u
Good talk! Was a little worried that the talk would just be about introducing Agile development yet again but.. no, it went beyond that. Jeff introduced one thing that the Agile manifesto missed completely, and techniques to avoid delivering crap applications, late. (I would add that Architecture should be addressed the same way in order not to be overlooked). "Embrace uncertainty" could be read "First, learn what your users will appreciate".
If you have to build an application that is to deliver features that you don't know exactly how they will work yet (from the user standpoint), then watch this! Or go straight to Jeff's blog at agileproductdesign.com/blog/emerging_best_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.
2 comments
Watch Thread Reply