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 02, 2008
In this interview, InfoQ’s Chief Editor, Floyd Marinescu, interviewed Scott Ambler, Practice Lead for Agile Development at IBM, on the current status of the Agile community and practices having a look at the perspective of the Agile’s future.
Watch: Scott Ambler On Agile’s Present and Future (38 min.)
After introducing himself, Scott is invited to speak about his perception of the current Agile status. Scott remarks that most organizations are doing Agile projects. Some are even doing Test-Driven Development (TDD) and most agilistas are doing requirements or architecture modeling. An early conclusion: “Agile is here to stay”, according to Scott.
One subject touched in this interview was Agile in large distributed teams. While acknowledging that Agile has best results in small collocated teams, Scott considers that Agile is also suited for large distributed teams. The success rate is lower for such teams, but it is still a high number at about 60%.
After speaking about Rational Team Concept, an Eclipse IDE for distributed teams, Scott presented his view on closing the gap between business and IT departments. He agrees that the gap is going to be narrower, but he does not think the IT department is going to disappear any time soon.
After addressing the issue of modeling, its role and ways to be done by Agile teams, Scott offers a peak preview on the future of Agile as he sees it. He considers Agile as a step forward in software development, but we need to move to high-quality enterprise development.
Five Key Practices to Agile ALM
Transforming Software Delivery: An IBM Rational Case Study
SCM best practices for multiple processes, releases & distributed teams
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