Investigate communication

[anna0207]

Investigate communication: Ideas:

• MVC with signalR
• Real-time database synchronization provided by Firebase
• Create REST WebApi between DB and front-end (and maybe also between Job and DB) (WINNER)

[anna0207]

Discussion:

2 databases (raw data & processed data)

The web-App is not aware of any server-side - it only communicates with databases The server-side can be replaced by a simple job hosted in the cloud, which synchronizes the two databases.

• Simple presentation directly from JSON format
• More seperation between the components

The web-App is ONLY aware of the server-side - The server-side then handle all database communication

• The server-side might act as the bottle-neck, because it is solely responsible for sending DB data AND data processing
• Only one communication link from the client-side
• The raw data DB could be retrieved directly from the client-side - avoiding an extra link

The WebApp has both connection with server-side and raw DB

• Avoids overhead links
• Only the processed data can be delayed in bottleneck (more parallel connections)

[anna0207]

Discussion with Aslak: If choosing architecture 1 - can create multiple jobs for different processing (Graph processing) pipeline

For security reasons create a REST layer between WebApp and DB to handle all requests (both Job and front-end)