MINOR: Add technical blog post on gateway-to-Kafka event delivery

[Yilialinn]

Summary

This PR proposes an original technical blog post: Designing Reliable Gateway-to-Kafka Event Delivery: Batching, Acknowledgments, and Backpressure.

The article explains how an API gateway should be treated as a Kafka producer with explicit delivery boundaries. Apache APISIX kafka-logger is the concrete open-source implementation used throughout the article.

Value to Kafka readers

The post connects gateway operations to Kafka concepts that practitioners need to design together:

• event decoupling, retention, replay, partitions, and consumer groups;
• producer batching and in-memory buffering;
• acks, ISR, and min.insync.replicas;
• ambiguous retries, partition-scoped ordering, and consumer idempotence;
• observability and a proposed failure-validation ledger.

Contribution context

I am contributing this article as Yilia Lin, an Apache APISIX Committer. The article is original and non-commercial. It contains no sales call to action, competitor comparison, SEO request, or unverified performance claim.

The APISIX configuration fields and Kafka acknowledgement/topic semantics have been checked against the current official documentation. The copyable APISIX JSON has also been syntax-checked.

Validation scope

This contribution does not claim exactly-once or lossless end-to-end delivery. It does not report throughput, latency, or fault-test results. The failure scenarios in the article are a proposed production-validation method and have not been executed as part of this contribution.

The article has been placed under content/en/blog/ and tested with the website build from the markdown branch.

Editorial fit

The current repository guide describes content/en/blog/ and uses release announcements as the most common example. Could maintainers please confirm whether a non-release, implementation-based technical article is appropriate for the Kafka Blog, and whether this path/category is preferred? I am happy to adjust the location, scope, or framing based on community feedback.