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 Mike Bria on Feb 04, 2008
We are always seeking ways to help our customers simplify the delivery of software. Our new interface ensures simplicity of use for all users - from the developer who only wants to see his or her work to the “power user” needing to leverage the broadest array of functionality. All key functionality is one click away, making the application much easier and more effective to use than a bunch of spreadsheets.
VersionOne’s unique Intelligent Release Forecaster tool enables teams to do “what if” analysis as part of the ongoing planning process. A project manager is able to input key parameters of the project, such as velocity, to accurately forecast the release delivery date with confidence. This is especially important to project managers in enterprise organizations demanding ongoing status and forecasting of delivery schedules.
VersionOne provides all integrations as open source software via the VersionOne community site. Interested customers and partners can download the source code to further customize integrations for their unique environment. Also available are existing integrations with tools such as Visual Studio, Subversion and FitNesse. Unlike other Agile tool providers there are no hidden charges for use of the integrations, providing a much lower total cost of ownership of a VersionOne solution.
Agile Development: A Manager's Roadmap for Success
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!
I used VersionOne on a recent project and it was a god awful mess. Specifically, there are way too many options for stories and it was overly difficult to re-create a sprint plan.
My overall impression with the product was one of surprise: surprise that a supposedly "agile" development team would produce such an overly complicated product.
Thankfully, on my current project, everyone is co-located so I'm back to using Excel to manage my backlog.
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