The latest articles on Forem by Mahendra Kumar (@mahendra_kumar_6b3dceb27e). https://forem.com/mahendra_kumar_6b3dceb27e https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F3641794%2F0c8528d3-b1c5-483f-9128-eda871658c1a.jpg https://forem.com/mahendra_kumar_6b3dceb27e en Mahendra Kumar Tue, 02 Dec 2025 16:43:06 +0000 https://forem.com/mahendra_kumar_6b3dceb27e/how-do-you-architect-audit-logging-in-a-microservices-platform-2f4p https://forem.com/mahendra_kumar_6b3dceb27e/how-do-you-architect-audit-logging-in-a-microservices-platform-2f4p <p>I’m designing audit logging for a microservices platform running on Kubernetes with Go services communicating via REST and gRPC. I’m researching how teams typically implement audit logging across distributed systems.</p> <p>The requirements are simple:<br> capture who triggered an action, what changed, and the before/after state, along with timestamps and results.</p> <p>Areas I’m exploring:</p> <ol> <li>Capture point</li> </ol> <p>At the API Gateway?</p> <p>Inside each microservice?</p> <p>A hybrid?</p> <ol> <li>Delivery model</li> </ol> <p>Synchronous writes?</p> <p>Asynchronous pipelines (Kafka, NATS, SQS, etc.)?</p> <ol> <li>Aggregation</li> </ol> <p>Central audit logging service</p> <p>Shared database</p> <p>Event log / stream</p> <ol> <li>Failure strategies</li> </ol> <p>Fail the business operation?</p> <p>Buffer and retry?</p> <ol> <li>Performance</li> </ol> <p>Avoiding bottlenecks</p> <p>Batching, buffering, and backpressure patterns</p> <p>If you’ve built audit logging across multiple services, I’d appreciate insights on what worked well.</p> microservices audit logging go