We rely on a handful of servers and services to power ViewMedica.
Global Content Delivery
To ensure fast, low-latency access to ViewMedica content regardless of where you're located, we distribute static assets through two industry-leading content delivery networks (CDNs): AWS CloudFront and Cloudflare.
AWS CloudFront
CloudFront serves our static assets to our end users from edge locations around the world rather than a single central server.
Currently enabled regions:
Region | Locations |
United States | N. Virginia, Ohio, N. California, Oregon |
Canada | Central |
Europe | Frankfurt, Ireland, London, Paris, Stockholm |
Asia Pacific | Mumbai, Osaka, Seoul, Singapore, Sydney, Tokyo |
South America | São Paulo |
Please refer to this AWS documentation page for an up-to-date list of CloudFront IP ranges. Note that these IP ranges change over time and will need to be updated periodically.
Cloudflare
We also use Cloudflare's global CDN network to serve static assets, adding a second layer of performance and redundancy on top of CloudFront. Please refer to this Cloudflare documentation page for an up-to-date list of Cloudflare's IP range. Note that these IP ranges change over time and will need to be updated periodically.
Built for Reliability
Production Application Server
Our primary application server hosts the ViewMedica content management system and is responsible for handling API requests.
Failover Application Server
To protect against downtime, we maintain a dedicated failover server. If the production server becomes unavailable, this server automatically takes over. It also hosts user uploaded videos for VMcast.
Streaming Socket Server
VMcast relies on a real-time connection maintained through our socket server. We use it to monitor the status of a stream and to send refresh or debug commands.