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 Dave West on Jul 06, 2009
Atlassian has released version 2 of Fisheye (a source code repository browser) and Crucible (code review tool). Both tools have revamped UI as well as added features. Most apparent in Fisheye 2 is a kind of "social networking" aspect that allows developers to follow and interact with the team as well as the work. Crucible 2 introduces and supports the idea of iterative code reviews.
The combination of the updated UI with the social networking capabilities leads to support for four major features of Fisheye 2:
Crucible 2 adds a number of features that allow you greater control over your code review process. You can establish a review process that is right for your organization, flexibly determining: pre/post commit review options and setting activity notifications, permissions, due dates, reviewers, and defect classifications. These improvements are intended to enhance support for an iterative (asynchronous) review process:
Conducting asynchronous code review typically leads to an iterative process. Crucible lets you update the contents of a review while it is under way. Updating an existing review, helps reviewers see fixes in the context of the discussion that instigated the change. It also saves later reviewers from reviewing the redundant code altogether.
Both tools emphasize the ability to integrate with other tools, both those from Atlassian (notably JIRA and, of course with each other) and those from other vendors, e.g. Eclipse and IntelliJ. Both tools supply RESTful API's and plugin frameworks so you can 'roll your own' integration.
Not too long ago, the agile community, especially its founders, resisted the idea of automated agile tools in favor of tangible artifacts like story cards and big visible charts. Increased reliance on automated testing, the need to support teams that were not co-located, and the need to support Agile@Scale has significantly reduced the anxiety about other kinds of automated agility tools. It is nice, however, when a tool vendor demonstrates a sensitivity to Agile philosophy and principles in the design of their tools - something that Atlassian seems to have done in a very conscious manner. Agile is a people-centric approach to software development, with communication and feedback among team members and between the team and the code an absolutely essential principle. The announced enhancements to Fisheye 2 and Crucible 2 support this principle.
SCM best practices for multiple processes, releases & distributed teams
A practical guide to choosing the right agile tools
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.
1 comment
Watch Thread Reply