200 likes | 342 Views
Architecture overview Visual programming for development of Distributed Event-Based systems. Carlos Neves Júnior cneves@ic.unicamp.br Hans Kurt Edmund Liesenberg hans@ic.unicamp.br Instituto de Computação – UNICAMP. (July/2013). Agenda. General foundation. 1. Introducing components.
E N D
Architecture overviewVisual programming for development of Distributed Event-Based systems Carlos Neves Júnior cneves@ic.unicamp.br Hans Kurt Edmund Liesenberg hans@ic.unicamp.br Instituto de Computação – UNICAMP (July/2013)
Agenda General foundation 1 Introducing components Runtime system 2 3
Communication based on Notification systems: Publish/Subscribe model
Examples 3 1 2 4
Related Work • SCXML (2013) – State Chart XML • Reactive Browser
Notes • Simple to design using visual programming and notations • Model Driven Architecture • Hybrid approach when additional functionality is needed • Visual Programming and Traditional Programming language (Java) • IDE implemented in Java/JEE • Support for Components covered in the current prototype • Event system (Brokers) to be addressed in next releases • System runtime configuration requires manual intervention • More experiments with Distributed Event-Based system
Introducing the building blocks Components • Producers • Consumers • Event Processing Agents • Event Processing Network • Scopes • Channels and Notification systems/Delivery of events
Producer • Component that generates and produces events (output) • publish
EPAEvent Processing Agent • Component that process events (rules) – produce and consume events • notify • (subscribe, • unsubscribe) • publish
Consumer • Component that consume and react to events (input) • notify • (subscribe, • unsubscribe)
Rules & Transitions in Statecharts • Transitions(Statecharts) • Source (State(s)) • Target (State(s)) • Trigger – Event+ guard (condition) • Action • Raise(event), Send(event), invoke(), assign() • Rule (NEW - Introduced in this Statecharts variant) • Trigger – Event + guard (condition) • Action • Special rules: onentry, onexit
RUNTIME – distributed components Messaging Service (JMS) and custom DEBS services for EPN handling
Thank you!!! Carlos Neves Júnior cneves@ic.unicamp.br Hans Kurt Edmund Liesenberg hans@ic.unicamp.br