Ashish Namdeo

Event-driven e-commerce platform: gateway, JWT auth, OpenFeign, Kafka, Stripe, Docker, AWS.

Problem

Checkout, identity, payments, notifications, and analytics cannot share one release cycle or one failure domain.

Solution

Independent Spring Boot services behind an API gateway. Synchronous OpenFeign where a consistent read is required; Kafka events for everything that can happen after an order is accepted.

Architecture

• API Gateway routes to Auth, User, and Order.
• Order publishes OrderCreated to Kafka.
• Payment, Notification, and Analytics consume independently.

Key decisions

• Keep payment off the checkout HTTP thread.
• Separate auth credentials from user profile data.
• Containerize first; treat AWS as the cloud-ready deployment target.

Production-style authentication and authorization service with JWT, refresh rotation, RBAC, and Redis revocation.

Problem

Most product backends rebuild the same security foundation before they can ship domain features.

Solution

A Spring Boot starter covering registration, login, JWT access tokens, refresh-token rotation, RBAC, Redis blacklist, rate limiting, and OpenAPI docs.

Architecture

• Layered Spring Boot service: controller, security, persistence, exception handling.
• Stateless JWT access tokens with rotating refresh tokens.
• Redis-backed token blacklist for logout and revocation.

Key decisions

• BCrypt password hashing and method-level security annotations.
• Rate limiting and secure headers against brute-force and common web attacks.
• Environment-based config and Swagger so the service is actually reusable.

Real-time AI pitch-coaching web app with sub-second streaming feedback and session analytics.

Problem

Founders get delayed, unstructured feedback on pacing, filler words, and delivery.

Solution

Full-stack investor-simulation app streaming speech-to-text over WebSockets, with GPT-4o structured feedback and exportable session reports.

Architecture

• WebSocket streaming path for low-latency transcript and coaching events.
• Session analytics dashboard with exportable reports.
• Live demo deployment with documented design tradeoffs.

Key decisions

• Stream partial results instead of waiting for a full recording.
• Structure model output so pacing and filler-word metrics are comparable across sessions.

Autonomous code-repair agent that plans a fix, runs tests in Docker, and iterates until tests pass or the budget is exhausted.

Problem

Untrusted LLM-generated patches are dangerous to execute on a host, and one-shot patches usually fail the suite.

Solution

Ingest a GitHub issue, plan a fix, write code, run tests in an isolated Docker environment, read results, and iterate with a hard attempt cap.

Architecture

• Agent loop: plan → patch → test → observe → retry or exit.
• Sandboxed Docker execution with resource limits and timeouts.
• Evaluation suite of 20+ cases with run logging for steps, tool calls, and token cost.

Key decisions

• Never execute generated code on the host.
• Cap retries so a failing agent cannot loop indefinitely.
• Log every step for observability, not just the final patch.

Ride-sharing platform connecting riders and drivers — Java 21, Spring Boot 3, React, MySQL.

Problem

Daily commuting leaves unused seats and uncoordinated demand.

Solution

Full-stack matching product: register, publish or search rides, request bookings, accept/reject, and rate.

Architecture

• Spring Boot 3 backend with Spring Security JWT, JPA, and Flyway.
• React + TypeScript client for rider and driver workflows.
• MySQL 8 as the system of record.

Key decisions

• JWT + layered architecture so auth is not mixed into ride matching.
• Flyway migrations to keep schema changes explicit.
• OpenAPI/Swagger for a contract the frontend can actually consume.

Java 17 deep packet inspection engine: PCAP analysis, protocol classification, blocking rules, CLI and web UI.

Problem

Packet captures are opaque without protocol tracing tools or native libraries.

Solution

Pure-Java inspection pipeline that classifies HTTP, DNS, and TLS SNI, applies block rules, and exposes both CLI and a REST/web workflow.

Architecture

• Multi-module Maven: packet models/decoders, PCAP IO, CLI, REST API with web UI.
• Classification pipeline for TLS SNI, HTTP Host, DNS, flows, and detected domains.
• Blocking rules for apps, source IPs, and domains.

Key decisions

• Implemented in Java to keep local setup portable.
• Same core engine serves automation (CLI) and analysis (web upload).

Java journal for habits, tasks, and growth tracking with secure persistence.

Problem

Personal notes and habits need a structured backend, not a throwaway CRUD demo.

Solution

Spring-based journal API with authentication and Redis-backed support for session/token concerns.

Architecture

• Java service with Spring Security at the edge.
• Redis used alongside secure persistence.

Key decisions

• Treat journal entries as authenticated user data, not an open notebook.

Flutter habit tracker with Pomodoro focus, AR rewards, and a productivity assistant. SS12 hackathon winner at CSUN.

Problem

Habit apps lose ADHD users when the interface adds friction instead of reducing it.

Solution

Mobile-first productivity app with task simplification, Pomodoro, AR character rewards, and guided prompts.

Architecture

• Flutter client for cross-platform delivery.
• Pomodoro timer, AR rewards, progress tracking, and in-app guidance.

Key decisions

• Reward loops and visual scheduling over dense task lists.
• Shipped as a hackathon product with frontend and Spring Boot backend contributions.

Warm orange-accented VS Code theme — high contrast, built for long coding sessions.

Problem

Default editor themes are either too dim or too noisy for daily use.

Solution

A VS Code theme with a copper-warm accent and balanced contrast, published on the Marketplace.

Architecture

• VS Code theme extension packaged for Marketplace distribution.

Key decisions

• Optimize for contrast and warmth rather than trend palettes.