Nurudeen  SalihuFull-stack developer, Abuja

Multi-department operations platform

Built at JD Marc Limited / production, internal

A single workspace replacing nine departments' worth of spreadsheets and email threads. Staff, HR, and admin each see a different application, enforced at the database rather than in the interface.

The hard part: nine departments wanted nine different data shapes, and building nine schemas would have meant nine migrations every time something changed. I built a generic record layer on a single jsonb table, with department modules declaring their own fields on top — one schema, nine applications. Access is enforced with row-level security policies for the Admin, HR, and Staff tiers, so a bug in the frontend cannot leak another department’s records.

What it produced: reporting that used to arrive as an hourly batch now lands in under a second over a realtime channel, and roughly 40% of the repetitive steps in cross-department handoffs are gone.

React, Vite, Supabase (Postgres, RLS, Realtime), WebRTC signalling, TypeScript

Office management on service boundaries

Personal build / microservices and deployment practice

The same business problem rebuilt the other way: five-plus independent services behind an API gateway, each owning its own data, talking over HTTP and a message broker.

The hard part: once services own separate data, a single user action spans several of them. I used a Controller–Service–Repository layout so the transport layer never touches persistence, issued JWTs with roles at the gateway so downstream services trust one authority instead of each re-checking credentials, and pushed anything that could tolerate delay onto RabbitMQ rather than a synchronous call chain.

What I got from it: a deployment story I can actually explain — containers per service, Kubernetes manifests, and a GitHub Actions pipeline that builds, tests, and rolls out on merge.

Node.js, Express, MongoDB, RabbitMQ, Docker, Kubernetes, GitHub Actions

Aladdin Drive — automotive commerce

Personal build / payments and authentication

A digital showroom that has to take real money: listings, checkout, invoicing, and an admin side for products, users, and orders.

The hard part: payments are where a tidy demo starts lying to you. Two providers, two webhook shapes, and an order that must not be marked paid twice if a webhook retries. I made order state transitions idempotent and driven by the provider callback rather than the browser redirect, so closing the tab mid-payment does not lose the order.

Next.js, TypeScript, Tailwind, shadcn/ui, Auth.js (Google OAuth + magic link), Stripe, PayPal, MongoDB