Basically I need a way to stand up an API with an /price/ endpoint and a /orders/ endpoint that run a bit of logic, put stuff in a database and trigger the payment processor flow. Easy-peasy except I have analysis paralysis over what to build it with and where to host it.
I’m comfortable with “classic” .net and dabbled in Node.js. I’d love to build it as an .Net Web API but the prospect of cloud hosting scares me (plus azure is freakin pricy).
With .NET Core and Postgres you can get something stood up within a few days and host on a cheap Linode, Digital Ocean or another provider's box for $6 a month or so. That should last you scalability wise until you have enough money from it to do something else and gives you type safe, performant code.
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...
Both will integrate easily with Postgres, and for flask, take a look at the peewee ORM.
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.
As for .NET hosting prices, I don't understand why you need complex hosting. A smallish instance paired with SQL Server RDS (both of which can be hosted on Linux or Windows) should suffice.
Keep in mind that both AWS and Azure offer a free tier when you're starting up:
"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.
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.
http://pojo.sodhanalibrary.com/ConvertJsonToSQL
and your selects, updates etc
If you are not familiar with ruby, go with a language you are familiar with. There is a clone in every major language. It’s just that RoR is the “original”.