Comments on: Role on an Enterprise Service Bus (ESB) Post 1 http://kunalmittal.com/blog/2008/10/role-on-an-enterprise-service-bus-esb-post-1/ Blog on Cloud Computing, SOA, SaaS, and my flying experiences.... Sun, 09 May 2010 03:20:36 +0000 hourly 1 http://wordpress.org/?v=3.0.1 By: kunal http://kunalmittal.com/blog/2008/10/role-on-an-enterprise-service-bus-esb-post-1/comment-page-1/#comment-12 kunal Thu, 30 Oct 2008 15:45:42 +0000 http://kunalmittal.com/blog/?p=106#comment-12 You make some good points. I am not saying that an ESB is absolutely useless. It obviously has its place in an SOA. I will be blogging about specific scenarios on when and how to use an ESB in the next few days. One thing you said really hits home - today 95% of the ESB use is for classic integration - EAI or BPM, but not truly Services Orchestration, or other SOA use cases. I am not convinced that SOA will cost less with an ESB. It depends on the scope of your SOA project. If your initial SOA is not scoped to a small project or set of services, you are probably trying to bite off more then you can chew - thus adding risk. So, if you truly are "piloting" your SOA, then I definitely don't think putting an ESB into the mix is required. Once you have an SOA that is somewhat mature - of course, and ESB will come into play. This is a good segway into my SOA Maturity Model (http://www.kunalmittal.com/html/soamm.html). You make some good points. I am not saying that an ESB is absolutely useless. It obviously has its place in an SOA. I will be blogging about specific scenarios on when and how to use an ESB in the next few days.

One thing you said really hits home – today 95% of the ESB use is for classic integration – EAI or BPM, but not truly Services Orchestration, or other SOA use cases.

I am not convinced that SOA will cost less with an ESB. It depends on the scope of your SOA project. If your initial SOA is not scoped to a small project or set of services, you are probably trying to bite off more then you can chew – thus adding risk. So, if you truly are “piloting” your SOA, then I definitely don’t think putting an ESB into the mix is required. Once you have an SOA that is somewhat mature – of course, and ESB will come into play. This is a good segway into my SOA Maturity Model (http://www.kunalmittal.com/html/soamm.html).

]]> By: Mathieu http://kunalmittal.com/blog/2008/10/role-on-an-enterprise-service-bus-esb-post-1/comment-page-1/#comment-11 Mathieu Thu, 30 Oct 2008 09:55:31 +0000 http://kunalmittal.com/blog/?p=106#comment-11 Hi, from my point of view (and as an open source vendor point of view), the main problem is that there's no real definition of ESB, each vendor, or even consultant, has its own definition. We've met some guys of TIBCO, and for their new product, they gave up to call "ESB" what we call ESB. ESB means anything. Then, you don't need ESB for SOA. But it just can save you time/money. 1- In development : With a development framework, you avoid losing time on repetitive tasks 2- In production : If you have some production needs, like security, high avalability, scalability, monitoring... That would be quite long and maybe less stable to create from scratch. And with ESB you can get support from vendors, which might be essential. Then, it's clear, ESB is not SOA. 95% of ESB use today is not about SOA, but just classic integration. SOA is not ESB is not that clear to me. It might depends on your definition of ESB. Most of the time, SOA would cost less with an ESB, both for development and production phase. So, most of the time, ESB could be useful in an SOA. Hoping my comment is not too vendor-oriented or marketing-sucker-oriented ^^ Hi,
from my point of view (and as an open source vendor point of view), the main problem is that there’s no real definition of ESB, each vendor, or even consultant, has its own definition. We’ve met some guys of TIBCO, and for their new product, they gave up to call “ESB” what we call ESB. ESB means anything.

Then, you don’t need ESB for SOA. But it just can save you time/money.
1- In development : With a development framework, you avoid losing time on repetitive tasks
2- In production : If you have some production needs, like security, high avalability, scalability, monitoring… That would be quite long and maybe less stable to create from scratch. And with ESB you can get support from vendors, which might be essential.

Then, it’s clear, ESB is not SOA. 95% of ESB use today is not about SOA, but just classic integration.
SOA is not ESB is not that clear to me. It might depends on your definition of ESB. Most of the time, SOA would cost less with an ESB, both for development and production phase. So, most of the time, ESB could be useful in an SOA.

Hoping my comment is not too vendor-oriented or marketing-sucker-oriented ^^

]]>