FTL Server: Message Broker Default Operation

That is, when you run one FTL server without supplying any configuration file, it automatically operates as a message broker. Moreover, when you run three FTL servers without supplying any configuration file, they automatically join together to operate as a message broker.

• Each FTL server provides a realm service and a persistence service.
• The persistence services arrange themselves in a default cluster.
• The default realm definition includes a set of default persistence stores and default persistence clusters.
• The realm defines a default application which uses the default non-persistent store and the dynamic standard durable template named ftl.pubsub.template.
• Any application definition can specify a server-defined transport, Server, which automatically connects with the persistence services of the message broker.
• Clients connecting to any of the FTL servers can send and receive messages through the message broker.