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 Jun 01, 2007
"... the compelling economics that bind open source products and SOA activities."The report mentions that of 400 executives surveyed, 71% of them view open source as either "important" or "very important" for consolidating their IT infrastructure. Plus, 57% said that they saw open source as "important" or "very important" for facilitating a migration to SOA. According to Forrester, 78% believed that the open standards approach typically taken by open source software is a major factor driving their view of its value for SOA next-generation enterprise architectures.
Most importantly is the expected delivery in Q4 of this year of a comprehensive open source SOA platform stack from Red Hat and its JBoss unit. The goal is to take the best of open source platform, middleware, tools, and SOA infrastructure (such as ESBs) and package them for volume viral delivery to the market, with a simplified pricing model (based on a “server instance”) for support.Furthermore, recent interviews with IONA Technologies around CXF (the Apache merger of XFire and the Celtix ESB), the CEO of SourceLabs (who are attempting to “professionalize” the adoption of open source components, making it “safe and easy,” as well as “dependable”), and a new SOA project in Eclipse from Deutsche Post World Net, are further evidence that open source is not lagging behind the traditional proprietary vendor approaches, as has often been the case in the past. As the article mentions:
SourceLabs expects open source for SOA to be huge, and it is gearing up to manage the movement to and support of open source code products for SOA ...However, it's not all a bed of roses. Celtix wasn't really going anywhere when it was within ObjectWeb. The Eclipse STP project (an attempt to provide a toolset for SOA) is still struggling to gain acceptance over the WTP project. As with all successful open source, the community adoption/following is often as important as (and sometimes more important than) the technology. Whether 2007 is really going to see open source leading the way with SOA adoption remains to be seen. However, it does seem clear from the amount of open source efforts in and around SOA, that developers and adopters are taking open source solutions seriously.
If by SOA you mean WS-*, I'm not sold. Open source projects tend to emerge from some fairly concrete need, and grow to the extent that they address that need in a useful way. The WS-* leviathan is so overwrought with interlocking dependencies that it is hard to imagine how an open source team would ever muster the manpower to get started, let alone produce anything useful.
I just don't see it. The buzz that I hear in the open source world is about Ruby, JavaScript, AJAX, RIA, REST, LAMP, and other very concrete things that get out of your way and let you do interesting things with networked computers. The buzz is there because those things work well independently, and they work well together.
That's not to say that IBM, BEA, and other big vendors won't release big chunks of useful code as open source, it's just that I never, ever hear any of my peers saying "Dude, did you hear about that new WS-ResourceLifetime spec? So killer. I can't wait to use it."
I agree with your underlying premise but think of it a little differently.
Most of WS-* is useless and will never be implemented. Some of it is essential to replace proprietary, vendor specific solutions. The incumbent mega-vendors have incentives to keep you locked into their type system, platform, world view, and way of approaching things. With the world interested in standard commoditized plumbing they have retrenched by confusing the situation with WS-*. Being able to do a low risk swap Windows machines for Linux boxes at any point (because of standard and loosely coupled services) does not get MS very excited and same goes for the other vendors - they're all in the same camp no one is worse then the other really.
Open source doesn't have the same legacy to protect or lock-in to create. So while the big vendors continue battle each other in spec committees solution driven open source projects can be quietly delivering on the promise of SOA by providing the tools and infrastructure needed to realize it.
All that said - my company ain't goin open source anytime soon but I appreciate how a neutral point of view fits best with SOA.
Jim
I can't see RedHat driving the acceptance of SOA with a "comprehensive open source SOA platform stack." The last thing I need is a tightly-coupled package. I like all the non-functional features provided by an ESB (BPEL included). Can I get this best of breed in a decoupled open source offering? Probably not there yet. Opensource is a more powerful driver than SOA. SAO has vendor-lock all over it right now with proprietary offering. As more opensource projects implement WS-* and ESB defacto specs the more adoption will continue.
"Ruby, JavaScript, AJAX, RIA, REST, LAMP " - these solutions are primarily targeted at the web application space which is the largest sector for application developers to focus on today. Much like client/server not that long ago when everyone needed to understand event-driven GUI and windows development.
SOA is here to address application to application interoperability and integration. This is a fundamentally different problem space than webapp dev. The integration space is a relatively smaller market in terms of technologists than general web app designers/programmers. If your organization is streamlined enough to only need a few web applications then SOA may not be for you.
SOA does not equate to WS-*, however, SOAP & WSDL are two very useful solutions when it comes to MSFT/.NET to Unix/Linux/Java interop often needed in application to application requirements.
The report doesn't include WSO2's new ESB, it doesn't talk about TIBCO ActiveMatrix, it doesn't consider what may happen if JBI 2.0 succeeds, and there are a hundred or more open source projects for SOA development not even considered. It seems to me that it is way to early to be talking about emerging winners. It's still going to be another year or two before management understands SOA, let alone which tools will get them there.
-Frank Cohen
www.pushtotest.com
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.
5 comments
Watch Thread Reply