Finally ready to deploy! But... where?
After 4 long months, my MVP is finished, which service do you recommend to use to deploy my app?
My stack is:
Nodejs
Express
MongoDb (Mlab)
Jade
Btw.. Now.Zeit did not work for me... I'm trying now ElasticBeanstalk, but wondering what other options you would recommend :)
Thanks!
Make your life easy by using render.com @csallen uses it for Indie Hackers and @lynnetye uses it for KeyValues
Thanks for the shoutout @emekaonu! @ThisisGiorgio Render is indeed the easiest way for you to deploy your stack. Try it out!
This is the first time I've really noticed Render!
Is it possible to run a web server and a database on the same container with Render? Also is it possible to set up with Gitlab CI/CD?
You can create a Dockerfile that does both, but I wouldn't recommend it. In general, Docker is best used with a single process per container.
GitLab support is on our TODO list!
I don't mind separating the db once things are a certain size, but given that I'm mostly writing Elixir back-end, one process per container sounds a bit crazy, at least to my ears.
IMO, it would make more sense not have any containers at all than to be firing up another copy of the BEAM for each process.
Sure. You can certainly run multiple Elixir processes per container on Render; we leave this completely up to you if you're using Docker containers. If you're using our native environments, we're going to allow multiple instances of the app in the next twoish weeks, with EPMD service-discovery built in. Stay tuned!
I didn't mean multiple Elixir processes since they're just lightweight threads as opposed to what most people mean by processes. What I meant is that I'd like the BEAM running on a multi-core machine having access to multiple machine processes rather than firing up many BEAMs that can use one core and one process each. Basically, I'm looking for something monolith-friendly. This is really useful info, though.
Even with the limitations I mistakenly thought were in place, if it's a really easy way for people to get started, I should probably make some screencasts to share how to use your service once I have a good handle on that myself 😂
Got it. We are monolith friendly with multi-CPU plans all the way up to 64 CPUs 🔥
This comment was deleted 7 years ago
The primary mechanism is containerization of apps and smarter scheduling of resources. Of course we also have a CDN (which you're reading this on!).
Start with a something that costs just a few bucks a month and then scale up once you get some traction. We at SendingBee have been pretty happy with a dedicated server [1] from Hetzner but to get started you might go with their Cloud offerings [2].
If you want something more managed, have a look at Heroku [3]. It can get pretty expensive once you add more "dynos" but last time I used it they offered a free plan to get started with some limitations.
[1] https://www.hetzner.com/dedicated-rootserver/matrix-ex
[2] https://www.hetzner.com/cloud
[3] https://www.heroku.com
I'd go against the grain. Don't deploy somewhere where you'd inevitably end up in a vendor lock in. Go for something that you manage yourself. DigitalOcean, Hetzner, Scaleway, Vultr are all good options. On top, they are significantly cheaper than PaaS solutions.
I have almost the same stack and I've chosen Heroku and it works like a charm.
MLab + Heroku = sure fire win! Lightweight, cheap, easy to use C/D. AWS is overkill for new products.
HEROKU!
Sorry for shouting. But just go for Heroku. Huge fan here.
I'm a huge fan of Heroku as well. I don't feel very stupid there. and looks like for your stack it works fine
This ^^
I'm currently working on https://stackmate.io/ that aims to provide effortless cloud deployments for web applications. I would be more than happy to have a chat with you (or any of the commenters) where share your pain points, it would help improve my offering so much. Thanks
Thanks for all the answers i went with render.com, its awesome!
I really wouldn't go the Elastic Beanstalk route. Keep it simple. I've personally bailed out far to many projects that started with an "AWS architecture astronaut" who set up a lot of infrastructure that slowed them down or even cost them ridiculous amounts of money as they scaled. If you've got Amazon credits, that's fine, but I'd use their Lightsail service or try to stick to something simple like just putting everything on EC2 and S3 rather than using five or more services.
I'm a big fan of Digital Ocean and it will get you more for your money than an equivalently labeled EC2 instance.
As long as your app is reasonably profitable compared to the number of users you expect, Heroku can be fine, too.
If you want a medium amount of hand-holding and you're on Rails, then Hatchbox.io is a great choice, as well.
I tried EB and found Heroku cheaper and easier to work with.
This comment was deleted 7 years ago