You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@eventmesh.apache.org by GitBox <gi...@apache.org> on 2021/08/04 16:14:14 UTC

[GitHub] [incubator-eventmesh] jinrongluo commented on issue #339: Integrate With OpenSchema

jinrongluo commented on issue #339:
URL: https://github.com/apache/incubator-eventmesh/issues/339#issuecomment-892789427


   @JunjieChou @qqeasonchen @yzhao244 
   
   Hi Junjie, Thanks for your proposal on Schema Registry design. I agree overall design and the example steps of how eventmesh are using Schema Registry to process the events. I have two comments below:
   
   1.  Schema Registry API is part of EventMesh administrative API, In the future we can have other admin APIs such as Topic API, and subscription API. See issue #346, and issue #349 All these admin APIs can be group into a new module of eventmesh: **eventmesh-rest** module. This module will be running as part of eventmesh runtime. And this module includes the Schema Registry Runtime in @JunjieChou 's design.  See issue #435 
      
   Also, It is much lightweight to run Schema Registry Runtime as part of EventMesh runtime process. Deployment and service upgrade  only deal with single runtime process.
   
   When scaling up the EventMesh runtime instances, Schema Registry Runtime will scale up along with it. it provides high availability.   Since Schema APIs are stateless, we can scale up Schema Registry Runtime.
     
   Thus, from the perspectives of extensibility, deployment maintenance, and high availability, I would say running Schema Registry as part of EventMesh Runtime process.
   
   2.  For database, I would say it is not dedicated to Schema Registry.  In the future it can be used to store other EventMesh assets, such as topics and subscriptions. see issue #349 


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: dev-unsubscribe@eventmesh.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org



---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@eventmesh.apache.org
For additional commands, e-mail: dev-help@eventmesh.apache.org