1 / 10

Historic Data Access in Publish/Subscribe

Historic Data Access in Publish/Subscribe. Middleware System Research Group University of Toronto. A. E. B. C. F. D. Application Domains. Workflows, business processes and job scheduling. Supply chain and logistics. Job A done. In flight. Trigger. Delivered. Fault. Order.

cevallosj
Download Presentation

Historic Data Access in Publish/Subscribe

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. Historic Data Access in Publish/Subscribe Middleware System Research Group University of Toronto

  2. A E B C F D Application Domains Workflows, business processes and job scheduling Supply chain and logistics Job A done In flight Trigger Delivered Fault Order Event-Based Callback Razor SKU Invoke Loan Light Transform Temperature Service oriented architecture RFID and sensor networks

  3. Publisher Subscriber Publish/Subscribe 1. Advertise 3. Publish 2. Subscribe Event-Based Content Routing Flexible Decoupled Declarative Responsive

  4. Research Challenges • Seamless historic data access • Query semantics • Content-based query processing • Event correlation • Future/historic events • In-network correlation • Routing optimization • Robust routing over cyclic overlays • Adaptive to network traffic • Distributed load balancing

  5. P P C Customer Database SystemInfo Database SystemInfo Customer DB Administrator S Sales Manager System Architecture [class, DB_Control][command,`STORE’][db_id, Customer_DB] [content_spe,` [class,eq,order][orderID,isPresent,any],[item,isPresent,any]…’] 2 1 3 S A P 4 5 6 P HS CS AS PADRES Broker Network

  6. Database Schema Tables [class, order][orderID,C100-01],[customerID,C100],[item,shoes] classes SQL INSERT P attributes … … DB Binding events Broker Database SQL SELECT Views HS HP messages HP HP [class, eq,order][orderID,isPresent,any] … [time,<, now]

  7. C P P P SystemInfo Database Customer Database Monitor SystemInfo Customer Customer S S Sales2 Sales1 Retail Application Management Scenario ESB 1 2 3 5 4 6 7 8 9

  8. Future Work • Strategies for database placement • Data space assignment • Runtime optimizations • Large-scale experiments • For more details, please visit: http://padres.msrg.toronto.edu/Padres/

  9. BACKUP

  10. Features Demonstrated • Unification of historic and future event processing • Event correlation and in-network processing • Dynamic message routing on cyclic overlay • Network virtualization

More Related