History

Andrew Mayorov a5fc26736d refactor(mqttconn): split ingress/egress into 2 separate pools Each with a more refined set of responsibilities, at the cost of slight code duplication. Also provide two different config fields for each pool size.		2023-05-30 17:21:44 +03:00
..
etc	chore: change the enable_pipelining default value	2022-05-31 19:32:53 +08:00
include	fix(rule_engine): count referenced bridges in `from` clauses as dependencies (rv5.0)	2023-03-28 10:31:10 -03:00
src	Merge pull request #10867 from zmstone/0530-merge-release-50-to-master	2023-05-30 09:54:57 +02:00
test	refactor(mqttconn): split ingress/egress into 2 separate pools	2023-05-30 17:21:44 +03:00
.gitignore	refactor(bridge): rename emqx_data_bridge to emqx_bridge	2021-09-10 11:43:03 +08:00
README.md	docs(README): EMQ X -> EMQX	2022-02-15 16:19:26 +01:00
rebar.config	refactor: move emqx_json to emqx_utils_json	2023-04-14 13:31:27 +02:00

README.md

emqx_bridge

EMQX Data Bridge is an application that managing the resources (see emqx_resource) used by emqx rule engine.

It provides CRUD HTTP APIs of the resources, and is also responsible for loading the resources at startup, and saving configs of resources to data/ after configs updated.

The application depends on emqx_connector as that's where all the callback modules of connector resources placed.