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 Mark Little on Nov 28, 2007
The original WS-CDL specification was less than impressive, however, the concepts were right on. I haven't gone back to revisit the specs but I will. It will take people some time to understand the fundamental 'centralization' problem associated with BPEL. Until then, alternatives will largely be ignored.Or as Charlton Barretto commented:
CDL enables the business stake holder, the business analyst, the enterprise architect and the application engineer to share their views of the same system in a synchronised fashion, by providing the means for each level of detail for each stake holder to be captured without that detail being necessarily exposed to the others. Also CDL provides the necessary provenance to enforce requirements at each level. In this fashion, CDL also enables the A in SOA, since it provides the manner in which architecture can be modelled, described and implemented.However, despite this (or maybe because with the exception of Oracle, no major vendor has supported WS-CDL since the start) there has been limited tooling around for developers to use. It is interesting to note that despite Oracle's support, they have no WS-CDL implementation either. In fact, the only option until recently was the tooling available from HatTrick Software, related to the Pi4 Technologies Foundation. That should come as no surprise, given that Steve Ross-Talbot is a co-author of the standard. However, one is the loneliest number and WS-CDL hasn't exactly caused the same kinds of waves as other WS-* technologies.
At last, Christmas has come early. Congratulations to Hongbing Wang and his team in China. A new WS-CDL tools suite is born and we at Pi4 Tech are no longer out on our own.Now as the song says, "Two can be as bad as one It's the loneliest number since the number one". This may not be a wave, but maybe it's a ripple. Perhaps WS-CDL is finally turning the corner to mainstream acceptance as people see that WS-BPEL is not the final solution.
I feel every more sure that others will join the fray.
http://wscomposition.seu.edu.cn/index.html
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.
No comments
Watch Thread Reply