cddfdf4038
* init swaggerui action Signed-off-by: Ivan Milosevic <iva@blokovi.com> * remove dep Signed-off-by: Ivan Milosevic <iva@blokovi.com> * fix filename Signed-off-by: Ivan Milosevic <iva@blokovi.com> * add checkout master Signed-off-by: Ivan Milosevic <iva@blokovi.com> * try diffrent action Signed-off-by: Ivan Milosevic <iva@blokovi.com> * change path for search Signed-off-by: Ivan Milosevic <iva@blokovi.com> * change path Signed-off-by: Ivan Milosevic <iva@blokovi.com> * change path Signed-off-by: Ivan Milosevic <iva@blokovi.com> * put almost all openapi spec to one folder Signed-off-by: Ivan Milosevic <iva@blokovi.com> * fix pattern Signed-off-by: Ivan Milosevic <iva@blokovi.com> * try servers changing Signed-off-by: Ivan Milosevic <iva@blokovi.com> * test k8s Signed-off-by: Ivan Milosevic <iva@blokovi.com> * remove servers Signed-off-by: Ivan Milosevic <iva@blokovi.com> * use blokovi action Signed-off-by: Ivan Milosevic <iva@blokovi.com> * add cname Signed-off-by: Ivan Milosevic <iva@blokovi.com> * Parameters ready for PR to upstream Signed-off-by: Ivan Milosevic <iva@blokovi.com> * Fix errors in Auth openapi spec Signed-off-by: Ivan Milosevic <iva@blokovi.com> * remove white line Signed-off-by: Ivan Milosevic <iva@blokovi.com> * fix link in README Signed-off-by: Ivan Milosevic <iva@blokovi.com> * change docs and api links in readme files Signed-off-by: Ivan Milosevic <iva@blokovi.com> |
||
|---|---|---|
| .. | ||
| notifiers | ||
| writers | ||
| README.md | ||
| consumer.go | ||
| docs.go | ||
| messages.go | ||
README.md
Consumers
Consumers provide an abstraction of various Mainflux consumers.
Mainflux consumer is a generic service that can handle received messages - consume them.
The message is not necessarily a Mainflux message - before consuming, Mainflux 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 Mainflux, please check out the official documentation.
For more information about service capabilities and its usage, please check out the API documentation.