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 Jean-Jacques Dubray on Jan 03, 2009
In this latest article, Matthieu Hug, CEO of the BPM-as-a-Service startup RunMyProcess.com, provides his views on Cloud Computing, focusing on the Platform-as-a-Service layer.
He explains that for the most part:
[…] Cloud Computing is about making usually “painful” problems someone else’s problems
In addition, Cloud-based development platforms enable a new Development paradigm:
One of the core innovations behind PaaS is the emergence of a Dev 2.0 paradigm with the utilization of Web 2.0 technologies for developer tools, agile methodologies and massive use of domain specific languages (DSL) rather than multi-purpose programming languages. Dev 2.0 makes developers a lot more productive and enables non-developers to participate in the definition and validation of key elements of the business logic, such as a business process, a business rule or a form definition.
These characteristics are disruptive enough. Yet he sees another emerging disruption in partner relationship management. He explains how Cloud Computing Development Platform can be used to deliver a new kind of Enterprise Information systems: the Multi-Enterprise Information Systems (MEIS).
Up until today, multi-enterprise information systems have often been implemented using a portal hosted by one of the parties collaborating on particular activities, be it, for instance, an OEM portal for suppliers, or a distributor portal for retailers.
The problem is:
This approach has lead to significant inefficiencies, risks and inflexibilities as one of the parties is bearing all the costs of building, maintaining and operating the portal.
PaaS, and in particular BPM-as-a-Service can:
[…] deliver Multi-Enterprise Information Systems where each party can contribute to the development of the system, in essence mutualizing the development costs while offering superior integration capabilities with any party’s legacy systems and web based intranets applications.
In this new type of information system architecture, services exposed by the different parties become key elements of the new multi-enterprise solution.
He concludes:
"Cloud computing" takes its entire dimension when SaaS is also read as "Services-as-a-Software". Multi-Enterprise Information Systems is about making these services useful and valuable to any business, big or small.
Free Gartner Cloud Service Brokerage Report
Getting Started with Stratos - an Open Source Cloud Platform
Complimentary Gartner (Hype Cycle for Cloud Security) Report
SOA All-In-One Guide: KPIs & Best Practices, ESB Report
Improve Java Garbage Collection, Runtime Execution, and JVM visibility with Zing
Cloud Computing, SaaS, PaaS, BPM-as-a-Service, Dev 2.0, Web 2.0, DSL, MEIS... a lot of buzzwords!
The best falacy wasCloud Computing is about making usually “painful” problems someone else’s problems
... as if this "someone else's problems" were not your problems too when things go wrong in your project. Unless you are just looking for someone else to blame when it fails, of course.SaaS is also read as "Services-as-a-Software"
... was also funny. I hope it was a typo :)
Ron:
thanks for your comment. Matthieu's intent was to express that Cloud Computing enables a new kind of thinking in the enterprise, and that SaaS could "also" be read "Services-as-a-Software" (this is not a typo).
As I understand it, Cloud Computing can help you package and deliver your (physical) services with a software interface (as opposed to say a Call Center interface). Multi-Enterprise Information Systems offer new ways to consume these services, making them that much more attractive to publish.
I am not sure MEIS are just another Buzzword, people like Jack Greenfield (Microsoft) and Dave Frankel (SAP) have started to write and build stuff in this area. 10 years ago, people like Bob Haugen already had a similar vision. The problem then was where to deploy them? It seems that this problem is no longer a road block.
I was reading the article with a general interest and attracted by the headline question. However I see that this article lines up with all the other articles I found so far in the web. These articles use (as the other comments complain about) all buzzwords in the area.
However this is not my point. My question is whether the headline question was answered or not?
I can see a lot opportunities in the *aaS space. However one has also to understand that every *aaS provider has is own definition of *aaS. Furthermore I already understand from what I read about this topic so far that there is a whole pandoras' box of new issues and problems to be solved. Here I see a gray to dark bubble of information lack. I'm also interested what these 'Advanced Dev 2.0 tools' look like and who develops/will develop them?
As more as I read, I get more and more questions. Where is the one who can answer these questions? Are there some good blogs?
Thanks,
Karsten
Asking the question about a blog, I tried to answer it myself. This one looks very promising: www.saasblogs.com/2008/12/01/demystifying-the-c...
In general I found the information on www.saasblogs.com/ quite substantial.
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