[jively]

Go's GC is excellent btw, a massive benefit is also that you don't need the whole Java VM to run your app.

For pure performance, go write something in C or Rust. In fact for folks that are obsessed with performance rolling your own is the only option. Which is probably why the DO team went down this path.

For most use cases the benefit of working in your dev teams context / language of choice outweighs performance considerations.

And at Tyk the go plugins are native, you can slow down the GC activity to really boost performance if you have RAM to spare. Speed isn't an issue.

Ultimately it comes down to what you are trying to accomplish. What's best for your dev team? How can you innovate faster? How can you get this done cost effectively.

Performance comparisons are a dick measuring contest that are rarely relevant to the problem you are trying to solve.