English lad currently a C#/Java/VueJs/JavaScript/TypeScript engineer.
Extra dribbling can be found at https://codeheir.com
Portfolio found at https://lukegarrigan.com
Sure but that's $3 a month you're paying flat, whereas serverless you pay for what you use and - as you mentioned - it has the benefit of scaling meaning you don't need to worry about purchasing more servers per continent. My suggestion is by no means a must, but for the majority of use-cases, for ease and simplicity I'd go that direction.
Just a heads up, a lot of serverless platforms still tie your functions to a specific region. You will have to choose which regions to deploy to. Also if you deploy to multiple regions your database needs to be available in those regions as well or you will actually increase your latency. You can't easily do this for most databases. Scaling to multiple regions is not easy for most apis. You really need to plan ahead for this.
English lad currently a C#/Java/VueJs/JavaScript/TypeScript engineer.
Extra dribbling can be found at https://codeheir.com
Portfolio found at https://lukegarrigan.com
Sure but that's $3 a month you're paying flat, whereas serverless you pay for what you use and - as you mentioned - it has the benefit of scaling meaning you don't need to worry about purchasing more servers per continent. My suggestion is by no means a must, but for the majority of use-cases, for ease and simplicity I'd go that direction.
Just a heads up, a lot of serverless platforms still tie your functions to a specific region. You will have to choose which regions to deploy to. Also if you deploy to multiple regions your database needs to be available in those regions as well or you will actually increase your latency. You can't easily do this for most databases. Scaling to multiple regions is not easy for most apis. You really need to plan ahead for this.
Very true Andrew, a good problem to have though!