[GitHub] [incubator-eventmesh] jinrongluo commented on issue #349: Suggestion of Event Subscription management and persistence

[GitBox <gi...@apache.org>]

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


   > @jinrongluo Would you like to share some new desgin with us if you like ?
   
   The new design is to introduce three new modules in the EventMesh project.
   
   1. **eventmesh-rest** module. This module is to refactor the eventmesh runtime -> admin code into a separate new module. We can add more admin REST APIs into this module.  /subscriptions  API will be in this new module
   
   /topics API will be add to this module too. As for implementation, It can invoke RocketMQ's ./mqadmin command to perform the topic operations: create/update topic, delete topic.
   
   2. **eventmesh-store-api**  module.  EventMesh needs to persist data into database. As mentioned in this issue. subscriptions need to persist into database to preserve the data in case of server restart. This is the database interface module. It provides interface of database CRUD operations.
   
   3. **eventmesh-store-h2**  module. This is H2 reference implementation of eventmesh-store-api. Data such subscriptions are store into H2 database and write back to file system
   
   
   


-- 
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