Application Design

  • Structuring Programs
    These steps outline the main structural components of most application programs that communicate using TIBCO FTL.
  • Application Instance Identifier
    Administrators can arrange transports to implement endpoints in different ways, and select among them at runtime using an application instance identifier.
  • Callbacks and Recursive Dispatch
    When designing application callbacks, do not recursively dispatch the same event queue.
  • Inline Mode
    Programs that receive time-sensitive messages can use inline mode to favor low latency over high throughput. Inline mode reduces inbound message latency by consolidating transport I/O and message callback processing into one thread.
  • Request and Reply
    Request/reply is an important communication pattern. Proper use of this pattern places requirements on the runtime environment.
  • Recovery of a Disabled Process Restart versus Reopen the Realm
    When the realm server disables an application process, the application can recover in one of two ways: either create a new objects and resume operation, or exit and restart.
  • Clean-Up
    Design programs to behave appropriately when they exit, and when they create a new realm object and its associated objects. (For example, creating new realm objects could be a recovery path after the realm server disables the client process.)
  • Consolidation with Loose Coupling
    With process transports, program threads within a process can communicate with one another by publishing and subscribing to messages. The main use case for process transports is consolidation of several application processes into one process, to boost performance by decreasing message latency.