Category Archives: Uncategorized

Key Takeaways You have the benchmark results now. Article 9 reported results for a compact Go net/http service and a Helidon SE Java service running on two measured Oracle JDK runtime shapes. So the question becomes the one teams actually … Continue reading →

Key Takeaways A service tier in front of Oracle AI Database can sit directly in the hot path. It might validate requests before calling vector search, enrich context before a model call, serve retrieval results to an AI application, or … Continue reading →

Key Takeaways If you have ever read a benchmark post and thought, the chart is clean, but I still do not trust it, this is probably the missing layer. Most benchmark arguments sound like methodology arguments, but a lot of … Continue reading →

Key Takeaways Service-runtime choices matter when an HTTP endpoint sits in front of a model call, retrieval step, vector search request, enrichment pipeline, or another application workload. Teams naturally ask whether Go, Java, framework choice, JDK choice, warmup, or runtime … Continue reading →

Key Takeaways If you have ever read a benchmark post and thought, I still can’t tell whether this is a runtime result or a harness result, this article is for you. That confusion usually starts long before the chart. A … Continue reading →

Key Takeaways If you want a skeptical reader to trust the later benchmark charts, you have to earn that trust before the first results article. That starts with the client. A load generator can flatten throughput for the wrong reason, … Continue reading →

Key Takeaways Before we believe a future Go-versus-Java chart, we need to know exactly what the Go service is doing. Not “it is a small Go program.” Not “it uses the standard library.” Not “it looks equivalent.” We need to … Continue reading →

Key Takeaways You can make “Java” mean almost anything in a benchmark. It might mean a plain JDK HTTP server, Spring Boot, Quarkus, Micronaut, Vert.x, Netty, or Helidon. It might mean platform threads, virtual threads, a reactive handler model, a … Continue reading →

Recently, I was lucky enough to be invited to give a short presentation on blended teams, and I wanted to share some of my thoughts with you, dear reader! What is a “blended team”? I am defining it as a … Continue reading →

Key Takeaways You can make two services look almost identical and still measure different work. One implementation accepts an unknown JSON field and ignores it. The other rejects the request. One silently clamps a payload size that is too large. … Continue reading →