[lgkk]

I’d use whatever scales best for the least cost.

Go backend. Single binary. Big performance. I’d use Go for as many things as possible until I actually had a need for distinct technologies (queues, redis, etc.). Throw embedded db into the mix and you shouldn’t have any problems for a long time.

React UI on cloudflare pages. Free. Easy.

Postgres. Single node goes far. Great plug n play extensions. Same as with Go I can push this pretty far until there is some serious requirement to do something else.

Deploy on either cheap bare metal or an affordable provider like DO.

[cookiengineer]

Do you by any chance know whether there's something like a go library or converter/transpiler that allows you to reuse the structs from a backend on the client side?

Currently I always have a little redundancy in my projects when it comes to the JS HTTP client that calls the golang backend's API and I want to avoid that.

[lgkk]

Not that I am aware of. If there is one I’d try it out.

I usually just make the types by hand on TS client.

Maybe gpt :p