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 Miko Matsumura on Sep 08, 2006
Despite these struggles, SOA seems to be a significant committment for these organizations. The Information Week survey shows that two out of three of the companies currently engaged in SOA expect their spending on it to increase over the coming year. The survey says that nearly half (45%) of survey respondents rate SOA projects as "very important to their companies' business goals."
During times when the going gets tough, it's important to ask why organizations are committed to SOA in the first place. 72% of the respondents in the information week survey indicated "Increased flexibility in application development". 61% indicated "Ability to create service-oriented business apps faster" and 58% indicated Increased software modularity. A surprising 55% indicated "Better integration with business partners."
Discuss.
Probably the initial investment and complexity is huge but once the services/components in the SOA get reused wouldnt it reduce both cost and complexity drastically? Are there any surveys that have interviewed companies which are in advanced stages of SOA implementation?
-Jeevak
Sometimes I wonder if there are any companies that are in advanced stages of SOA implementation :-) Those who claim to be, like Deutsche Post or Credit Suisse, cite significant cost savings. But as usual, it's hard to find proof, especially because it's not easy to find a meaningful comparison.
There's a Joe McKendrick post on SOA "reuse":
blogs.zdnet.com/service-oriented/?p=699
H.Ozawa
I think now we have to ask ourselves What is SOA?
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.
4 comments
Watch Thread Reply