ElastiCubes can run both on a local desktop machine and a centralized server accessible by multiple concurrent users.  ElastiCubes can be seamlessly moved from a local machine to a server machine and vice versa.

Shared ElastiCube Architecture

In a shared ElastiCube architecture, ElastiCubes service multiple concurrent users.  In this case, the Abacus ElastiCube Server module needs to be installed on the server machine.  The ElastiCubes on the server are usually set to import new data on a scheduled basis, usually when end-users do not access the ElastiCubes.

 

 

 

Local ElastiCube Architecture

Local ElastiCube architecture is often used in two scenarios:

1. A single user creating ElastiCubes on their own computer to perform personal analysis
2. A developer creating ElastiCubes locally for testing and debugging purposes, prior to setting up the ElastiCube on a production server.

ElastiCubes created on a local server can be easily moved to an ElastiCube server by exporting the ElastiCube data on the local computer and importing it on the server.

 

When no server exists and sharing of ElastiCubes is required, the ElastiCube data can be exported and placed on an accessible shared storage resource, from which other users can import it into their own local server.