emqx/apps/emqx_bridge_pulsar
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 feat: implement Pulsar Producer bridge (e5.0) 2023-04-24 10:28:26 -03:00
include feat: implement Pulsar Producer bridge (e5.0) 2023-04-24 10:28:26 -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): use shared list of reboot apps and add bridges to reboot list 2023-07-19 20:15:42 -03:00
.gitignore feat: implement Pulsar Producer bridge (e5.0) 2023-04-24 10:28:26 -03:00
BSL.txt feat: implement Pulsar Producer bridge (e5.0) 2023-04-24 10:28:26 -03:00
README.md docs: hide the not-ready document links 2023-05-15 11:20:23 +08:00
docker-ct feat: implement Pulsar Producer bridge (e5.0) 2023-04-24 10:28:26 -03:00
rebar.config fix(pulsar): update pulsar -> 0.8.3 2023-06-12 10:29:40 -03:00

README.md

Pulsar Data Integration Bridge

This application houses the Pulsar Producer data integration bridge for EMQX Enterprise Edition. It provides the means to connect to Pulsar and publish messages to it.

Currently, our Pulsar Producer library 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 on Apache Pulsar, please see its official site.

Contributing

Please see our contributing.md.

License

EMQ Business Source License 1.1, refer to LICENSE.