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 Oct 12, 2006
According to the SOA Reference Model document itself, a reference model is an abstract framework for understanding significant relationships among the entities of some environment. It enables the development of specific reference or concrete architectures using consistent standards or specifications supporting that environment. A reference model consists of a minimal set of unifying concepts, axioms and relationships within a particular problem domain, and is independent of specific standards, technologies, implementations, or other concrete details.
The reference model defines SOA as:
Service Oriented Architecture (SOA) is a paradigm for organizing and utilizing distributed capabilities that may be under the control of different ownership domains.
Now SOA has a standardized reference model, thanks to the work of OASIS SOA-RM technical committee. According to an email sent to the OASIS Reference Model Technical Committee, Duane Nickull, chair of the TC notified the group's status on the standardization vote as follows:
The Ballot to advance the Reference Model for SOA to become a full OASIS Standard received 89 positive votes, the second highest number of positive votes anyone on the TC can recall being cast to support a standard. The single no vote came from Avaya Inc. The sole statement provided by a representative from that company was:
"Too vague and confusing, e.g. things which are not SOA can be mapped into this and claim they conform to this SOA model."
Despite this sole dissenting vote, the techical committee, after approaching Avaya with a formal letter and expressing an interest to resolve any issues with the spec, the Technical Committee decided to move ahead according to the OASIS rules and move to a standard with a final tally of 89 organizations supporting, one against.
The Reference Model can be downloaded here:
http://www.oasis-open.org/committees/tc_home.php?wg_abbrev=soa-rm
Those Avaya guys, they're smart. I honestly don't know what value, exactly, the RM provides ...
Also notice noone from Microsoft, IBM or Oracle on the membership list. This lack of major vendor leadership or support always concerned me.
Service Oriented Architecture (SOA) is a paradigm for organizing and utilizing distributed capabilities that may be under the control of different ownership domains.
I find this definition surprising as I've never heard SOA described in this manner anywhere else. No mention of loose coupling, no mention of standard protocols, etc. I'm curious why this definition is the way it is.
It is so loosely defined that everything from CORBA to EAI and grid systems fit into this definition.Secondly, do the component services have to be distributed by definition? It should be easier to distribute the capabilities of a choreographed business process or a business service which follows the SOA principles. Any comments on that?
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