Is JBI dead ? Is it still a valid criteria in an ESB selection?

JBI standard is (was?) supposed to be the standard for Entreprise Service Bus, especially in terms of facility of reuse/exchange of capabilities of different ESBs (or lonely Service Engine providers)

Known JBI implementations are (according to wikipedia) :

Non implementers:

  • IBM => as far as I know is not JBI. Definitively follows SCA
  • JBoss => Custom

Without taking into consideration that JBI works, and that it address different problems than SCA, would you really took into account in an ESB choice the fact that it is or not JBI compliant ? or stick to the capabilities of the ESB ?

Reference: What are the differences / similarities between JBI and SCA

 

 

Yeah jbi is dying. There is not gonna be a jbi 2 spec. Check out the blog post by gnodet, lead on jbi and servicemix, posted on his blog, about his thoughts on jbi.

Its just so so much easier to do apache camel, or spring integration than jbi.

share|improve this answer

 

Alternative to JBI seems to be more than one... Apache Camel or Spring Integration as mentioned by Clause.. which means, JBI need exists as standard.. to avoid multiple ways of doing the same thing..

I think JBI would continue to evolve as it is just a specification and not implementation.. Camel and Spring could comply to such specification

More can be read at http://www.pymma.com/index.php?option=com_content&view=article&id=127:is-jbi-dead-not-of-course&catid=82:blog-paul-perez&Itemid=574

Raja Nagendra Kumar, C.T.O www.tejasoft.com

share | improve this answer

 

 

评论
添加红包

请填写红包祝福语或标题

红包个数最小为10个

红包金额最低5元

当前余额3.43前往充值 >
需支付:10.00
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明:

1.余额是钱包充值的虚拟货币,按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载,可以购买VIP、付费专栏及课程。

余额充值