History

Thales Macedo Garitezi 3ba65c4377 feat: poke the buffer workers when inflight is no longer full if max inflight = 1, then we only make progress based on the state timer, since the callbacks were not poking the buffer workers.		2023-01-17 16:48:48 -03:00
..
i18n	fix: remove time unit from duration fields description	2023-01-12 14:18:55 +01:00
include	feat(buffer_worker): refactor buffer/resource workers to always use queue	2023-01-05 10:15:09 -03:00
src	feat: poke the buffer workers when inflight is no longer full	2023-01-17 16:48:48 -03:00
test	refactor: enter running state directly	2023-01-17 16:48:48 -03:00
README.md	feat: add test cases for batching query	2022-08-10 00:34:35 +08:00
rebar.config	fix: drop no longer supported dialyzer option	2022-12-16 13:45:05 +03:00

README.md

emqx_resource

The emqx_resource is a behavior that manages configuration specs and runtime states for resources like mysql or redis backends.

It is intended to be used by the emqx_bridges and all other resources that need CRUD operations to their configs, and need to initialize the states when creating.

There can be foreign references between resource instances via resource-id. So they may find each other via this Id.

The main idea of the emqx resource is to put all the general code in a common lib, including the config operations (like config validation, config dump back to files), and the state management. And we put all the specific codes to the callback modules.

See

test/emqx_connector_demo.erl for a minimal emqx_resource implementation;
test/emqx_resource_SUITE.erl for examples of emqx_resource usage.