I have a bunch of C++ applications that want to use the low latency c-media driver for the lowest latency. There is also a need to access past messages when a new subscriber joins or an existing one crashes and restarts. Want to leverage the archiving media driver to gap fill in these scenarios.
Want to know if this setup is possible
- run the c media driver with a local publisher and local subscribers
- run the archive media driver to record the messages flowing in the c-media-driver
- allow the apps to access the archive-media-driver to replay past messages and join the c-media-driver live publication
Not sure what configurations to use for setting up the two media drivers so the archiving media driver records the c-media-driver streams
Yes it is possible to run a C media driver and a Java media driver with associated Archive. It is also possible to run an Archive alongside a C media driver without a Java media driver. The ArchivingMediaDriver is an aggregation of an Archive and a Java MediaDriver bundled for convenience.
BTW the Java media driver is on par with the C media driver for latency and throughput when using the BSD sockets API which comes in the open source version. A significant latency reduction and throughput increase can be achieved with the kernel bypass extensions for the C driver which are available as a premium component.