This reference is either acquired through a stringified URI string, NameService lookup (similar to DNS), or passed-in as a method parameter during a call. Object references are lightweight objects matching the interface of the real object (remote or local). Method calls on the reference result in subsequent calls to the ORB and blocking on the thread while waiting for a reply, success or failure. The parameters, return data (if any), and exception data are marshaled internally by the ORB according the local language and OS mapping. [edit]
- leave anything related to transport, communication to other layers- use this revised CEP to express and execute event-relevant logic, the purpose of which is to translate the ambient events into relevant business events- have these business events trigger business processes (however lightweight you want to make them)- have these business processes invoke decision services implemented through decision management to decide what they should be doing at every step- have the business processes invoke action services to execute the actions decided by the decision services- all the while generating business events or ambient events- etc.
For those unfamiliar with business-driven architecture, I believe the most viable, agile architectures will be comprised of a blend of architecture strategies, including (but not limited to) service-oriented architecture, event-driven architecture, process-based architecture, federated information, enterprise integration and open source adoption.
Most BREs today are deployed as “decision services”, and are used in “stateless” transactions to make “decisions” as a part of a business process. A CEP application is instead processing multiple event streams and sources over time, which requires a “stateful” rule service optimized for long running. This is an important distinction, as a stateful BRE for long-running processes needs to have failover support - the ability to cache its working memory for application restarting or distribution. And of course long-running processes need to be very particular over issues like memory handling - no memory leaks allowed!
"Not many sites can take you from the Design Council to Design Addict, from the Rural Studio to Worldstudio, and have it all make sense. Nate Burgos’s ever-evolving webliography is a smart portal to the ever-expanding universe of design"
T. Gu, N. Lo, und W. Yang. Proceedings of the 2007 Summer Computer Simulation Conference, Seite 1128--1135. San Diego, CA, USA, Society for Computer Simulation International, (2007)
D. Menasce, J. Sousa, S. Malek, und H. Gomaa. Proceedings of the 7th international conference on Autonomic computing, Seite 195--204. New York, NY, USA, ACM, (2010)