---
title: "Shantanu Badmanji (@ShantanuBadmanji) | Hashnode"
description: "Shantanu Badmanji (@ShantanuBadmanji) writes on Hashnode. Read their latest articles and follow their work."
url: "https://hashnode.com/@ShantanuBadmanji"
---

@ShantanuBadmanji

# Shantanu Badmanji

@ShantanuBadmanji · Joined December 2022

### [Aurora Optimization: How Storage Cleanup, Replica Removal, and Right-Sizing Cut RDS Costs by 84%](https://shantanubadmanji.hashnode.dev/aurora-rds-optimization-84-percent-cost-reduction?utm_source=hashnode&utm_medium=feed)

Reduce Aurora RDS costs by 84% through storage cleanup, replica removal, and instance right-sizing. Real metrics, tested approach, zero downtime.

10 min read · [shantanubadmanji.hashnode.dev](https://shantanubadmanji.hashnode.dev/aurora-rds-optimization-84-percent-cost-reduction?utm_source=hashnode&utm_medium=feed)

[Aug 13](https://hashnode.com/posts/aurora-rds-optimization-84-percent-cost-reduction/6a7e302acbfeeeacf87beab7)

### [From $4,200 to $800/month: Our AWS Cost Optimization Journey — 81% Cost Reduction With Zero Downtime](https://shantanubadmanji.hashnode.dev/from-4-200-to-800-month-our-aws-cost-optimization-journey-81-cost-reduction-with-zero-downtime?utm_source=hashnode&utm_medium=feed)

We were paying $4,200/month for infrastructure we didn't need to use. In three months of careful measurement and disciplined optimization, we cut that bill by 81% with zero downtime and zero incidents. This is how we did it—and the framework you can apply to your infrastructure.

11 min read · [shantanubadmanji.hashnode.dev](https://shantanubadmanji.hashnode.dev/from-4-200-to-800-month-our-aws-cost-optimization-journey-81-cost-reduction-with-zero-downtime?utm_source=hashnode&utm_medium=feed)

[Aug 4](https://hashnode.com/posts/from-4-200-to-800-month-our-aws-cost-optimization-journey-81-cost-reduction-with-zero-downtime/6a71df80020719f37fee5085)

### [Why I Used PostgreSQL Advisory Locks Instead of Redis](https://shantanubadmanji.hashnode.dev/why-i-used-postgresql-advisory-locks-instead-of-redis?utm_source=hashnode&utm_medium=feed)

When the "obvious" distributed locking answer is overkill — and your database is already equipped for the job.

11 min read · [shantanubadmanji.hashnode.dev](https://shantanubadmanji.hashnode.dev/why-i-used-postgresql-advisory-locks-instead-of-redis?utm_source=hashnode&utm_medium=feed)

[May 5](https://hashnode.com/posts/why-i-used-postgresql-advisory-locks-instead-of-redis/69f967ff46610fd6065afc43)

### [Why DATE(updated\_at) Broke Timezones and Killed PostgreSQL Index Performance](https://shantanubadmanji.hashnode.dev/why-date-updated-at-broke-timezones-and-killed-postgresql-index-performance?utm_source=hashnode&utm_medium=feed)

A real-world deep-dive into how a single SQL wrapper caused wrong dates for international users and made indexes completely useless — and the SARGable fix that resolved both.

7 min read · [shantanubadmanji.hashnode.dev](https://shantanubadmanji.hashnode.dev/why-date-updated-at-broke-timezones-and-killed-postgresql-index-performance?utm_source=hashnode&utm_medium=feed)

[Apr 20](https://hashnode.com/posts/why-date-updated-at-broke-timezones-and-killed-postgresql-index-performance/69e697e2c9501dd01036ca18)
