It will still probably be goth.

Some good discussion there, would love to respond - but the invitation only model prevents me from doing so :(

I'd go with Rust, since I use Go daily. It all depends on your goals though.

Yes, it's quite verbose.

This is a question I'm yet to find an answer to, please ping me if you do.

It depends on your architecture and what you are going for. I mostly cache specific objects in dedicated k/v stores such as redis. If a full response can be cached for a long time doing so on the reverse proxy might be an easy way to go, but I usually keep things cached app side.

Yes, mostly redis. Sometimes postgres.

Welcome!

It's not really an ORM though is it?

They do come in handy but I feel like they tend to be a bit overused. I personally rarely use them.

I have been liking it for a while now too!

It's simple to read and understand.

care to share the blacklist?

I've been doing golang almost exclusively for quite a few years now, and the format still eludes me. I'm confident I'll never memorize it.

I've used both moq and mockery. I'm not too opposed to either, but if your interfaces are small then you don't really need them. Write an implementation for tests yourself. If you find your interfaces are too complex, perhaps a different design is an option?

Thank you for the valuable insights on this topic.