Dušan Borovčanin
4e9480266e
* Update RE to use pure Go instead of Lua bindings Signed-off-by: Dusan Borovcanin <borovcanindusan1@gmail.com> * Fix RE DB Signed-off-by: Dusan Borovcanin <borovcanindusan1@gmail.com> * Fix nil error case Signed-off-by: Dusan Borovcanin <borovcanindusan1@gmail.com> * Fix adding query Signed-off-by: Dusan Borovcanin <borovcanindusan1@gmail.com> * Fix constraints on kind and logic type Signed-off-by: Dusan Borovcanin <borovcanindusan1@gmail.com> * Update RE to use multiple outputs Signed-off-by: Dusan Borovcanin <borovcanindusan1@gmail.com> * Update PG writer output Signed-off-by: Dusan Borovcanin <borovcanindusan1@gmail.com> * Fix protocol error in MQTT forwareder Signed-off-by: Dusan Borovcanin <borovcanindusan1@gmail.com> * Fix rules error handings Signed-off-by: Dusan Borovcanin <borovcanindusan1@gmail.com> * Add false value check Signed-off-by: Dusan Borovcanin <borovcanindusan1@gmail.com> * Fix topic filtering Signed-off-by: Dusan Borovcanin <borovcanindusan1@gmail.com> * Fix consumers Signed-off-by: Dusan Borovcanin <borovcanindusan1@gmail.com> * Fix publisher Signed-off-by: Dusan Borovcanin <borovcanindusan1@gmail.com> * Fix mocks Signed-off-by: Dusan Borovcanin <borovcanindusan1@gmail.com> * Fix tests Signed-off-by: Dusan Borovcanin <borovcanindusan1@gmail.com> --------- Signed-off-by: Dusan Borovcanin <borovcanindusan1@gmail.com>
Consumers
Consumers provide an abstraction of various SuperMQ consumers.
SuperMQ consumer is a generic service that can handle received messages - consume them.
The message is not necessarily a SuperMQ message - before consuming, SuperMQ message can
be transformed into any valid format that specific consumer can understand. For example,
writers are consumers that can take a SenML or JSON message and store it.
Consumers are optional services and are treated as plugins. In order to run consumer services, core services must be up and running.
For an in-depth explanation of the usage of consumers, as well as thorough
understanding of SuperMQ, please check out the official documentation.
For more information about service capabilities and its usage, please check out the API documentation.