01
Think
Understand the problem, the constraints, and what happens when it fails.
Initializing
Java backend developer · Azamgarh, India
From the first endpoint to a containerized deploy, and everything that breaks in between.
Available for backend roles
The journey
0
components
Endpoint
One controller, one response.
Every system starts as a single endpoint. Each layer here is one I have built into a published project, or am building now.
How the work actually happens
01
Understand the problem, the constraints, and what happens when it fails.
02
Shape the system: entities, API contracts, data access, and where to cache.
03
Turn the design into software: Spring Boot services, secured APIs, data layers, and tests.
04
Production is the real test: green tests, a Docker image, a deploy, and an eye on the logs.
05
Software is never finished. The architecture has to grow with the product.
Stack
The tools behind the systems, grouped the way they show up in a real backend.
01 / 06
Case studies
Taking harmful media down fast, without ever keeping a copy.
A trust and safety platform that detects deepfakes and explicit images, routes them for human review, and tracks takedown deadlines. Raw media is never stored.
Built with
The challenge
Harmful media needs a fast, auditable path from detection to takedown, without the platform becoming a store of the very content it removes.
What I did
The result
Turning a website crawl into a ranked list of what to fix.
A full-stack website SEO audit platform. Connect a site, run a crawl, review ranked issues, and download a report.
Built with
The challenge
An audit is only useful if it is fast to run and clear about priority. Raw crawl data is noise until it becomes a ranked list of issues.
What I did
The result
A task manager built like a production service.
A task manager with registration, JWT auth, role-based access, search, filters, and pagination. Packaged with Docker and Nginx.
The challenge
Most to-do apps stop at CRUD. The goal was the parts real products need: identity, permissions, and queries that stay fast as data grows.
What I did
The result
Making Redis behavior observable instead of magical.
A Redis internals lab: data structures, streams, locks, rate limits, persistence, and cluster topologies, exercised through Spring Boot.
The challenge
Redis is easy to add and hard to reason about. Locks, persistence modes, and clustering only make sense once you watch them fail.
What I did
The result
Putting soil data and plant health in a farmer's hands.
An AI-assisted farm monitoring platform with soil analytics, plant image review, weather context, and a live web app.
The challenge
Farm data is scattered across sensors, weather, and what the farmer sees in the field. It needs to land in one place that is simple to read.
What I did
The result
Earlier studies
A minimal Spring Boot service that sends email through Resend.
JavaA Java OOP console project for teachers, students, and grades.
JavaA library interface built with HTML, CSS, and JavaScript.
WebA C console program for adding, issuing, and returning books.
CAn AI-powered career assistant for career exploration and job-search activities.
AIRight now
Labs, experiments, and LeetCode. A different playground for the same backend mindset.
Currently exploring: Spring AI, RAG, embeddings, MCP, system design, Redis internals, and LLM apps.
Contact