TL;DR Same hexagon, same tools, same k6 scenario, two runtimes. Both servers handled the agent burst with zero failures and stayed far below the SLO. Go answered with a ~5× lower p95 (2.6 ms vs 13.8
Senior Backend Engineer · Java, Go & AI (MCP) · Building production-grade systems
Senior Software Engineer with 14+ years building backend systems in Java (8 to 25) and Spring Boot, now also working with Go. I write about MCP, AI agents, cloud-native architecture, observability and taking systems to production. Based in Colombia.
Markdown supported · ⌘↵ to post
No responses yet.