Which Backstage DB should be used?
Opened this issue · 3 comments
Cassandra may not be a good choice for the Backstage DB, used for the buffering of alarm inputs. Some online DBs (e.g. REDIS) may be a better solution. This should be investigated during the design phase.
This issue was suggested by CTA during the F2F meeting on 12 December 2016.
In terms of interface development there is a potential of synergy with the Array Performance Monitoring System (APMS).
The BSDB is meant to support the functioning of the IAS at run time. I still have to evaluate how to implement the Long Term DataBase to permanently store alarms and if it is the case, monitor points. For the latter I also see a potential synergy.
All of that will be clear when I finish the architecture document.
Due to the big amount of data produced by the external alarm system we need a performant online database to reduce the latency between when the value is produced, stored in the BSDB and finally delivered to the ASCEs for processing.
Cassandra is very performant when writing data but much less for reading. For that reason it is not the best solution for our case. We could still use Cassandra as Long Term DataBase (LTDB).