Beating Go’s encoding/json with Schema-Guided ProtoJSON🔒 SSL Verified

Table of Contents

• ↓ Moving Schema Work Out of the Hot Path
• ↓ Benchmark Setup
• ↓ Marshaling Performance
• ↓ Unmarshaling Performance
• ↓ Conclusion
• ↓ What I Need Tested Next
• ↓ Top Alternatives to kmcd.dev

6-Month Traffic Trend Estimate

Official Contact & Profiles

Visual representation extracted from kmcd.dev

Content Snippets from kmcd.dev

"In my previous article, benchmark results showed that Go’s official protojson package was surprisingly slow. Execution profiles consistently highlighted the same bottlenecks: reflection, pointer chasing, and descriptor traversal accounted for much of the latency and memory allocation."

"ProtoJSON must preserve Protobuf semantics, including custom field names, enums, presence rules, and message structure, while producing standard JSON. The official implementation uses protoreflect to dynamically walk descriptors and inspect message structures on every call."

"That raised a concrete question: how much of this cost is inherent to JSON formatting, and how much comes from repeatedly resolving schema mappings at runtime?"

"To answer this, I built protojsonx. Moving schema resolution out of the hot path brings ProtoJSON marshaling performance close to binary protobuf and ahead of both Go’s standard encoding/json and encoding/json/v2 in these benchmarks."

Key Topics & Focus Areas for kmcd.dev:

Moving Schema Work Out of the Hot Path

Benchmark Setup

Marshaling Performance

Unmarshaling Performance

Conclusion

What I Need Tested Next