The network for creativity
Join 1.25M professional creatives like you
Connect with clients, get discovered, and run your business 100% commission-free
Creatives on Contra have earned over $150M and we are just getting started
Back to feedPost
For a multi-tenant backend, I keep tenant configuration out of the Docker build whenever the tenants run the same code.
One application image. Tenant configuration at runtime. Separate deployment credentials and data boundaries.
In GitHub Actions, I copy package manifests before application source, use npm ci, and reuse BuildKit cache. A source edit shouldn’t force a fresh dependency installation.
The multi-stage Dockerfile keeps compilers and build tools out of the runtime image.
I also tag images with the commit SHA and promote the same artifact through staging and production.
Build speed matters, but so does knowing that the image tested in staging is the image being deployed. Database migrations get an explicit step, with compatibility checked before rollout.
The network for creativity
Join 1.25M professional creatives like you
Connect with clients, get discovered, and run your business 100% commission-free
Creatives on Contra have earned over $150M and we are just getting started
Related posts
Full-Stack Developer & AI Automation Engineer
I build scalable web applications, SaaS platforms, mobile apps, custom dashboards, and AI-powered automation systems that turn complex business workflows into reliable digital products.
My core stack includes Next.js, React, Node.js, NestJS, Python, PostgreSQL, MongoDB, and AI APIs.
I specialize in turning ideas into production-ready systems—from architecture and development to deployment, automation, and optimization.
Available for:
AI Automation • SaaS Development • Web Development • Mobile Apps • Custom Dashboards • API Development • Business Automation
Seeing how you stitch AI APIs into custom dashboards really cuts the manual data wrangling. The stack choice keeps the deployment pipeline smooth.
Can you answer these 5 system design questions in 30 seconds each? ⏱️
Out loud, while an interviewer is watching 👇
1️⃣ 1,000 requests hit one expired cache key at the same moment. How do you protect the database?
2️⃣ You add 1 node to a 3-node cache using key mod N. Roughly how many keys move?
3️⃣ 3 partitions, 4 consumers in one Kafka group. What does the 4th consumer do?
4️⃣ 3 service layers each retry 3 times. How much traffic hits the failing service?
5️⃣ A client retries a payment with the same idempotency key but a different amount. 200, 409 or 422?
If you hesitated on even one, you're not alone. Most engineers know these topics. The hard part is explaining the trade-off clearly, saying when not to use it, and surviving the follow-up.
That's why I built the System Design Interview Crack Sheet 📘
✅ 49 concepts, one page each
✅ 98 interviewer questions with ready 30-second answers
✅ 49 colour-coded diagrams that show the real mechanism
✅ Use when / avoid when / how it fails, for every concept
✅ 49 follow-up questions interviewers use to dig deeper
✅ Decision matrix, acronym glossary and a clickable revision map
Covers caching, sharding, consistent hashing, replication, Kafka, sagas, outbox & CDC, CAP & PACELC, consensus, idempotency, rate limiting, circuit breakers, multi-region & DR, and more.
🎯 Made for backend, SDE-2, senior and staff interviews
⚡ 64-page PDF · instant download · free updates
📘 Get the full crack sheet here:
https://contra.com/products/moOF13Ea-system-design-interview-crack-sheet
I developed Movam to bring customer ordering, merchant fulfilment, rider dispatch, and platform administration into one application.
I built the backend with Laravel and REST APIs, alongside Vue.js and TypeScript dashboards for customers, merchants, riders, and administrators.
Key features include:
Product browsing, cart, checkout, and order management.
Paystack payment integration, wallets, and OTP-verified withdrawals.
Dispatch logic that assigns deliveries to nearby available riders.
Mapbox integration for location services and delivery-distance calculations.
WebSocket events for order status and rider location updates.
Merchant product management and administrative reporting.
The project demonstrates my ability to translate business workflows into connected interfaces, backend services, and third-party integrations.
Tools: PHP, Laravel, Vue.js, TypeScript, Tailwind CSS, Pinia, Laravel Sanctum, Laravel Reverb, Paystack, and Mapbox.
Combining ordering, fulfilment and dispatch in one app probably trims a lot of manual steps. Laravel APIs feeding Vue TypeScript dashboards keep the data moving smoothly across customers, merchants and riders.