Go for backend. Yes it’s a bit more tedious. But in return you get deadass simple builds and pretty amazing performance. Also tbh it’s not that tedious to write SQL and tests. I’ve almost always run into issues with ORMs when things get complex.
Use Postgres and embedded db for cache. With SSD and Nvme you can leverage the embedded db for crazy performance. These days you can get a lot of storage space. Swap file and 5gb of space for the db as cache and you’re speeding. Save money and the network call, don’t need Redis.
React or svelte for UI. Don’t use next or any of that bloat. Use vite and lazy loading. If you need SSR don’t use SPA tech, maybe sveltekit would be good. I use sveltekit and react mostly.
For anything else like using sdk I use node if it’s not available for Go.
Use Postgres and embedded db for cache. With SSD and Nvme you can leverage the embedded db for crazy performance. These days you can get a lot of storage space. Swap file and 5gb of space for the db as cache and you’re speeding. Save money and the network call, don’t need Redis.
React or svelte for UI. Don’t use next or any of that bloat. Use vite and lazy loading. If you need SSR don’t use SPA tech, maybe sveltekit would be good. I use sveltekit and react mostly.
For anything else like using sdk I use node if it’s not available for Go.