Slant community chat on Discourse| 5 Recommended Products | Recommendations | IPv6 | ISOs | Server locations |
|---|---|---|---|---|
| #1 DigitalOcean· · · | 3 | 0 | Yes | Ubuntu; Fedora; Debian; CentOS; CoreOS; FreeBSD | New York (3); Amsterdam (2); San Francisco (2); Singapore; London; Frankfurt; Toronto; Bangalore |
| #2 PythonAnywhere· · · | 3 | 0 | – | – | – |
| #3 Heroku· · · | 2 | 0 | – | – | – |
| #4 Cloudean Infotech· · · | 0 | 0 | Yes | Linux | Windows | FreeBSD | Hong Kong | Jakarta | Singapore | Sydney | Amsterdam | Dublin | Frankfurt | London | Vienna | Buffalo | Chicago | Dallas | Los Angeles | Toronto |
| #5 Google App Engine· · · | 0 | 0 | – | – | – |
Pro Pay-as-you-go with multiple payment options
Billing is done per hour. Each month has a 672 hour (28-day) billing cap with server runtime past that point being free of charge. DigitalOcean accepts payments via Visa, MasterCard, American Express, Discover, and PayPal.
Pro Flexible backup mechanism
Automatic backups can be made for 20% of the droplet price and an unlimited amount of snapshots at $0.02 per GB of storage can be made manually. EditComments References 1
Pro Beginner-friendly
DigitalOcean has a control panel that's intuitive and easy to use, new servers (Droplets) can be spun up in under a minute and they offer stock "apps" (LAMP, RoR, Wordpress) that can be deployed instantly. There's also an extensive documentation for people new to VPS.
Con Server charging
Digital Ocean charges the server 24/7 even if you turn it down. For example, on AWS you can shut down the server and it will not be charged.
Con No load balancing solution yet
Work on load balancing was announced January 11th, 2015.
Pro Excellent customer service
Really fast turnaround, friendly.
Pro Easy scaling
You pay for a number of "Workers" for your web app (to handle requests), or CPU seconds for code that you run outside a web app, and you can get more workers or CPU seconds by upgrading your plan any time.
Con Python-only on the server side
Obviously you can put JavaScript in your web pages and so on, but you can't use Rails or Node.
Pro Simple scaling
Heroku instances can easily be scaled up or down by increasing or decreasing the number of available dynos for that instance. This can be done through the CLI or through Heroku's web UI.
Pro Easy to start with
Getting started with Heroku is very easy. It's a very straightforward procedure and a beginner can set up their first app in two minutes. Often it's just a matter of a couple of git commands and it's all set up and running. The official Heroku docmentation also helps a lot.
Con Constrained by addons
If you want to fully customize your production environment, then Heroku can be seriously constraining. Installing libraries or services can not be done unless there is already a Heroku plugin for it.
Con Further deployments are slow
While starting with Heroku is fast and easy, and the first few deployments are actually very fast, larger applications tend to have slower deployments. It takes some time for the dynos to restart and while they are restarting the application is completely offline. Which means that you can lose pre...
Pro Increases application speed considerably
Google App Engine integrates with Google's CDN out of the box and it distributes your application's assets through that, increasing loading speed considerably.
Pro Easy to use
Google App Engine is very easy to use. All you need to do is install the SDK (which in itself is easy as well, and the documentation is very heplful) and run the command needed depending on the type of project to deploy it. For example, to deploy a golang application, you run golang deploy inside...
Con No SQL database available
Google App Engine uses Google's NoSQL cloud database. There's no option to use a SQL database with your application.
Comments
Welcome to the Slant Community
Stop spending hours researching
Slant is written by a community helping you be informed. Let us know what you’re passionate about to get an awesome personalized feed.