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 Floyd Marinescu on Apr 09, 2008
IBM's 2nd annual IMPACT SOA conference is being held this week and there are over 6000 attendees here. During the morning keynotes, IBM execs re-affirmed the view that the main innovation presented by SOA is business/IT alignment. They presented a business-process centric view of how SOA is an enabler for enterprises to change (agility), as well as their view of Smart SOA, a set of principles / maturity model for SOA based on numerous customer SOA deployments. IBM also invites you to contribute to their view of SOA via their live SOA JAM, an idea sharing site that will be active until this Thursday. This post summarizes various live interviews and the day 1 and 2 morning keynotes and press conferences.
As the pheonomenon of the world wide web kicked off in '94 and we solved the problem of people connecting to apps and to people on a golobal scale, what emerged was set of concepts about open architecture, of navigating over 30 milllion web servers...calling services to get something done in the context of what you’re trying to do. Around 2004 SOA comes around. But we’ve been doing integration for a long time. Something is new, and I would argue that something is: About business, not technology. The alignment of business and IT, the connection of them and the use of IT as transformational technology in the context of business process and business flow, drives significant incremental value around investments in IT... It’s a powerful idea and one delivering near term via cost savings an long term through business flexibility.
We’ve gone form automating in vertical slices (throughout the 20th century, where we used packaged/custom apps for vertical lines of business' with very manual links between systems, to a 21st century approach where apps are a source of content for processes. Allowing dynamic deployment of services at runtime.
This view of SOA as being about enabling end-to-end business processes was an ongoing theme around the conferences. IBM sees this as a paradigm shift for enterprise executives - rather than have individual lines of business manage their own IT systems with point-to-point or no integration between systems, instead have them expose their apps as sources for wider business processes, often united by an ESB. Also seek to replace multiple implementations with similar business processes across departments with one service that the whole company is mandated to use. IBM calls the consolidation of departments around unified services controlled by central IT "turning the enterprise on its side"
IBM invited a number of brand name customers to the stage telling similar stories about implementing new business-critical processes across a variety of heterogenous IT systems. One not-so mission critical system, but one which got the point across well was Harley Davidson, which implemented a ride planner application that allows you to plan a trip across the US and book hotels, get GPS locations, pre-purchase Harley Davidson gear for pickup laong the way, search for and add gas station stops, etc. Harley CIO Jim Haney explained:
SOA is not about technology. It’s about how you put the pieces together that sets you apart. Its about defining the process that creates good customer experience.
Jim compared the traditional approach to application design vs. the new SOA-style appraoch using the trip mapping applicatoin. Tradititionally – they would create a mapping app, "focused on a single transaction" - mapping. Additional servies a user may want such as hotel reservations, searches for interesting events/sites along the way, would be left to other IT systems or separate apps.
But with an SOA type mind set, they focus on the ‘customer lens’, not the ‘IT lens’, focussing on the process ‘plan a motorcycle ride’, and not indidivual transactions. Jim explained:
This requires cultural change: focus beyond systems and applications. How does the customer complete a process from start to finish? Go from thinking in terms of sysems, applications, to thinking in terms of what a customer does to complete a process.
InfoQ spoke to Sandy Carter, VP of SOA Marketing who talked about IBM's Smart SOA view/maturity model and gave a view of where they see enterprises in this spectrum:

According to Sandy:
A number of IBM executives mentioned that this final area of events+policy will be a focus for IBM this year. At Impact, a new product called WebSphere Business Events, which allows business owners to define patterns and filters and fire off new processes as a result.
Another interesting customer story was Health Care services corp, which is the 4th largest health plan in the US. A number of different subsets of their business are done by many different groups in with different IT systems, ie: eligibility, benefit inquiry, claim status, etc. In transitioning to SOA, they built an enterprise-wide eligibility services. Now 10 different applicaitons in the system are using the one eligibility service. Austin Waldron from the company explained:
it hasn’t been an easy transition, these app owners used to do everything themselves...this moves pieces of IT away from individual app owners and into a centralized architecture group...the governance- making sure that all the different parts of the organizatoin recognize the service oriented approach and use it instead of doing their own thing is a very very big deal.
This transition of services from individual departments to central IT was called 'turning the organization on its side' by many IBM execs. Here you take the various 'ilities' of concern in individual applications and you have to ensure the same robustness for the entire process end to end. Steve Mills called this "process integrity", saying it "puts a lot of stress on the environment, needing features for compensation, remediation, rollback", etc. Steve said this is a differentiator for IBM compared to others in their space.
Also during the day 2 keynotes, IBM presented 5 SOA best practices, distilled from 6000+ customer deployments and 250 case studies:
SOA spending was said by analysts to double in 2008, as more and more departments are being brought into enterprise SOAs. This year's IBM Impact also marked the 10 year anniversary of Websphere, 15 year anniversary of IBM MQ, and the 40 year anniversary of CICs.
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