Typed languages are great for systems development, and I think, not so good for writing web applications.
I also think, Ruby, Python, JS have dominated web dev world largely cause they don't come in the way of the developer having to constantly convert HTML (untyped) and JS (untyped)into types for the backend programming language.
Remember how ActiveRecord (not sure about SQLAlchemy) simply took away the pain of managing types? You didn't have to explicitly parse or cast "0.001" into 0.01.
Whatever you do, don't even think that GraphQL will solve your problems. You were on the right track staying away from it till now.
I can't also advise enough to stay away from a typed language (Go in this case) serving data in a different typed language (gql). You will eventually be pulling your hair out jumping through hoops matching types.
After my last web project that require gql and go, I did some digging around, thinking, there has to be a better alternative to this. I have worked with jQuery, React, GraphQL.
I have seen too many front end developers write queries equivalent to "select * from users, t1, t2, ... tn, left outer join on users.id = t1.user_id... etc etc etc".
I think that is just bullshit.
I prefer to tell the frontend people - these are the endpoints that backend team provides, go live with it. If you really have issues, talk to them, and they might just add a new endpoint for you.
If you let frontend developers dictate backend queries, all you will get is a big master cluster fuck. I am talking average joe developers that we usually find to work on startups.
k8s and even docker are trying to solve a problem not many people will ever face. However, being the sexy new things loads of people get sucked into integrating it into their stack from the word go.
Being reluctant to adopt new technology unless you really really need might be a more sensible thing to do.
My personal mantra of being a late adopter when it comes to cloud deployment tools has some benefits has served me well. I am even reluctant to integrate docker in my work flow. Git pull, build and deploy bash scripts are serving me well enough for now. Thank you very much.
I have been remoting for over ten years now. The only rule I have now is to work with remote first teams. If there's an office where a big clique meets, you'll eventually feel left out.
I have done close to a decade of work in js, with jQuery in 2008, all the way to react and webpacker madness.
I hope someone builds a wasm based front end framework. I did a quick search and MSFT seem to be on it with their Blazor framework. Unfortunately, I am not in a hurry to go learn ASP.NET or C# anytime soon.
Maybe we need a frontend framework in Golang that compiles to WebAssembly. I am rooting for Golang here, cause after a decade in Ruby/Python/JS, I am really enjoying going back to typed languages.
But even a python/ruby to wasm web frontend framework will be awesome. Anything that keeps me away from node hell.
There's so much data in this universe, people don't know what to do with it. When people don't know what to do, an industry grows to let them "feel" they are doing something useful.