Why do we still need to choose between the simplicity of Heroku or lower cost with AWS/GCP?
Why AWS/GCP is so complicated, and Heroku so simple but so expensive. Why we cannot have the best of the two world.
I'm working on an open source cli project to help developer to deploy application on google cloud in few commands a la "Heroku".
See this as your own DevOps, who will create/maintain/deploy your OWN infrastructure.
I'm looking for very early user who are interested by using this. I'm actively working on that and have a preview release with basic functionality like one command deployment, Https support etc
Thank you,
I'm a fan of Digital Ocean, which is arguably simpler than Heroku and absolutely cheaper than AWS.
I dont know well Digital Ocean. I will have a look, thank you
Really not sure if your tool would have much of a market.
Personally, App Engine is easier than Heroku for me, though pricing is an issue. When that becomes a problem I'll likely move to K8S since I'm already using Docker.
I just git push to GitHub and new releases are tested and deployed once I've setup CI (again, with Google's free CI service) and it's definitely amicable to more complex setups - I have staging/production environments and also can do canary deployments.
You are exactly the "target audience". You see, you still have to make a choice between easy to use vs cost. The goal of that tool is to make the cheaper solution as easy as heroku/app engine etc. I would like to exchange with you if you have time
I'm more than willing to have a chat about tech and stuff (hello@cameronbrown.co.uk) but my app's soon progressing past the phase I described. I need the complexity that GCP offers now, so like I said I'm not sure if I'm the target market.
This comment was deleted 7 years ago
My tool it's not a a platform as doku. My tool (no name for now) manage and abstract for you all the GCP infrastructure. It's more like you hire a devops on your team and he create a very simple cli that abstract all the infrastructure.