emqx/apps/emqx_bridge_kafka
Thales Macedo Garitezi 6cd503865b fix(machine_boot): ensure emqx_bridge starts after its companion apps
We need to reverse the dependency of `emqx_bridge` and `emqx_bridge_*`, because the former
loads and starts bridges during its application startup.  If the individual bridge
application being loaded has not started with its dependencies, the supervision tree will
not be ready for that.
2023-07-20 13:11:44 -03:00
..
etc refactor(kafka_bridge): move kafka bridge into its own app 2023-04-12 13:54:45 -03:00
src fix(machine_boot): ensure emqx_bridge starts after its companion apps 2023-07-20 13:11:44 -03:00
test fix(machine_boot): ensure emqx_bridge starts after its companion apps 2023-07-20 13:11:44 -03:00
BSL.txt refactor(kafka_bridge): move kafka bridge into its own app 2023-04-12 13:54:45 -03:00
docker-ct refactor(kafka_bridge): move kafka bridge into its own app 2023-04-12 13:54:45 -03:00
README.md docs: fix invalid links 2023-05-15 11:18:09 +08:00
rebar.config feat(kafka): check whether target topic exists 2023-06-21 15:00:35 -03:00

Kafka Data Integration Bridge

This application houses the Kafka Producer and Consumer data integration bridges for EMQX Enterprise Edition. It provides the means to connect to Kafka and publish/consume messages to/from it.

Currently, our Kafka Producer library (wolff) has its own replayq buffering implementation, so this bridge does not require buffer workers from emqx_resource. It implements the connection management and interaction without need for a separate connector app, since it's not used by authentication and authorization applications.

Documentation links

For more information about Apache Kafka, please see its official site.

Configurations

Please see Ingest Data into Kafka for more detailed info.

Contributing

Please see our contributing.md.

License

EMQ Business Source License 1.1, refer to LICENSE.