emqx/apps/emqx_schema_registry
Zaiming (Stone) Shi 10c1245125 refactor: change schema registry SERD_TAB to ets
Prior to this change, it's a mria/mnesia table
which may cause nodes to overwrite each other.
2024-02-28 23:13:07 +01:00
..
etc refactor(schema_registry): refactor schema registry app and modules 2023-07-12 09:24:15 -03:00
include refactor: change schema registry SERD_TAB to ets 2024-02-28 23:13:07 +01:00
priv refactor(schema_registry): refactor schema registry app and modules 2023-07-12 09:24:15 -03:00
src refactor: change schema registry SERD_TAB to ets 2024-02-28 23:13:07 +01:00
test refactor: change schema registry SERD_TAB to ets 2024-02-28 23:13:07 +01:00
BSL.txt chore: update BSL license change date 2024-01-29 16:47:31 +01:00
README.md refactor(schema_registry): refactor schema registry app and modules 2023-07-12 09:24:15 -03:00
rebar.config refactor: change schema registry SERD_TAB to ets 2024-02-28 23:13:07 +01:00

README.md

EMQX Schema Registry

EMQX Schema Registry for managing various of schemas for decoding/encoding messages.

To use schema in rule engine, a schema name should be passed to the SQL functions that decode/encode data, like:

SELECT
     schema_decode('sensor_notify', payload) as payload
FROM
     "message.publish"
WHERE
     topic = 't/1'

Using schema registry with rule engine

                      +---------------------------+
                     |                           |
 Events/Msgs         |                           |   Events/Msgs
 -------------------->           EMQX            |------------------>
                     |                           |
                     |                           |
                     +-------------|-------------+
                                   |
                             HOOK  |
                                   |
                     +-------------v-------------+           +----------+
                     |                           |   Data    |          |
                     |        Rule Engine        ------------- Backends |
                     |                           |           |          |
                     +------|-------------|------+           +----------+
                            |^            |^
                      Decode||            ||Encode
                            ||            ||
                     +------v|------------v|-----+
                     |                           |
                     |      Schema Registry      |
                     |                           |
                     +---------------------------+

Architecture

                              |              |
                       Decode |    [APIs]    | Encode
                              |              |
                              |              |           [Registry]
                       +------v--------------v------+
    REGISTER SCHEMA    |                            |
       INSTANCE        |                            |    +--------+
    ------------------->                            |    |        |
[Management APIs]      |       Schema Registry      ------ Schema |
                       |                            |    |        |
                       |                            |    +--------+
                       |                            |
                       +----------------------------+
                            /        |        \
                       +---/---+ +---|----+ +---\---+
                       |       | |        | |       |
      [Decoders]       | Avro  | |ProtoBuf| |Others |
                       |       | |        | |       |
                       +-------+ +--------+ +-------+

  • Register schema instance: adds a new instance of a schema of a certain type. For example, when the user may have several Avro or Protobuf schemas that they wish to use with different data flows.

Documentation

Contributing

Please see our contributing.md.

License

EMQ Business Source License 1.1, refer to LICENSE.