Worst possible advice, if you pardon my borderline rudeness. That's what most programmers do, following famous saying that for someone with a hammer every problem looks like a nail.
Ops problem is more architecture and scale, IMO, as opposed to what coding language or JS framework.
I’d start with Postgres on the back end and then work with scale as needed over time. The service can be written in pretty much any language like Kotlin, Java, Python, or even Rust if you want. Personally I’ve never used Swift server side.
IMO the worse option is to try to over optimize and use some shiny technology that you don’t understand how to use.
I’d start with Postgres on the back end and then work with scale as needed over time. The service can be written in pretty much any language like Kotlin, Java, Python, or even Rust if you want. Personally I’ve never used Swift server side.
IMO the worse option is to try to over optimize and use some shiny technology that you don’t understand how to use.