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 Mark Levison on Dec 04, 2008
Building on the success of last year’s metaphor of festival with multiple stages, the Agile Alliance is taking the same approach this year, reducing their number from 17 to 14. The idea behind the stages is to make what has become a large conference a smaller place so that sessions with similar themes will end up on the same stage. For those whose area of interest is focused (i.e. New to Agile/Adopting Agile), they will end up seeing many of the same people throughout the conference, making a 1600+ persons event seem smaller.
This year’s program chair, Ahmed Sidky, says: “We welcome submissions for research papers, experience reports, panels, workshops, tutorials, and activities for any of the above-mentioned stages. You are invited to submit ideas and proposals for sessions via our online submission system, which will be available mid-December”.
Next year’s stages are:
Changes to the list include the addition of: Agile Adoption, Agile Product Management, Coaching and New to Agile. Missing next year are: Breaking Acts, Chansons Françaises (French language stage), Committing to Quality, Live Aid, Musik Masti and Questioning Agile. Some in the Kanban Community are disappointed at the loss of the Breaking Acts and Questioning Agile Stages. David Anderson says “If there is no "breaking acts" stage, what is the community doing to encourage innovation?”
Like this year, the submission system will utilize “The Wisdom of the Crowds” – all submissions will be open for review and ratings by the public and submitters will have a chance to respond and update their work. While the submission deadline is Feb. 13th, submitting sooner will give one a chance for more feedback.
On InfoQ: Agile 2008 Coverage
Transforming Software Delivery: An IBM Rational Case Study
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!
The links to the stages are all broken - please can you update them to match the ones at agile2009.agilealliance.org/welcome ?
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