HeraldAchievingaGlobalEventNotificationService.pptVIP

hello! Herald: Achieving a Global Event Notification Service Marvin Theimer Joint work with Michael B. Jones, Helen Wang, Alec Wolman Microsoft Research Redmond, Washington What this Talk will be About Event notification: more than just simple multicast. Problems you run into at large scale. Herald event notification service: Design criteria and initial solution strategies. Some results on overlay networks. Event Notification: It’s more than just Simple Multicast Additional types of functionality: Reliability/Persistence QoS Security Richer publish/subscribe semantics Herald will be exploring a subset of the potential design space. Multicast + Reliability/Persistence Multicast + QoS Multicast + Security Richer Publish/Subscribe Semantics Global Event Notification Services Internet Scalability is Hard Internet scale implies that individual systems can never have complete information: Information will be unavailable, stale or even inaccurate Some participants will always be unreachable Partitions, disconnection, and node downtime will always be occurring somewhere There will (probably) not be a single organization that owns the entire event notification infrastructure. Hence a federated design is required. Scaling to “Extreme” Event Notification 1011 computers and embedded systems in the world (soon): 1011 event topics 1011 publishers subscribers in aggregate Global audiences: 1010 subscribers for some event topics “Trust no one”: Potentially 1010 federated security domains Some Event Notification Semantics Don’t Scale Well Fully general subscription semantics Simultaneous delivery times Highly available, reliable, ordered events from multiple publishers Global Event Notification is Hard to Validate What kinds of work loads? Instant messaging++ ? Billions of inter-connected gizmos (BIG)? eCommerce? How do you explore and validate a design that should scale to tens of billions? Rule of thumb: every order of magnitude results in qualitatively different syste