yzhao244 commented on issue #339: URL: https://github.com/apache/incubator-eventmesh/issues/339#issuecomment-875765278
@xwm1992 Thanks for the questions. :) . The followings are replies.. Sorry about my drawings are a bit rough. :)  * The interaction between the Schema Registry and the Database is not represented in this figure; The database which is H2 In-memory DB in this case persists schemas and subjects data. REST APIs which follow OpenSchema specification will be exposed by the EventMesh Schema Registry for performing CRUD against schema and subject tables in DB. FYI, the followings are list of REST APIs that EventMesh Schema Registry according to OpenSchema standards. `` POST /subjects/(string: subject)/ POST /subjects/(string: subject)/versions POST /compatibility/subjects/(string: subject)/versions/(version: version) GET /subjects GET /subjects/(string: subject) GET /subjects/(string: subject)/versions GET /subjects/(string: subject)/versions/(version: version)/schema GET /schemas/ids/{string: id} GET /schemas/ids/{string: id}/subjects GET /config/(string: subject) PUT /config/(string: subject) DELETE /subjects/(string: subject)/versions/(version: version) DELETE /subjects/(string: subject) `` * What is the relationship between **topic** and **schema id**, at present topic store the messages or events, are these represent as data in your figure? Yes, topic still stores message or events as how it does today. Since OpenSchema factors serialization into its specification, it makes sense that EventMesh Schema Registry supports serializing/deserializing event. Therefore, in the future, a topic can store serialized event based on user defined format(json, avro and so on). * What kind of data does the database and topic need to store 1. Database stores subject and schema specifications (name, schema content, versions , compatibility and so on) defined by end-user when using EventMesh Schema Registry REST APIs. The followings are my proposed DB schemas for subject and schema tables. 2. topic stores events and messages.   -- 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: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
