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 Ben Hughes on Mar 12, 2008
Agile Commons is an on-line, agile software development community designed to help fuel the drive and innovation of teams adopting and scaling agile. The road to agile is road of incremental and continuous improvement or Kiazen. To stay on this road, Agile Commons is designed to facilitate the sharing of ideas across organizations and support the continuous improvement teams need to avoid “giving up” or “settling for amateurism” in the form of just a modest improvement.He goes on to say:
Agile Commons is also home to a number of sub-communities:The platform originally enabled Rally to respond to customer requests and hosted discussions, however as it has now become host for Chris Spagnuolo's rapidly growing and star studded Agilistas community. By inviting cross organisational, cross community groups, agilecommons.org seems to be breaking new ground in assembling a diverse, socially aware, agile community resource.
- Rally Commons is for Rally customers to gain visibility and provide feedback into the usage, release and value of Rally's software capabilities.
- Agile University Commons is for student and instructors to share materials and collaborate prior to and following their courses.
- Agilistas Community is open to the Linked-in Agile group formed by Chris Spagnuolo.
Five Key Practices to Agile ALM
Transforming Software Delivery: An IBM Rational Case Study
Case Study: IBM's Agile Transformation
Maximize your business-responsiveness with Mingle. Provide your global development team a shared space that adapts to the way they work.
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.
No comments
Watch Thread Reply