Ring Buffered Network Bus

This is version 14. It is not the current version, and thus it cannot be edited.
[Back to current version]   [Restore this version]

Properties:

• Uses a finite-sized ring buffer to handle data.
• The copy of most recent data is kept in memory and the rest is on disk. Size of both can be configured.
• Data on disk is called Archive.
• Data on memory is called Cache.
• Data is saved to and retrieved from the RBNB server by applications termed sources and sinks, respectively.
• Each source application generates its own ring buffer, which is managed by the RBNB server.
• Sink applications can request data from the RBNB server, which retrieves information from the appropriate ring buffer(s) and passes it back to the requesting sink application.
• Sources and sinks communicate with RBNB by passing messages via channel map objects.
• Each channel in a channel map is named and contains timestamped data.
• An RBNB frame is created each time a channel map is written/flushed to disk.
• Size of a frame is variable.
• The sizes of both the cache and the archive are defined in terms of the number of frames.
• Sink applications use channel maps to request data from the RBNB server in the following ways:
1. Subcribe:
2. Monitor:
3. Request:

There's a more complete Getting Started with Data Turbine document at the NEESit website.