10月4日,WSO2 ESB发布了2010-2010的产品路线图(草稿版)。
主要内容涉及到:
- Redesign the configuration language(配置,仍然是配置,虽然提供了编辑器,但是大量的XML配置文件仍然会带来很多工作,和Mule3.x一样都在简化XML配置文件)
- Multiple Synapse Configuration management support
- URLReWrite mediator
- AsyncBridge pattern and (formalize the EIPs)(增加了新的EIP组件)
- Integrate wand/tcpmon like tool for message playing(提供了貌似监控消息的功能)
- Sampler, sampling throttle(流控是WSO2独有的)
- New NIO transport(目前是通过Apache HttpComponents提供NIO,将来是否会通过Netty提供NIO?)
- Integrate WSDL import, schema import governance features and auto populate all the references in the proxy services UI when you select the WSDL
- TCP and MSMQ transports(除了支持JMS外,开始支持JMS provider的接入)
- Projects concept into ESB
- A project is a collection of sequences, endpoints, proxy services and etc... in an ESB configuration
- We should be able to bundle this into an artifact
- This artifact should be deployable on an ESB server
- Support Store and forward MEP(个人感觉MEP是个非常重的模式,但仍收到许多ESB的青睐,Mule2.x开始支持MEP)
- Improved support and samples for JSON.
- Debugger for the mediations(提供debug的功能非常重要)
- A debug console for a sequence of mediators so that you can replay messages and check the mediation action using the ESB admin console(和OSB的模式一致,均提供基于web console的debugger。)
- Provide facility to attach policies to service level (Proxy services) from the registry or the file system.
- Policy editor should have an option to browse the registry and point to a policy stored in the registry as the service policy
- Complex Event Processing with Rules..
- Recently Drools has announced the CEP capabilities using Drools and we are researching to get CEP implemented on ESB with Drools
- Implement the Dead Letter Channel (EIP)(向EIP靠近是主流ESB的趋势)
- Switch to event instead of eventing component for event sources
- Thread pool with the water mark level
- Secure vault support for all secret information
- UDP Multicast support and WS-Discovery adhoc mode(对WS-*的始终是WSO2的主要优势,但这个特征在实际应用中多吗?)
对WSO2 ESB的期望:
1.提供eclipse IDE工具,便于开发,目前的web console显得单薄。OSB、Fuse ESB和Mule最近都提供了IDE,希望WSO2也能跟上。
2.提供监控功能或者是API。通过监控可以看到ESB内部流转的消息,比如Camel和Mule提供了对消息监控的功能。
3.改造WSO2的架构,由于它基于Synapse,而Synapse是基于Axis2,所以对ws-*的支持尤其独到的优势,但是对其他协议的支持的实现使得其架构不够清晰。
期望毕竟是期望,开源ESB都做了很多工作,虽然在企业级应用中显得单薄,但毕竟是开源而不是商业的。
对开源的态度应该是:能用就行,别奢望太多,自己有能耐的话,在它们的基础上进行扩展或者改造成自己的ESB;同时可以将发现的bugs提交到社区论坛中,也为开源做点事情。