Project Wihidum
•
0 recomendaciones•286 vistas
This is the presentation of my final year research project "Wihidum".
Recomendados
Recomendados
Más contenido relacionado
Destacado
Destacado (17)
Similar a Project Wihidum
Similar a Project Wihidum (20)
Project Wihidum
- 1. WIHIDUM An Efficient and Scalable Middleware for Publish-Subscribe Communication Paradigm W Coordinator Mr. Shantha Fernando Developer Team Dilshan Amadoru Hasini Gunasinghe Chamini HasangaPrabath Abeysekara Supervisors Mrs. Vishaka Nanayakkara Dr. Srinath Perera
- 2. Overview
- 3. Publish-Subscribe Paradigm Publisher Subscribe Renew Get status Unsubscribe Publish Subscriber Listener
- 4. A Real World Example Greenland Russia USA Indonesia South Africa Tsunami Sensors Alarming Systems
- 6. viewed as a single messaging brokerS2 P2 P2 L1 P2 L2
- 7. Architecture of a Single Broker Publisher Service Listener Service Queue Delivery Thread Pool Publication Processor Publish Subscription Processor Filter Message Receiver Topology DB Storage Manager Communication Manager Subscriber Route Route Subscriber Service Next Broker Service
- 8. Overview of Wihidum Admin Service Setup Broker B Setup Broker Get Broker List Get Broker List Setup Broker Route Route B B Subscribe Publish Delivery Publisher Service Subscriber Service Listener Service
- 9. Topologies of Wihidum Broker Network Tree Topology Cluster Topology B B B B B B B B B B B B B Simple Structure Easy to implement Efficient in the publication process Root node gets too much weight Complex structure Harder to implement Efficient in the subscription process Small number of communication channels Load is distributed at three levels of clustering
- 10. Performance Testing Broker Hierarchy CC Publishers SCC B Listeners Subscribers
- 11. Publication Process Publication Throughput Publication Latency
- 12. Subscription Process Subscription Throughput Subscription Latency
- 14. optimized concurrent processing in routing of publications
- 15. asynchronous routing of subscriptions
- 16. usage of in-memory storage
- 17. Hierarchy of web services with inherent interoperability gives platform independence
- 21. WS-Eventing
- 22. Publish-Subscribe Benchmarking guidelines such as having a data model for publishable information and having a well defined communication protocol.
- 23. Apache Savan
- 24. Narada Brokering
- 26. References PATRICK TH. EUGSTER, PASCAL A. FELBER, RACHID GUERRAOUI, ANNE-MARIE KERMARREC, “The Many Faces of Publish Subscribe,” No. 2, Vol. 35, ACM Computing Surveys, June 2003. “Web Service Eventing(WS-Eventing),” 24 September 2009. [Online]. Available: http://www.w3.org/TR/2009/WD-ws-eventing-20090924/. [Accessed: October 11, 2009] ShrideepPallickara and Geoffrey Fox, “On the Matching of Events in Distributed Brokering Systems,” in International Conference on Information Technology: Coding and Computing (ITCC’04), 2004 IEEE, Community Grid Laboratory, Indiana University. “IBM WebSphere Message Broker”, [Online]. Available: http://www-01.ibm.com/software/integration/wbimessagebroker/. [Accessed: March 25, 2010]
- 27. Do you want to know more?
- 28. Thank You! W
Notas del editor
- Add coordinator
- What is it?There are many applications in the real world where the two parties involve in communication. Clients of such a system, who produce information, are referred to as publishers, while clients that consume information are referred to as subscribers. Publishers generate messages to inform the external world when a certain event has occurred. Subscribers, who express their interest in events by means of subscriptions, are then notified about the occurrence of these eventsDrawbacks of P2P communication:Publishers and subscribers are tightly coupled Many communication channels. Publishers can not handle the subscribers individually when the number of subscribers grow.Examples of pub/sub: News publication. Mobile communication. Business process management. Eg: Microsoft BizTalk serverDatabase integration. Eg: Oracle Road traffic visualization. Enterprise application integration. Eg: JMS Message Oriented Middleware. Eg: Tibco Rendezvous, Advantages of PubSub communication paradigmDecoupled in three dimensions: space, time and synchronization All the subscriptions are handled at subscription manager. Efficient filtering criteria.Where WS-Eventing comes into play
- What is it?There are many applications in the real world where the two parties involve in communication. Clients of such a system, who produce information, are referred to as publishers, while clients that consume information are referred to as subscribers. Publishers generate messages to inform the external world when a certain event has occurred. Subscribers, who express their interest in events by means of subscriptions, are then notified about the occurrence of these eventsDrawbacks of P2P communication:Publishers and subscribers are tightly coupled Many communication channels. Publishers can not handle the subscribers individually when the number of subscribers grow.Examples of pub/sub: News publication. Mobile communication. Business process management. Eg: Microsoft BizTalk serverDatabase integration. Eg: Oracle Road traffic visualization. Enterprise application integration. Eg: JMS Message Oriented Middleware. Eg: Tibco Rendezvous, Advantages of PubSub communication paradigmDecoupled in three dimensions: space, time and synchronization All the subscriptions are handled at subscription manager. Efficient filtering criteria.Where WS-Eventing comes into play
- What is it?There are many applications in the real world where the two parties involve in communication. Clients of such a system, who produce information, are referred to as publishers, while clients that consume information are referred to as subscribers. Publishers generate messages to inform the external world when a certain event has occurred. Subscribers, who express their interest in events by means of subscriptions, are then notified about the occurrence of these eventsDrawbacks of P2P communication:Publishers and subscribers are tightly coupled Many communication channels. Publishers can not handle the subscribers individually when the number of subscribers grow.Examples of pub/sub: News publication. Mobile communication. Business process management. Eg: Microsoft BizTalk serverDatabase integration. Eg: Oracle Road traffic visualization. Enterprise application integration. Eg: JMS Message Oriented Middleware. Eg: Tibco Rendezvous, Advantages of PubSub communication paradigmDecoupled in three dimensions: space, time and synchronization All the subscriptions are handled at subscription manager. Efficient filtering criteria.Where WS-Eventing comes into play
- What is it?There are many applications in the real world where the two parties involve in communication. Clients of such a system, who produce information, are referred to as publishers, while clients that consume information are referred to as subscribers. Publishers generate messages to inform the external world when a certain event has occurred. Subscribers, who express their interest in events by means of subscriptions, are then notified about the occurrence of these eventsDrawbacks of P2P communication:Publishers and subscribers are tightly coupled Many communication channels. Publishers can not handle the subscribers individually when the number of subscribers grow.Examples of pub/sub: News publication. Mobile communication. Business process management. Eg: Microsoft BizTalk serverDatabase integration. Eg: Oracle Road traffic visualization. Enterprise application integration. Eg: JMS Message Oriented Middleware. Eg: Tibco Rendezvous, Advantages of PubSub communication paradigmDecoupled in three dimensions: space, time and synchronization All the subscriptions are handled at subscription manager. Efficient filtering criteria.Where WS-Eventing comes into play
- Inter broker communication interfacesDesign principles:Strategic extendable algorithmsSingleton classes for high cost operationsAchievements of desirable features in implementation:Scalability: Concurrency mechanism in publications – blocking thread safe queueDistribution of broker nodesEfficiency: In memory subscription storeAsynchronous routing (reduced response time)
- Middleware as a wholeSingle broker
- Middleware as a wholeSingle broker
- Middleware as a wholeSingle broker
- OAQ pub sub functionality is using Queue tables implemented in Oracle DB engines which communicates with each other and outside pubs and subs. Hence, all the operations of OAQ involves DB activities wheras Wihidum doesn't.