←back to thread

DigitalOcean App Platform

(pages.news.digitalocean.com)
646 points digianarchist | 5 comments | | HN request time: 0.431s | source
Show context
user5994461 ◴[] No.24700185[source]
I am so glad to see this. I was looking to deploy an app and the choice is either Heroku or manage your own server which I don't want to do.

Heroku gives instant deployment for the most common types of apps (python/java/ruby). It's PaaS done right, it's fantastic. You should really have a look if you're not aware of it, it's only $7 for a starter app.

Problem is, scaling up is about $50 per gigabyte of memory which makes it a dead end for anything non trivial. You're forced to go to digital ocean / Linode / OVH instead to have something affordable.

That leaves Digital Ocean as the only alternative (don't trust Linode) and it sucks because it only gives me a server to manage. I don't want to manage a server I want to run a (python) application. It's 2020 this sort of things should auto deploy from GitHub without bothering me to manage an operating system.

replies(19): >>24700693 #>>24700794 #>>24701039 #>>24702228 #>>24702633 #>>24702880 #>>24703398 #>>24703543 #>>24703620 #>>24704410 #>>24704873 #>>24705031 #>>24705668 #>>24706188 #>>24706382 #>>24707003 #>>24709134 #>>24716137 #>>24727185 #
emilsedgh ◴[] No.24703543[source]
This is spot on, except for one thing: Google Cloud Run.

It's the closest offering I've found to Heroku and am planning to migrate all our services to it due to significantly better pricing. Make sure you look into it.

replies(4): >>24704841 #>>24705131 #>>24705555 #>>24705865 #
1. blaisio ◴[] No.24704841[source]
Google Cloud Run doesn't provide nearly the same features as Heroku. For example, there is no easy way to manage secrets with Cloud Run. There is no way to run a worker process. Integration with other Google Cloud things like Cloud SQL is clunky. Cloud Run is okay to get started but almost all apps will need more.
replies(4): >>24705099 #>>24705264 #>>24705602 #>>24706725 #
2. fdweitendorf ◴[] No.24705099[source]
How would you like to see the integration with Cloud SQL improved?
3. jsmeaton ◴[] No.24705264[source]
We've been successfully using Cloud Tasks and firing payloads right back at our HTTP cloud run service to solve for the lack of background workers. We had to build a mini-framework around it, but it works surprisingly well.

https://cloud.google.com/tasks

4. manigandham ◴[] No.24705602[source]
It's built around everything being an HTTP request, and billing for the continuous seconds of time the app needs to run to service those calls.

You can run worker code by moving them into individual HTTP calls, triggered by whatever workflow you want. Cloud Tasks, PubSub, Cron, etc.

5. tomd ◴[] No.24706725[source]
> there is no easy way to manage secrets with Cloud Run

See https://cloud.google.com/secret-manager/

I recommend this community-maintained FAQ on Cloud Run:

https://github.com/ahmetb/cloud-run-faq