On Thu, Feb 7, 2019 at 11:59 AM Jeremy Cline <jeremy(a)jcline.org> wrote:
3. Expose a consume-only AMQP broker to the public.
The advantage here is everything can use the same fedora-messaging
APIs (or any AMQP client) inside or outside infrastructure. The downside
is the service is exposed to the harsh world of the Internet.
Talking with Patrick before DevConf, I think this is the direction we
will ultimately go, but there are a number of deployment configurations
to consider so this isn't something you'll see tomorrow. I plan to do
some more research and present the options in detail in the coming
weeks.
This would be fantastic to have the broker publicly accessible.
Looking forward to seeing more information about this.
- Ken