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 Sep 18, 2006
In 2003, Mary and Tom Poppendieck's Lean Software Development introduced development techniques that adapt the principles of Lean manufacturing and logistics (like the Toyota Production system, which revolutionized the automobile industry) for use in software development.
Since the publication of the first book, the benefits of lean and agile software development have become widely known and appreciated, and the Poppendiecks have traveled around the world, visiting organizations as they implement these new approaches, and continuing to learn from their interaction with people working to improve the way they develop software. Still, demand for further information has led to their second book, Implementing Lean Software Development: From Concept to Cash, which offers a companion guide: a blend of history, theory, and practice which shows exactly how to implement Lean software development, hands-on.
The new book draws on the their extensive experience helping development organizations optimize the entire software value stream, an important approach which Mary practiced years ago at 3M, where software development is seen as as simply one part of the entire product development process, or "value stream". They present the right questions to ask, the key issues to focus on, and techniques proven to work.
In the exclusive InfoQ book excerpt, Chapter 2: Principles, the authors look at how manufacturing and supply chain management differ from IT, and how they needed to adapt Lean's basic ideas to the characteristics of software development. They then discuss each of the seven principles they developed: Eliminate Waste, Build Quality In, Create Knowledge, Defer Commitment, Deliver Fast, Respect People, and Optimize the Whole:
The authors point out that a lean organization optimizes the whole value stream, from the time it receives an order to address a customer need until software is deployed and the need is addressed. They point out that, if an organization focuses on optimizing something less than the entire value stream, it's almost guaranteed that the overall value stream will suffer. This is a major theme of the book, which offers the tools to root out sub-optimization and other forms of inefficient process.18 agile and lean practices for effective software development governance
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!
Hi, the link to the sample chapter is broken,...
Thanks,
Eric.
Links work for me... what browser are you using? Pls send further details to me at deborah a t infoq d o t com - I'll see what I can do. Thanks for letting us know.
Hi Deborah,
I tried this link in both Firefox and IE
www.infoq.com/resource/news/poppendieck-impleme...
and got a:
"Oops! The server couldn't find the requested information" message.
Anyway, I can wait for the book, I have pre-ordered it 3 months ago,...
Solved. Thanks for your patience.
www.infoq.com/resource/news/poppendieck-impleme...
is broken. Monitoring comment logs for strings like broken/error can make it easy to manage forums like these.
BR,
~A
Uh oh, there were two links, only one got fixed. Done.
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.
6 comments
Watch Thread Reply