Architecture
Each appliance consists of 4 modules deployed in Tomcat containers as separate WAR files. For production systems, it is recommended that each module be deployed in a separate Tomcat instance (thus yielding four Tomcat processes). A sample storage configuration is outlined below where we’d use
Ramdisk for the short term store - in this storage stage, we’d store data at a granularity of an hour.
SSD/SAS drives for the medium term store - in this storage stage, we’d store data at a granularity of a day.
A NAS/SAN for the long term store - in this storage stage, we’d store data at a granularity of a year.

A wide variety of such configurations is possible and supported. For example, if you have a powerful enough NAS/SAN, you could write straight to the long term store; bypassing all the stages in between.
The long term store is shown outside the appliance as an example of a commonly deployed configuration. There is no necessity for the appliances to share any storage; so both of these configurations are possible.
Multiple appliances sending data into one long term store
Multiple appliances sending data into different long term stores