Flussonic supports different modes for combining servers into cluster, here you can learn what you can achive with Flussonic installed on several servers.
Please note that there is no such thing as "simple cluster", you always need to understand what exactly you want to achieve by installing several servers: it may be reducing downtime in case of failure, increasing total service throughput or sharing storage between servers.
Please read the following manual to get better idea of how Flussonic can help you.
Below are a few examples of Flussonic cluster configuration:
- Capture streams on one or several servers and then automatically restream them to another with instant failover
- Instant access from restreamer to streams published on source
- Remote access to DVR captured on source server
- Capturing and transcoding streams on group of servers with instant automatic failover
- Automatic and managed load balancing clients between servers in group of peers
Here we explain some terminology that can help you not to get lost:
A group of servers with Flussonic installed to work together in the same service.
Flussonic which already captures (or can start to capture streams "on demand") and can be used as a source for restreaming server.
Flussonic which can receive (or already receives) streams from one or more sources.
Configuration consisting from source and restreaming servers that allows restreaming servers to automatically receive live streams and DVR captured on source servers.
Flussonic which is located nearby another Flussonic. Only one of them can capture some stream. It can be useful when capturing the stream on both servers is very expensive, for example, when the stream is an IP camera connected through an unreliable connection.
Configuration of several peer Flussonic servers that ensures that each stream is captured only once. If one of the peers fails, the other peers will begin to capture its streams.