...
Installation of Operator Clients
| non-exhaustive list of options | remarks |
|---|---|
| database http proxy using SSL | |
| Azure Virtual Desktop | only in Azure |
| ssh + mobaxterm |
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 adjusted 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.
...
An estimate for the cost for a basic/medium-sized Delft-FEWS system in the cloud would be around 12k€- 15k€. Many cloud providers offer a "cloud calculator" to calculate, upfront, the expected cost, e.g. Azure calculator. | The estimate differs per Delft-FEWS system.
Data size and egress
Egress, i.e.g. data traffic transferred from the cloud environment, is not free. The egress costs depend on the type of connection and on the amount of egress data. Ingress, e.g. data traffic into the cloud environment is often free of cost. See See How to calculate the right Azure outbound capacity and choose the best egress option. Egress can be, partly, configured in the Delft-FEWS. Also the location of the operator client (in the cloud or on-premise) effects the egress.
...