Blog
OVERVIEW
A personal developer blog with deep dives into tech, tools, and web development. Covers full-stack development, performance optimization, and practical engineering insights.
TECH STACK
Next.jsMDX
KEY FEATURES
- MDX-powered posts for mixing rich prose with live code samples
- Deep dives into full-stack engineering, tooling, and performance optimization
- Built on Next.js for fast, statically-optimized page loads
- Focused on practical, hands-on engineering insights over generic tutorials
HOW IT WORKS
- 01The frontend posts a file to an upload endpoint, which tags admin uploads in S3 accordingly
- 02Files land in S3 under a unique short-ID prefix per upload
- 03A get-file endpoint serves files back via a presigned URL with a short expiry
- 04A Telegram bot integration handles bot-driven uploads and retrieval through a separate webhook
- 05An hourly scheduled job groups objects by short ID, checks their tags/metadata, and deletes non-admin uploads older than 24 hours
CHALLENGES
Serving uploaded files without a database meant finding a way to track which files were admin-preserved versus temporary. Solved by using S3 object tags and a metadata.json file per upload as a lightweight stand-in for a database, checked by an hourly cleanup job before deleting anything past a 24-hour retention window.
METRICS
4
Lambda functions
932
Handler LOC
17
Frontend source files
5,161
Frontend LOC
LINKSLive Demo ↗