In this post I’m taking a closer look at the minimum cost required to get an application up and running, without compromising on security, and retaining some level of durability.
This example application runs a Node.JS web server, fronted by a load balancer and backed by a MongoDB replica set.
I have purposely selected the lowest cost compute instances available from each provider, which means as little compute power, RAM and storage as possible. It’s not a performance/cost comparison, since some providers offer lower minimum specifications than others. It’s also not something I would recommend for running your production environment on, but it gives us an idea of where the starting point is in terms of financial commitment, for getting an application online.
Although many providers could offer us virtual machines at an hourly or monthly rate, only five are listed below, because they are the most prominent and have the richest feature sets of all providers.
|Type||512MB RAM||512MB RAM||512MB RAM|
- The full name of the Joyent instance type is
- Google expects you to buy and upload your own SSL certificate, whereas AWS issues and manages one for you for free. The Vault instance on Joyent is intended to manage renewal of SSL certs from Letsencrypt (together with Consul).
- This comparison does not take into account the cost of storage and log management, or any other costs outside the hourly instance rate.
- All providers except AWS offer per-minute pricing.
- Cost estimate for Azure Load Balancer is based on their Application Gateway.
- Azure offers a range of managed application deployments, that are likely lower cost than rolling your own.