Speakers:

During the webinar, these questions from the attendees were answered:

– What is the differences for scaling on Cloud or on Regular VM (on premise) servers?
– I would like to be given a very rough way to estimate required resources on the host PC. For example, for a system that may have 1, 2, 5, 10 doctors concurrently, how many compute resources would I need for a smooth experience?
– Do we need a MedDream High Availability license for every node that we deploy? Or do we purchase a single High Availability license that allows for us to deploy all our necessary pools and nodes?
– By enabling MedDream’s own caching functions, where we have several endpoints that will perform caching based on those endpoints, can I still use MedDream’s HA mode? Can we guarantee the functionality of caching and HA within a Kubernetes cluster?
– Do you provide k8s resource yaml examples? Other templates (Kustomize, Terraform)?
– Have you tested in Google Cloud GKE Standard or Autopilot clusters? Is it able to connect to Google Healthcare API?
– Is the github AWS setup using multiple MedDream pools for splitting up caching, viewing and cleaning up as you described before?
– What about support of HA for Azure Health Data Services?