Work

Open SourceGitHub, npm, PyPI, and public packages.

Depth

JourneyCareer timeline, roles, and education.AchievementsScholarships, rankings, and milestones.

Writing

PublicationsResearch-facing work and technical reports.ProfilesAll key public links in one place.

Project

Real-Time Notification Migration

Migrated notification workflows to SQS, Lambda, and Firebase while improving backend reliability and pushing a large JavaScript codebase toward TypeScript and server-compatible React patterns.

180K lines affected
Migration
Realtime + scalable
Delivery
SQS / Lambda / Firebase
Stack

Outcome narrative

What this project optimizes

Migrated notification workflows to SQS, Lambda, and Firebase while improving backend reliability and pushing a large JavaScript codebase toward TypeScript and server-compatible React patterns.

Technology footprint

Tooling and implementation stack

Selected technologies supporting reliability, maintainability, and delivery speed.

  • SQS
  • AWS Lambda
  • Firebase
  • TypeScript
  • React
  • Next.js

Execution model

How this delivery is structured

The same framework can be adapted for adjacent products and modernization initiatives.

Discovery and architecture

Define constraints, expected outcomes, and non-functional requirements.

Build and validate

Deliver iterative milestones with quality checks and feedback loops.

Scale and optimize

Tune performance, harden reliability, and operationalize observability.

Next Steps

Explore more work

AWS Serverless Cost Optimization: A Real Audit Walkthrough

Serverless teams overspend by 30-50%. Here's how to audit your Lambda, API Gateway, and NAT costs, find the leaks, and cut your bill.

Navigate

How I Handle Environment Variables and Secrets on a Self-Hosted Server

NEXT_PUBLIC_ variables get inlined into the JavaScript bundle at next build, not read at runtime — which means the moment you rebuild a Next.js image per environment instead of injecting config at runtime, you've built something that can leak.

Navigate

Why Next.js Feels Slow on a VPS — and the Six Things That Fix It

The app that felt instant on Vercel goes home to a cheap VPS and forgets how to load fast. The framework didn't change. Six specific things underneath it did, and none of them are next/image.

Navigate

Why I Rebuilt This Site on Next.js 16 and Payload CMS

After five years on a hybrid stack, I rebuilt farasat.me with Next.js 16 and Payload CMS 3. Here's why the modern approach to full-stack typesafety and content management actually matters.

Navigate

Where to go next

More case studies

The rest of the record