---
title: "Mukul Kumar (@pydevgo) | Hashnode"
description: "Engineering deep dives into system design, distributed systems, and the trade-offs behind real-world technology."
url: "https://hashnode.com/@pydevgo"
---

@pydevgo

# Mukul Kumar

@pydevgo · Joined October 2026

Engineering deep dives into system design, distributed systems, and the trade-offs behind real-world technology.

## Comments

[Spot on. The worst part of applying a lifecycle rule straight to raw event files is you also get hit with per-object transition requests ($0.01 to $0.05 per 1,000 objects) just to move tiny files into the wrong tier. Compacting into larger chunks or Parquet in Standard first fixes both the 128 KiB padding and the transition fee in one go.](https://hashnode.com/posts/s3-request-fees-and-128-kib-minimum-object-size/6aefa7bda2604b31b2b2efe5/comment/6aefe413a529a56101dd251a#reply-6af161103097fe7d1bafc90b)

Reply · Article · 1d ago · [When S3 Request Fees and the 128 KiB Floor Outgrow Your Storage Bill](https://hashnode.com/posts/s3-request-fees-and-128-kib-minimum-object-size/6aefa7bda2604b31b2b2efe5)

[Exactly! The interesting part is that coalescing and hot partition mitigation solve different problems. coalescing can reduce duplicate reads when requests overlap but it doesn't automatically redistribute traffic that's concentrated on one partition. Treating those as separate bottlenecks is important when reasoning about the architecture.](https://hashnode.com/posts/how-discord-s-message-storage-hit-a-scaling-wall/6ad2f7ca9fb50037f2bb17d7/comment/6ad30a0135d30f9a8aac9caf#reply-6ad319888b23e004ebcd7900)

Reply · Article · Oct 17 · [How Discord’s Message Storage Hit a Scaling Wall](https://hashnode.com/posts/how-discord-s-message-storage-hit-a-scaling-wall/6ad2f7ca9fb50037f2bb17d7)