what if multiple processes need to consume the data
What if one consumer is a java app athat needs the even in kafka?
And what if you do not want a bottleneck gen server for the latest data but an ETS table ?
You can never cover all the cases I guess, so the best is to not close doors.
If you really want your library to force usage of Phoenix.PubSub then maybe accepting an option for the topic is ok. Or a topic prefix maybe. And then a tuple {YourLibrary, :actual_name} as the event name could work, so if the user provides a topic that other publishers publish to, there is still a way to match your library’s messages.
Edit; but I would just do both. Accept a callback where the default implementation (if no option given) is a broadcast to Phoenix.PubSub. And pass all the options given to your library when calling the callback.
