Hi, Following were discussed on CEP 3.0.0 and transport adaptors during the architecture review meeting held on 19/06/2013.
1. Instead of having multiple endpoints for different content types, having single endpoint and distinguish processing to be done using the content type. 2. Whiteboard pattern for Transport Adaptors - currently we have the inverse of whiteboard where different transport adaptor implementations register themselves at the core which can lead to problems like stale references etc. Instead, the suggestion was to get this done through the OSGi framework. This will facilitate to handle stale references, new bundle versions etc properly. 3. Worker manager separation 4. Separate implementation classes for handing in/out sequences of transport adapators - currently, there are some implementations where these implementations are done at the same class. 5. Clustering and autoscaling for CEP - this is very difficult to do efficiently due to the nature of the processing which requires large and frequently accessed shared memories, such as having to keep sliding windows, event tables etc. 6. Improving navigation in CEP UI - currently we have separate pages and links in menu bar for configuring various components of CEP, which is not very intuitive to the user. Suggestion was to improve the navigation so that user can perform the configurations easily just based on hints. 7. Removing low level configuration details from the UI - the idea is to keep these low level configurations at xml configuration file level. UI should be for the basic users and for advanced users, xml file configurations are preferable. 8. Publishing with minimal configurations - need something like in a SaaS deployed at the super tenant level and tenants can use easily without going through the hassle of configuring. 9. CEP Samples - rather than having ESB-sample-type samples where user is limited to a specific scenario, suggested to have something similar to BAM toolbox. 10. Multi-tenancy in CEP - due to the nature of the processing, currently all tenants are loaded at startup, which can lead to significant delays at startup when there are many tenants. The idea is to limit the number of tenants per engine. 11. Adaptors/components loading issues - Need to have a discussion with the kernel team. Thanks Rajeev -- Rajeev Sampath Senior Software Engineer WSO2, Inc.; http://www.wso2.com. Mobile:* +94716265766 *
_______________________________________________ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
