xregistry-looking-beyond-cloudevents-xregistry-yun-sakaki-cloudevents-leo-li-red-hat.pdf

1、xRegistry Looking Beyond CloudEventsLeo Li-Red Hat Hello!Leo LiSoftware Engineering Intern Red HatKnative Eventing MaintainerLeo6LeoAgendaCloudEvents(CE):Intro&Community updates1.Understand CE:analogy of delivery package2.Updates from the community3.What is the next step/direction for CloudEvents?xR

2、egistry:Event Discovery1.Understand current problems:Checkpoints analogy2.How xRegistry resolves the current problem?3.xRegistry work in practice4.xRegistry CLIQ&ACloudEventsA specification for describing event metadata in a common wayCloudEventsCloudEvents ExampleWithin each country,there are diffe

3、rent courier services CloudEventsSend a package from China to CanadaCloudEventsWithin China,the package has the Chinese Courier labelCloudEventsWhen leaving China,the package will have international courier labelCloudEventsWhen arriving Canada,the package will have the Canadian Courier labelCloudEve

4、ntsIf there is a universal label that all couriers can understand,No need to change label every time.CloudEventsThats why we name CloudEvents as that magic universal label at the beginning.CloudEvents ExampleSimilarly,events move between cloud servicesData:“Hello World”“data”:“Hello World 1”MQTTClou

5、d Service 1Cloud Service 2 “data”:“Hello World 1”Different Cloud Services may have protocolsEvents Are Everywhere “data”:“Hello World 1”MiddlewareMQTTCloud Service 1Cloud Service 2Events Are Everywhere “data”:“Im at KubeCon China!”“data”:“I love HK!”“data”:“Hello World!”Varying:FormatsSchemasBusines

6、s LogicMiddlewareHTTPMQTTNATSCloud Service 3Cloud Service 1Cloud Service 2Cloud Service 4Cloud Service 5Events Are EverywhereSmart middleware(selective routing)is costlyEvent ConsumerEvent ProducerDelivery ProtocolBusiness LogicProtocol LibraryCustom Glue(MQTT)Custom Glue(Kafka)Before CloudEventsSou