Open topic with navigation

# Message Broker Pattern

You can use the FTL server to implement a message broker, an intermediate store-and-forward service between publishers and subscribers.

The default configuration of an FTL server implements a message broker. 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.

When application programs interact with the message broker, its default behavior uses a non-persistent store and standard durables. This behavior is equivalent, in EMS terminology, to non-persistent messaging through topics. (You can explicitly configure persistent messaging behavior and queue behavior.)

Did you find this helpful?

Yes No
Great!
Thanks for taking the time to give us some feedback.
Sorry about that

Why wasn't this helpful? (check all that apply)

Could not find what I was looking for
Instructions confusing or unclear
Instructions did not work

Want to tell us more?

Please select at least one option or provide details about the issue!!

Error occurred while submitting feedback.

Error2 occurred while submitting feedback.

TIBCO FTL® - Enterprise Edition

Copyright © 2009-2024. Cloud Software Group, Inc. All Rights Reserved.