Premature optimization is the root of all evil. Implement algorithm the easiest way possible, profile your application, determine if this implementation a bottleneck or no. If yes, try other implementations, benchmark them and find the fastest one. Note that optimized go code can be faster than non-optimal code in rust, C, assembly or any other language.

Go is plenty fast for most things, and it is fairly simple. Rust is more interesting from a language geek perspective. I'd decide based on which of those appeals to you. I don't see good reason to combine them, though.

First write it in Go, which will likely be faster unless you are quite familiar with Rust. After that, you can port some/all of it to Rust if you wish.

Edit: by 'faster' above, I mean faster to write.

Go with what you want to do. If you prefer writing in one language over an other, do it.

The right answer is definitely PHP.

web development in Rust feels harder than say in Go or Python

Have you tried? There are some very nice web frameworks for Rust, like axum.

In my experience combining multiple languages usually creates more complexity and is slower than each of them individually because you need to convert the data structures of one language into those of another. Both of them are great languages and I've made web services in both so whatever one you pick will be a good choice.

As for which one to pick, although Rust is my favorite language, if you don't know it it'll take a while to learn. So for this project I'd say to go with Go because it's simpler and you really won't notice a performance difference unless you've got a huge amount of traffic.

If you have any more questions feel free to ask!

Bluesky Social, or at least their PDS (personal data server) uses Go and their Docker package includes Caddy, a webserver written in Go.

I don't know what you're doing, but I have difficulty accepting that Go cannot meet your performance requirements.

Given that it's a webserver and not a constantly running algorithm, definitely Go. It's plenty fast and is much more flexible.

My vote is Go. I've tried to make web services in both before and personally always found Go easier to use without noticeable performance trade-offs (even for real-time websocket apps). I feel you could always optimize more later if you start actually seeing performance issues.

Nim is cool

Yes go fast

Go with the Fiber framework will probably offer you enough performance https://www.techempower.com/benchmarks/#hw=ph&test=composite§ion=data-r22