Selected work

Portfolio

A focused set of backend-heavy and full-stack projects from my GitHub profile: microservices, semantic search, e-commerce systems, authenticated apps, and product UI work.

Backend architecture and API contracts
Database modeling and search workflows
React product flows connected to real APIs

01

Marketplace Microservices

Production-style e-commerce backend with an API gateway, separate domain services, authentication, validation, logging, and Dockerized local orchestration.

Problem

Marketplace backends need clear service boundaries without becoming hard to run, validate, or debug during development.

Solution

Split user, product, and order responsibilities into focused services behind an API gateway, with shared validation, centralized errors, JWT auth, logging, pnpm workspaces, and Docker Compose.

Review focus

Start here for backend architecture, API design, service boundaries, validation, auth, Docker, and maintainable project structure.

Tech stack

TypeScriptNode.jsExpressMongoDBMongooseZodJWTDockerpnpm

02

NeuroIndex API

Semantic document indexing and search API with ingestion, chunking, OCR, embeddings, async processing, PostgreSQL, and pgvector similarity search.

Problem

Document search becomes brittle when systems only match keywords and cannot process mixed content reliably.

Solution

Built a NestJS API that ingests documents, extracts and chunks content, creates embeddings, queues background work, and stores vectors in PostgreSQL for similarity search.

Review focus

Review this for AI-assisted backend engineering, vector search, async queues, OCR ingestion, and PostgreSQL/pgvector modeling.

Tech stack

NestJSTypeScriptPostgreSQLpgvectorPrismaBullMQRedisOllamaOCR

03

sinaEcom Server

E-commerce backend foundation with routes, controllers, middleware, models, uploads, and utility layers.

Problem

A commerce product needs a backend that can keep business workflows organized as product, order, user, and upload concerns grow.

Solution

Structured the server around conventional Express layers so routes stay readable, middleware remains reusable, and MongoDB models hold the data boundaries.

Review focus

Useful for reviewing Express API structure, middleware organization, MongoDB models, file upload flow, and utility boundaries.

Tech stack

Node.jsExpressMongoDBJavaScriptMulterJWT

04

sinaEcom Client

Customer-facing e-commerce UI connected to backend product and shopping workflows.

Problem

Storefront users need a clear path from browsing products to interacting with core shopping features.

Solution

Built a React client that consumes backend APIs and organizes product, cart, and customer-facing commerce flows into reusable UI sections.

Review focus

Review this with the server project to see how frontend workflows connect to API-backed commerce features.

Tech stack

ReactJavaScriptAPI IntegrationCSSE-Commerce UI

05

Contact Keeper Client

Frontend application for authenticated contact management workflows.

Problem

Users need a private, responsive way to manage personal contacts without losing context between sessions.

Solution

Implemented a React interface focused on authenticated flows, stateful forms, contact lists, and API-driven updates.

Review focus

A concise example of React state management, authenticated user flows, forms, and frontend API integration.

Tech stack

ReactJavaScriptAuthenticationAPI IntegrationCSS

06

Remote Talks Client

Frontend product interface for remote communication and collaboration use cases.

Problem

Remote communication tools need approachable UI patterns that keep conversations, presence, and collaboration flows easy to understand.

Solution

Created a React client that presents collaboration-oriented views and keeps interface concerns separated into reusable frontend pieces.

Review focus

Review this for product UI structure, component organization, and collaboration-focused frontend flows.

Tech stack

ReactJavaScriptProduct UIResponsive DesignCSS

Looking for a backend-leaning full-stack engineer?

I can help design the data model, build the API, connect the UI, and keep the implementation understandable for the next engineer who joins the project.

Start a conversation