Embed Size (px)
DESCRIPTION
Architecture overview Visual programming for development of Distributed Event-Based systems. Carlos Neves Júnior [email protected] Hans Kurt Edmund Liesenberg [email protected] Instituto de Computação – UNICAMP. (July/2013). Agenda. General foundation. 1. Introducing components. - PowerPoint PPT Presentation
Citation preview
Architecture overviewVisual programming for development of Distributed
Event-Based systems
Architecture overviewVisual programming for development of Distributed
Event-Based systems
Carlos Neves Júnior [email protected]
Hans Kurt Edmund Liesenberg [email protected] de Computação – UNICAMP
(July/2013)
2
Agenda
3
Communication based on Notification systems: Publish/Subscribe model
4
Event-Based systems: Architecture
5
Examples
1
2
3
4
6
Related Work
SCXML (2013) – State Chart XML
– Reactive Browser
7
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
8
Event-Based systems: Components
9
Introducing the building blocks Components
Producers
Consumers
Event Processing Agents
Event Processing Network
Scopes
Channels and Notification systems/Delivery of events
10
Producer
Component that generates and produces events (output)
publish
11
EPAEvent Processing Agent
Component that process events (rules) – produce and consume events
publishnotify
(subscribe,
unsubscribe)
12
Consumer
Component that consume and react to events (input)
notify
(subscribe,
unsubscribe)
13
Distributed view - channelsEPN – Event Processing Network
14
Distributed view - scopes Group of components
15
Distributed View #2 Scopes – Graph of scopes
16
Visual programming From EPN to DEBSxml
17
Visual programming From Statecharts to SCXML
18
Rules & Transitions in StatechartsTransitions (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
19
RUNTIME – distributed components Messaging Service (JMS) and custom DEBS services for EPN handling
20
Thank you!!!Thank you!!!
Carlos Neves Júnior [email protected]
Hans Kurt Edmund Liesenberg [email protected]
