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 Deborah Hartmann Preuss on Aug 17, 2006
True, most firms now try to use metrics such as internal rate of return, return on assets, net present value, or activity-based costing. But besides customer satisfaction there's no consensus or consistency on which measures to use. It's still not a given that ROI should be measured both before and after a project. And half of all executives surveyed, whether IT or business executives, doubt that the measures are even accurate.Findings include:
Transforming Software Delivery: An IBM Rational Case Study
18 agile and lean practices for effective software development governance
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!
Every failed IT effort to get ROI from making something more efficient Ive seen didnt take into account current business practices sufficiently and just said well if I plop this system down I will save money.
For example, having business process engineering folks going to satellite offices and coming back with a suggestion for a "new system" when the computers the users are using are crashing or operating so slowly they can barely do their jobs. Yeah, a new application is JUST what they need.
Or companies using IT apps as a political ploy to unify operating practices between satellite offices and putting the home office stamp of approval on an application while ignoring the needs of the majority of the company.
What does ROI mean if your software effort is doomed to fail and usually does?
Maybe ROI should be second to success. Because ROI has been used to justify so many software failures. Maybe ROIs time is up.
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