1 / 17

Visibility as Central Abstraction in Event-based Systems

Visibility as Central Abstraction in Event-based Systems. Event-based Systems. Pub/Sub System. Benefits. We appreciate the loose coupling Indirect addressing, space decoupling Additional degrees of freedom Basic CS solution… Event-based: Components control their own state, solely

baris
Download Presentation

Visibility as Central Abstraction in Event-based Systems

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Visibility as Central Abstraction in Event-based Systems

  2. Event-based Systems Pub/Sub System Ludger Fiege, fiege@acm.orgTU Darmstadt, Germany

  3. Benefits • We appreciate the loose coupling • Indirect addressing, space decoupling • Additional degrees of freedom • Basic CS solution… • Event-based: • Components control their own state, solely • Independence • Reusability Ludger Fiege, fiege@acm.orgTU Darmstadt, Germany

  4. Event-based Systems Pub/Sub System Ludger Fiege, fiege@acm.orgTU Darmstadt, Germany

  5. Drawbacks • Composed functionality is • Direct and implicit result of composition • No explicit control of coordination • Control only by adapting components: • Tailor event types/contents • Encode application structure into components • Sacrifice very benefits of event-based style?! Usable as basic programming paradigm? Ludger Fiege, fiege@acm.orgTU Darmstadt, Germany

  6. Event-based SystemsRegaining Control Pub/Sub System Ludger Fiege, fiege@acm.orgTU Darmstadt, Germany

  7. Family 2 advice advice Ma GrandMa Scopes • Scopes constrain the visibility of notifications • Visibilityas first-class concept • Structure not emulated by namespaces or filters • Clients not aware of structure • External control of structure: Integration Family 1 sick sick Ma GrandMa Ludger Fiege, fiege@acm.orgTU Darmstadt, Germany

  8. Forest Wolf Fairytale IIA Scoped World: Structuring Family 1 Family 2 LRRH Grand-mother Mother Ludger Fiege, fiege@acm.orgTU Darmstadt, Germany

  9. Forest Wolf Fairytale IIIA Scoped World: Information Hiding advice Family 1 Family 2 advice advice LRRH Grand-mother Mother Ludger Fiege, fiege@acm.orgTU Darmstadt, Germany

  10. GermanImmigrants Pen- friends Fairytale IVHeterogeneous World Forest Family Wolf sick krank LRRH Grand-mother Mother Ludger Fiege, fiege@acm.orgTU Darmstadt, Germany

  11. Default broadcast semantics not always appropriate Forest Family 1 Family 2 Wolf LRRH Service Grand-mother Dad Mother 1 2 3 Fairytale VLRRH Services Default broadcast semantics not always appropriate Forest Family 1 Family 2 Wolf LRRH Service Grand-mother Dad Mother 1 2 3 Ludger Fiege, fiege@acm.orgTU Darmstadt, Germany

  12. Implementation • Project REBECA: http://www.gkec.informatik.tu-darmstadt.de/rebeca • Prototype of notification infrastructure • Scalable content-based filtering • Structuring with Scopes • Example Applications • Stock trading platform • Self-actualizing web pages Ludger Fiege, fiege@acm.orgTU Darmstadt, Germany

  13. 2 Component Interface Component * DeliveryPolicy * SimpleComponent Scope SecurityPolicy SessionScope EventMappings UML Ludger Fiege, fiege@acm.orgTU Darmstadt, Germany

  14. Using Scopes • Different Implementations of Scopes • Not always all configuration options available • Adapt/tailored to deployment scenario • Up to now: Specification • XML description of interfaces • Java objects implementing policies • Future: • Composition languages • Functional PL Ludger Fiege, fiege@acm.orgTU Darmstadt, Germany

  15. Contributions • We started by implementing an event-based middleware • Introduce scopes in event-based systems • first-class structuring mechanism • Obvious benefits • Control side effects • Address heterogeneity issues • Refine event service semantics Ludger Fiege, fiege@acm.orgTU Darmstadt, Germany

  16. …and then • Event-based components • Information hiding • Composing new components • Implemented framework: • allows to investigate scopes as new abstraction in event-based systems • Software engineering • Component languages, Meta Object Protocols • Data management • Sessions, transactions, notification lifetime • Distributed systems • Multicast, ordering, group communication • … Ludger Fiege, fiege@acm.orgTU Darmstadt, Germany

  17. Questions? Thank you for listening! Ludger Fiege Dep. of Computer Science TU Darmstadt, Germany fiege@acm.org Ludger Fiege, fiege@acm.orgTU Darmstadt, Germany

More Related