...
| component | cloud readiness status | Room for improvements | ||
|---|---|---|---|---|
| Database | Both db docker containers as well as managed instances are already possible. Managed instances require minor adjustments of the db scripts. | Support one set of database scripts for all db flavors managed and unmanaged. | ||
Master Controller | Yes | Enable service replication | ||
Admin Interface | Yes | |||
Operator Client / SA | Use Azure Virtual Desktop or Database proxy | |||
Config Manager | Use Azure Virtual Desktop or Database proxy or API | |||
Forecasting Shell Server | Yes | Facilitate auto scaling. | ||
WebServices | Yes | |||
DatabaseProxy | Yes | |||
OpenArchive | Yes | Fileshares | cloud-specific |
Delft-FEWS in the cloud
Delft-FEWS Hardware and software requirements
...
| non-exhaustive list of options | remarks |
|---|---|
| database http proxy using SSL | |
| Azure Virtual Desktop | only in Azure |
| ssh + mobaxterm | |
| Citrix | Can be integrated with most cloud providers |
| Apache Guacamole |
Use of managed services
There is no actual requirement for the Delft-FEWS components to use managed services. Managed services can be used as long performance is not affected. As an example, customers that are using SQLServer database replication between different geographical locations reported database timeouts. In response, we've improved our software, removed database indexes and added reconnection strategy for these problems. Since we expect Delft-FEWS users add many more simultaneous running Forecasting Shell servers in the future, we expect / foresee more challenges in this area. It is much better not to use the automated placement of database indexes.
...