4 ms·

Something I'd probably do is make a very basic app (e.g. 'todo' app) in each framework, deploy all 3 to heroku, and check out the 'metrics' tab. For a few hours

by nomilk 3y ago

Something I'd probably do is make a very basic app (e.g. 'todo' app) in each framework, deploy all 3 to heroku, and check out the 'metrics' tab. For a few hours' work, that should give a rough idea of CPU and memory, at least for a very small app. One other thing: > I want to spend as few dollars on hardware as possible. This is a perfectly sensible objective, but always keep in mind any trade offs between development time and server costs. Sometimes less efficient frameworks are faster to develop in, and it can be worth suffering a slightly greater server bill to get an MVP out quickly, especially if the server bill is small to begin with.

metaloha 3y ago
You could use https://codebase.show/projects/realworld https://codebase.show/projects/realworld for this instead of writing something new.
- nomilk 3y ago
  Wow, that's a very useful resource! It looks like the rails/django/phoenix apps were all updated in the past year, so could probably be deployed rather quickly.
- goatking 3y ago
  This is really cool, thanks!
goatking 3y ago
This is something I could definitely do. To be honest I am trying to save myself from the trouble. But if there are no existing, up to date comparisons, this will be my fallback plan. > This is a perfectly sensible objective, but always keep in mind any trade offs between development time and server costs. Sometimes less efficient frameworks are faster to develop in, and it can be worth suffering a slightly greater server bill to get an MVP out quickly, especially if the server bill is small to begin with. That totally makes sense, but I already researched a bunch of frameworks, and that's how I came up with these 3. I have hobby experience in all 3, and all 3 seems very efficient to work with.
- nomilk 3y ago
  One side-benefit: you might find you have a taste for certain frameworks and not for others. Being able to use a language/framework you enjoy more could make a bit difference in the long term. One other thing, tangentially related, is someone did build the same app in 10 different frameworks, which is a fun overview: https://www.youtube.com/watch?v=FQPlEnKav48 https://www.youtube.com/watch?v=FQPlEnKav48

by nomilk 3y ago

metaloha 3y ago

You could use https://codebase.show/projects/realworld https://codebase.show/projects/realworld for this instead of writing something new.

nomilk 3y ago
Wow, that's a very useful resource! It looks like the rails/django/phoenix apps were all updated in the past year, so could probably be deployed rather quickly.
goatking 3y ago
This is really cool, thanks!

goatking 3y ago

This is something I could definitely do. To be honest I am trying to save myself from the trouble. But if there are no existing, up to date comparisons, this will be my fallback plan. > This is a perfectly sensible objective, but always keep in mind any trade offs between development time and server costs. Sometimes less efficient frameworks are faster to develop in, and it can be worth suffering a slightly greater server bill to get an MVP out quickly, especially if the server bill is small to begin with. That totally makes sense, but I already researched a bunch of frameworks, and that's how I came up with these 3. I have hobby experience in all 3, and all 3 seems very efficient to work with.

nomilk 3y ago
One side-benefit: you might find you have a taste for certain frameworks and not for others. Being able to use a language/framework you enjoy more could make a bit difference in the long term. One other thing, tangentially related, is someone did build the same app in 10 different frameworks, which is a fun overview: https://www.youtube.com/watch?v=FQPlEnKav48 https://www.youtube.com/watch?v=FQPlEnKav48