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 Amr Elssamadisy on Jun 20, 2008
In the now classic book by Martin Fowler, Refactoring: Improving the Design of Existing Code, Kent Beck co-wrote a chapter on smells that begins with this quote:
If it stinks, change it. Grandma Beck, discussing child-rearing philosophy.
There is something very attractive about seeing symptoms of something going wrong as a smell. The idea has since caught on and been used to describe more than design problems; it has been incorporated into our notion of Agile practices - and what happens when things go wrong.
Mark Levison wrote an interesting blog summarizing some of the work that has been done to catalog Agile smells. Here are some smells you might recognize:
There are many other smells listed, and they vary in quality/style by author. This is a mark of maturity in our community as we look back and learn from our years of experience.
Some related works to Smells are Patterns. Jason Yip has written about Stand Up Meetings as a pattern format, Mike Cohn has written about Patterns of Agile Adoption, and Amr Elssamadisy has written Patterns of Agile Practice Adoption: The Technical Cluster (which is available for download here on InfoQ) and Agile Adoption Patterns: A Roadmap to Organizational Success. The work on patterns, similar to those on smells, builds on our communities experiences by bringing us common ways that teams have succeeded AND common ways they have failed.
As our community grows, documenting our years of experience for others that are adopting Agile practices will be increasingly important. Smells and Patterns are great ways of doing so.
Transforming Software Delivery: An IBM Rational Case Study
Case Study: IBM's Agile Transformation
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!
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.
1 comment
Watch Thread Reply