Very Live Interview of LJE with a great humour and punchlines:

Its seems that great CEOs had a good time. Here is a glimpse of the witty interactions...

On Cloud Computing

"Everyone looks around and is like, 'Yah! Like everything is in the cloud,' " mocked Ellison. "My objection is it's absurdity--it's nonsense ... What are you talking about? It's not water vapor. It's a computer attached to a network!"

Again on Cloud Computing
"Cloud computing isn't the future--it's the present and the past of computing,"

This is the best comment on life:
"I think life is a series of acts of discovery," Ellison mused. "We're all interested in discovering our own limits."

SOA on Cloud

In today's world of Cloud computing, I would like to make a case for SOA on Cloud. It make sense for providing an agile and scalable infrastructure. SOA on Cloud would bring the setup cost of the customers down. Recently I had a discussions with a large consulting company engaged in providing SOA consultancy and Syetem integration to large enterprises. The executives really liked the idea of SOA on Cloud. That would immediately bring their cost down. In their opinion, at each client they spend 2-3 weeks in getting environment procured, set up etc before they could start SOA setup. With SOA on the cloud, they can immediately avoid all the setup time and start doing the real work. Obviously the saved time is a saving on billable hours.

Google FastFlip .. My quick take on it..

http://texploration.wordpress.com/2009/09/15/first-look-at-fastflip-flip-or-flop/

Flaws in Using BPEL to implement Orchestration Engine than Using BPEl to Orchestrate a Process Flow

BPEL provides a Web Service Orchestration language. Like any basic programming language, it has some constructs for declaring variables, switching, looping, sequencing or parallel branching, etc. Due to this construct, some times I came across implementation where BPEL is used as a programming language implementing an Orchestration Engine itself than an orchestration language. In this case, the flow sequence is captured as a model in database tables and then BPEL process is an engine which uses the model in the tables to get the next activity. So it kind of "implementing an orchestration" engine in BPEL rather than Orchestrating in BPEL. Isn't it cool? or Are there any issues? Yes, in prima-facie it looks like cool, creative and innovative. However, you would need to think about what BPEL orchestration is, how would compensation work? how about fault handling? how can you view the process itself, whether you would be able to meaningfully monitor the process? In most of the scenarios, the answers to these questions would steer you away from using BPEL as a programming language

IBM, watch out, we are coming to win it !

WSJ Advertisement:

Speaking at Oracle OpenWold 2009

I will be speaking at OOW 2009 on Oct 12th. The topic will be:
Oracle SOA Suite 11g Best Practices Based on Oracle Fusion Applications Development Experiences