Misplaced Pages

TIBCO Rendezvous

Article snapshot taken from Wikipedia with creative commons attribution-sharealike license. Give it a read and then ask your questions in the chat. We can research this topic together.
Software for messaging between programs
This article has multiple issues. Please help improve it or discuss these issues on the talk page. (Learn how and when to remove these messages)
This article relies excessively on references to primary sources. Please improve this article by adding secondary or tertiary sources.
Find sources: "TIBCO Rendezvous" – news · newspapers · books · scholar · JSTOR (March 2007) (Learn how and when to remove this message)
The topic of this article may not meet Misplaced Pages's notability guidelines for products and services. Please help to demonstrate the notability of the topic by citing reliable secondary sources that are independent of the topic and provide significant coverage of it beyond a mere trivial mention. If notability cannot be shown, the article is likely to be merged, redirected, or deleted.
Find sources: "TIBCO Rendezvous" – news · newspapers · books · scholar · JSTOR (September 2015) (Learn how and when to remove this message)
(Learn how and when to remove this message)
TIBCO Rendezvous
Developer(s)TIBCO Software
Stable release8
Operating systemCross-platform
TypeMessage-oriented middleware
LicenseProprietary
Websitewww.tibco.com

TIBCO Rendezvous is a software product that provides a message bus for enterprise application integration (EAI).

Details

TIBCO provides messaging APIs in C, C++, Java, Visual Basic, Perl and .NET to provide messaging between two or more services.

The basic message passing is conceptually simple:

  • A message has a single subject composed of elements separated by periods. A message is sent to a single Rendezvous Daemon (though it may end up being broadcast onto Daemons).
  • A listener announces its subjects of interest to a Daemon (with a basic wildcard facility) and messages with matching subjects are delivered to it if the two daemons are 'connected' to each other (or indeed the same daemon).

Considerable "Enterprise" functionality is layered onto this if desired with Fault Tolerance/Reliable or Certified options possible, all implemented through the underlying basic messages.

The messages themselves can be viewed as typed name-value fields and/or number-value fields (the two identification mechanisms within a message can mix and match with certain restrictions). A message can itself contain sub-messages which themselves may contain sub-messages, and so on.

The quality of the respective API implementations varies considerably. The C++ library is simply a wrapper providing an OO view over the C implementation. Likewise the Java and .NET implementations wrap the C++ implementation. This has led to memory management issues with the .NET implementation (though not with the COM Interop version which is considerably more cumbersome).

External links

References


Stub icon

This programming-tool-related article is a stub. You can help Misplaced Pages by expanding it.

Categories: