Earlier quoted context omitted.
"Roll your own" is hubris, unless you have the time, energy, inclination, theoretical knowledge, etc; I wouldn't try and solve solved problems if you can help it. But, host your own is definitely recommended IMO; a lot of the GDPR issues are resolved if you just host your own, because no data is shared to a 3rd party. Then you only need to worry about getting some approval and data retention. I'm sure data retention…
I would love to know other peoples opinion on this. But I am coming around to the idea that self hosted(atleast partially) might be cheaper and better if you are a single dev/a small team. The learning curve on the tools/hosting providers out there is has become very steep. Plus the costs are unclear with a lot of cloud providers and monthly subscription charges across the services you need can quickly stack up or th…
My go to 'cloud' path is just a digital ocean droplet, using docker containers to spool up whatever you need and connect it all on a docker network.
A single server (2-4 cores) running quite literally ANY modern backend framework (node, go, C#) should be able to handle _thousands_ of requests per second, I'm not sure where or when this idea has disappeared, it seems like everyone automatically assumes their small SaaS or webshop needs an autoscaling kubernetes 20 rack workhorse of a server. Not the case at all!!!!
Scale when you need to - if you're getting the kind of traffic where you need to, by then you won't need to worry about the added cost to do the actual scaling / upgrading.
Sorry for the winded / ranty answer, I've done this like 20+ times at this point and always had to battle against the "let's put it on AWS with kubectl and 2349023 redundant instances!", when in the long run it was never needed...