Once embedded NATS server is supported, allow the NATS API to be exposed optionally. This, in effect, turns NATS into an implementation detail and allows users to just interact with the Liftbridge API as a standalone service. In practice, this likely involves having NATS self-configure and providing a way for Liftbridge cluster nodes to connect to one another.
This depends on https://github.com/liftbridge-io/liftbridge/issues/19.
Once embedded NATS server is supported, allow the NATS API to be exposed optionally. This, in effect, turns NATS into an implementation detail and allows users to just interact with the Liftbridge API as a standalone service. In practice, this likely involves having NATS self-configure and providing a way for Liftbridge cluster nodes to connect to one another.