A good stack IMO has the fewest moving parts possible. JAMstack for the frontend served via cdn Terse STATELESS apis on the backend likely in Go on a managed

A good stack IMO has the fewest moving parts possible. JAMstack for the frontend served via cdn Terse STATELESS apis on the backend likely in Go on a managed k8s cluster DB choice depends on requirements for the app IMO if its data that needs to consistently persist put it in a relational DB like maria or postgres. If the data is short lived let it hit mongo or otherwise. To be completely honest though with current tooling you could do an e2ee local sqlite database and store it in an S3 bucket using a guid per user.