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 Jon Rose on Oct 24, 2007
At MAX and Web 2.0, Adobe announced how it is shifting all of their apps online, transforming them into Software as [a] Services [SaaS], although it would probably be about 10 years for such a shift to be complete.In Adobe’s view, this is not a shift that will happen overnight. Adobe Systems CEO, Bruce Chizen, gave time ranges from 10 to 20 years, telling pcworld.com in interview just prior to the Adobe Max conference it may take 20 years:
PCWorld.com: Do you agree the future of software delivery is that SaaS/hosted model?Chizen and pcworld.com discussed one of the early examples of Adobe offering software in this model with Premiere Express. In addition to a shift in how the applications are delivered, Chizen touched on the possibility of the revenue model being advertising based:
Chizen: Eventually. The key is how long does that take. It depends on the application and on broadband capabilities. I'm smart enough to say that will be in 20 years probably.
It [Premiere Express] lets consumers do simple video editing. We offer it through partners like Photobucket [and MTV]. Some of those business models are advertising-based. We'll continue to experiment.Chizen does see challenges in moving applications to the Web. Reuters’ quoted him speaking at the MAX conferences saying:
"The desktop is a powerful, powerful machine in which to run applications. Broadband, as quick as it gets, is still going to have some limitations in the short term," said Chizen in a question-and-answer session on stage at the conference.Along with moving their desktop applications to the Web, a more immediate part of Adobe’s strategy centers around the AIR platform. The AIR platform lets developers use web technologies to build desktop applications and deploy them in the AIR runtime. Chizen breaks down the AIR platform for pcworld.com:
PCWorld.com: Why is the AIR approach preferable to building an offline component for browser-based applications, along the lines of what Google is doing with Google Gears?A key AIR example application is Buzzword, a word processing application, which was developed in Flex and has a version that runs on the desktop using the AIR platform. Adobe recently announced that they are acquiring Virtual Ubiquity, creators of Buzzword. Chizen explained the motivation for the acquisition to pcworld.com:
Chizen: For some applications, the browser is great and having offline capabilities will be a great extension. But for other applications we want complete control over the user experience [and the browser is inadequate.]
That's where we really differentiate: the ability to go a little further in local capabilities, the ability to drag and drop easily from the desktop to the application and back. Those things would be tough to do with a browser. And some applications, you want to stay in them and don't want to be encumbered by a browser. You want local presence and that's where we really shine.
What excited us about Buzzword wasn't being in the word processing business, but that it's a great example of what AIR can do. It also fits really nicely into our Acrobat document collaboration strategy.Adobe is clearly creating a lot of buzz with Flex, AIR, and their SaaS strategy, but it is still unclear how significant Adobe’s role will be in the future of software.
For many apps, SaaS is more a change in billing model than anything else. Adobe for example could deliver PhotoShop "as a service" simply by adding a metering mechanism that would allow them to "give away" the software and then bill instead for actual time used. They don't need to rearchitect PhotoShop to have a "thin" front end in order to deliver it "as a service".
You could argue that PhotoShop is awfully big to pull down over broadband, but you'd have to be nuts in 2007 to bet against bandwidth.
Stuart,
SaaS is somewhat of an ambiguous term, and I believe you are correct that this doesn’t necessarily dictate an ASP like architecture. However, I think the more interesting part is the technical challenge of putting products like PhotoShop on the web, and vise versa with utilizing web technologies on the desktop, as the lines begin to blur between the desktop and web. Have you had a chance to look at AIR or some other options that are driving this trend? What do you think about them?
Ryan Stewart has a good post on zdnet.com breaking down three of the options: blogs.zdnet.com/Stewart/?p=595.
Thanks for commenting,
-Jon
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.
2 comments
Watch Thread Reply