Developed a full‑stack marketplace and messaging platform connecting buyers and farmers with real‑time chat and a polished, mobile‑first UI inspired by Telegram. Architected the system to scale into a full commerce workflow including Stripe subscriptions, orders, delivery, and notifications, with production‑ready backend patterns and cloud deployment.
What I Built
Authentication & role-based access (buyer/farmer/admin flows), profile management, and media handling
Realtime messaging (Telegram-like UX):
Typing indicators, read receipts, replies, message deletion flows
Emoji reactions with smooth UI and cross-user synchronization
Context menu reaction bar + action sheet, optimized for desktop and mobile
Presence system:
Online/last-seen indicators with consistent UX rules
WebSocket-driven updates for chat header and thread list
Scalable backend foundation (NestJS):
Modular services, DTO validation, guards/middleware, clean separation of concerns
Webhook-ready endpoints for payments/notifications and event-driven workflows
Cloud / Infrastructure (AWS)
Compute & orchestration: AWS EC2, ECS (containerized deployment approach)
Storage: AWS S3 for user/media assets (profile/farm images, attachments-ready)
Database: AWS RDS for relational data (users, threads, orders, subscriptions)
Caching / realtime support: Redis (sessions, rate limiting, pub/sub, presence/notification fanout patterns)
Tech Stack
Frontend: Next.js, React, TypeScript, Tailwind CSS
Backend: NestJS (Node.js), REST APIs, WebSockets
Data: PostgreSQL/MySQL on RDS, Redis
Storage: S3
Deployment: Docker + ECS/EC2
Payments (planned/integration-ready): Stripe subscriptions + webhooks
Realtime Messaging: Twilio Conversations (chat transport) + websocket presence layer
My Responsibilities
End‑to‑end implementation (frontend UI/UX + backend APIs + realtime behavior)
Designing data models and message metadata for cross-client sync (reactions/presence)
Production-oriented architecture: caching strategy, background/webhook flows, deployment setup…Developed a full‑stack marketplace and messaging platform connecting buyers and farmers with real‑time chat and a polished, mobile‑first UI inspired by Telegram. Architected the system to scale into a full commerce workflow including Stripe subscriptions, orders, delivery, and notifications, with production‑ready backend patterns and cloud deployment.
What I Built
Authentication & role-based access (buyer/farmer/admin flows), profile management, and media handling
Realtime messaging (Telegram-like UX):
Typing indicators, read receipts, replies, message deletion flows
Emoji reactions with smooth UI and cross-user synchronization
Context menu reaction bar + action sheet, optimized for desktop and mobile
Presence system:
Online/last-seen indicators with consistent UX rules
WebSocket-driven updates for chat header and thread list
Scalable backend foundation (NestJS):
Modular services, DTO validation, guards/middleware, clean separation of concerns
Webhook-ready endpoints for payments/notifications and event-driven workflows
Cloud / Infrastructure (AWS)
Compute & orchestration: AWS EC2, ECS (containerized deployment approach)
Storage: AWS S3 for user/media assets (profile/farm images, attachments-ready)
Database: AWS RDS for relational data (users, threads, orders, subscriptions)
Caching / realtime support: Redis (sessions, rate limiting, pub/sub, presence/notification fanout patterns)
Tech Stack
Frontend: Next.js, React, TypeScript, Tailwind CSS
Backend: NestJS (Node.js), REST APIs, WebSockets
Data: PostgreSQL/MySQL on RDS, Redis
Storage: S3
Deployment: Docker + ECS/EC2
Payments (planned/integration-ready): Stripe subscriptions + webhooks
Realtime Messaging: Twilio Conversations (chat transport) + websocket presence layer
My Responsibilities
End‑to‑end implementation (frontend UI/UX + backend APIs + realtime behavior)
Designing data models and message metadata for cross-client sync (reactions/presence)
Production-oriented architecture: caching strategy, background/webhook flows, deployment setupWW…