Open topic with navigation

# Messaging Concepts

Application programs (clients) use TIBCO FTL software to communicate by sending messages to one another. Programs send messages using publisher objects, and receive messages using subscriber objects.

FTL typically uses a message broker architecture. For low latency, FTL can be configured such that messages travel directly between peer application programs.

## Messages and Fields

A message is a structured unit of data. The structure is flexible, and developers tailor the structure to the needs of the application.

Each message consists of a set of named fields. Each field can contain a value of a specific data type.

## One-to-Many Communication

Publishers can send messages using one-to-many communication. These messages can reach potentially many subscribers.

A subscriber can use a content matcher to receive only those messages in which a particular set of fields contain specific values.

## One-to-One Communication

For efficient one-to-one communication, publishers can also send messages that can reach one specific inbox subscriber. Theinbox data structure uniquely identifies an inbox subscriber.

Inbox subscribers cannot use content matchers. An inbox subscriber receives all messages directed to it.

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.