Architecture
The TIBCO ActiveSpaces Connector for Apache Pulsar consumes messages from an Apache Pulsar topic and inserts the message data as rows into a running ActiveSpaces grid, where data can be kept and efficiently queried. The following figure illustrates the interactions among the components of TIBCO Messaging as messages flow from Apache Pulsar producers to ActiveSpaces tables.
Connector for Apache Pulsar
The TIBCO ActiveSpaces Connector for Apache Pulsar is a sink connector that appears to ActiveSpaces as an ActiveSpaces client application. You configure the connector to write all received messages to a specified ActiveSpaces table. You can run one or more instances of the connector in parallel where each instance can be configured to write to a different ActiveSpaces table.
The Sink Connector receives Apache Pulsar messages based on a topic configured in the sink connector configuration settings, converts their format from FTL JSON to ActiveSpaces row data, and then sends the data to ActiveSpaces using ActiveSpaces Proxy.
You can run one or more instances of the connector in parallel where each instance can be configured to read from a different Apache Pulsar topic. When combined with the ability to write receive messages to a specific ActiveSpaces table, you can build a matrix to handle any combination of topic-to-table mapping.
Upon receiving the data, the ActiveSpaces Proxy adds the data to the table. If the table does not exist, it is automatically created (when configured to do so).
Message Representations
The connector accepts a specific JSON message representation for messages received from Apache Pulsar. This format is described in FTL JSON Message Format Reference.