Geographically Distributed Deployments
In geographically distributed deployments your JSA deployment might be impacted by intermittent or poor connectivity to remote data centers. You might also be impacted by local regulations, such as complying with specific state or country regulations to keep data in the place of origin. Both of these situations require that you keep collectors on site. If you must keep data in the place of origin, then you must keep the processor on site.
For example, your company is growing and this growth not only increases activity in the network, but it also requires that you expand your JSA deployment to other countries. Data retention laws vary from country to country, so the JSA deployment must be planned with these regulations in mind.
You note these following conditions:
In case of event or flow collection from remote office locations that has intermittent connectivity, we may use a store-and-forward Event Collector which can implement scheduled and rate-limited forwarding options. The scheduled and rate-limited connections compensate for intermittent network connectivity and ensures that the requirement for more bandwidth is avoided during regular business hours.
If you are constantly searching for data on a remote processor, it is better to have that processor on the same high-speed network segment as the JSA console. If the bandwidth between the JSA console and remote processor is not good, you might experience latency with your searches, especially when you are doing multiple concurrent searches.