Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Ask HN: Which stack will get my MVP API off the ground fastest?

news.ycombinator.com

Post reply on HN
Print view View original

21–30 of 31 posts

Re: Ask HN: Which stack will get my MVP API off the ground fastest?

#21

Post by bbayer »

Usually, I cannot finish what I have started because of debating over which shiny new framework/stack I need to use. I overoptimize things and always try to code for worst case. I cannot resist to think about hundreds of users, peak performance, hn traffic of death etc. Eventually it never finishes or I loose interest.

Best thing you can do is to make something that just works in fastest way possible. Anything that can print out text will work. You will always have a chance to make it better once it starts to get some traction.

Re: Ask HN: Which stack will get my MVP API off the ground fastest?

#22

Post by simonahgilbert »

Personally I would choose ASP.Net Core, hosted on a Microsoft Azure App Service with continuous integration from AppVeyor.

Benefits - Azure App Service free tier is awesome. AppVeyor have a 14 day trial that supports deployment directly from Git to Azure and .Net Core is awesome.

Here’s a blog I wrote recently which covers this exact implementation -

https://www.simongilbert.net/xunit-ci-azure-appveyor-aspdotn...

In terms of a database implementation, Azure’s NoSQL table storage is super cheap and awesome, as covered here -

https://www.simongilbert.net/dependency-injection-aspnet-mvc...

Re: Ask HN: Which stack will get my MVP API off the ground fastest?

#23

Post by fjp »

wilson_4 wrote: post #4

Can’t really go wrong with python + Django (or flask if you want to stay minimal). Sounds like you’ll need auth, so Django should support that out of the box. Both will integrate easily with Postgres, and for flask, take a look at the peewee ORM.

It won't be quite as fast to get off the ground as Django since it's not batteries included, but as an async Python fan I like to spin things up with aiohttp + Postgres like here: https://github.com/francojposa/aiohttp-postgres or here: https://github.com/francojposa/aiohttp-auth

The upside is that aiohttp's built in server can be put up in production with a lot more confidence than Django's built-in server, meaning one less layer to configure

Re: Ask HN: Which stack will get my MVP API off the ground fastest?

#26

Post by joshmn »

Whatever you know best.

"But deployment" deployment is cheap.

"But hosting" hardware is cheap.

"But time" time is _not_ cheap.

You don't need to screw around and learn another language/framework/ecosystem to get an MVP off the ground. You need to be able to hit the ground running and never let off the gas. This means you need to be able to change/adapt/feature what you need to. That takes brain cells. So does learning another language/framework/ecosystem. Don't make it harder than it needs to be.

Re: Ask HN: Which stack will get my MVP API off the ground fastest?

#27

Post by hanoz »

.NET Core Web API is absolutely perfect for this and the fact you already have some .NET experience makes it a no brainer in my opinion.

Just get started knocking out a prototype running locally and break the analysis paralysis, you'll have no end of hosting options to choose from later. You'll be amazed what a 5 dollar a month Ubuntu server from Digital Ocean or similar will handle running .NET Core. Azure is obviously an option too but don't rule out AWS.

Post reply on HN