Endpoints

TIBCO FTL software uses the concept of an endpoint to simplify arrangements when multiple transports carry the same message stream. An endpoint abstracts all the transport details into a simple name. This abstraction insulates application programs from those details.

Transports are analogous to communications wiring behind the walls of an office building, while endpoints are like the plug and wall socket through which devices connect to that wiring. The designers and users of those devices do not need to know the specific communication technology behind the walls.

  • One Endpoint Many Subscribers
    In this first example, the message stream from one publishing endpoint fans out to many subscribers that require different transport technologies. Endpoints help manage this complexity, and separate the responsibilities of programmers from the responsibilities of administrators.
  • One Endpoint Many Publishers
    This second example extends the previous example by adding another publisher. Endpoints hide any additional complexity from programmers, and simplify administrative tasks.
  • Distinct Endpoints in One Program
    In the two preceding examples, each program used only one endpoint. In this third example, we consider a reason that a program might need more than one endpoint.