phoenix
phoenixPhoenix - Your AI Assistant
Inactive session will be ended in 24 hours
End Session

Backend Developer: E-Commerce Inventory Sync & Redis Order Queue

  • Posted:
  • Proposals: 81
  • Remote
  • #4505891
  • Open for Proposals
Awais A.Zain A.Aurel H.Prince Pratap M.Dhirendra K. + 76 others have already sent a proposal.
  • 9

Description

Experience Level: Expert
We are scaling a high-traffic e-commerce platform and are seeking a proficient Backend Developer to optimize and extend our server-side architecture. The primary objective is to fortify our backend against peak traffic surges during promotional events, entirely mitigating database latency and eliminating overselling risks. The scope of work is precisely delineated, offering an engaging project for a Senior specialist looking for a clean architectural implementation, or a seasoned Mid-level engineer keen to demonstrate their expertise in high-load scenarios.

Scope of Work

Autonomous Inventory Synchronization: Develop a robust standalone service to synchronize stock levels between our central database and an external Warehouse Management System, ensuring graceful handling of data conflicts and partial updates.

High-Load Order Queueing: Implement a Redis-based queue system to process incoming checkout requests sequentially. This is critical to preventing race conditions when hundreds of users attempt to purchase identical inventory concurrently.

Database Optimization: Review our current relational database to identify, profile, and rewrite heavy queries that trigger performance degradation during peak hours.

Resilient Webhook Architecture: Establish an idempotent and fault-tolerant architecture to handle incoming webhooks from payment gateways, complete with sophisticated retry logic for failed requests.

Tech Stack & Requirements

Proficiency in either Node.js with NestJS or Express, or PHP with Laravel. We are completely open to selecting the optimal tool based on architectural alignment.

Deep understanding of relational databases (MySQL or PostgreSQL) and hands-on experience in SQL query optimization.

Practical experience with Redis for queue management, caching, and distributed locking.

Solid grasp of high-availability backend design and RESTful API architecture.

Commitment to writing clean, well-documented, and highly maintainable code.

Project Budget & Timeline

Fixed Budget: $1,450 USD

Expected Timeline: 2–3 weeks from project kickoff

When submitting your proposal, please provide a brief summary of your experience with similar high-load challenges, such as queue management or heavy data synchronization. Additionally, let us know which technology stack you would recommend for this specific service and why.

New Proposal

Login to your account and send a proposal now to get this project.

Log in

Clarification Board Ask a Question

  • Sudhanshu K.

    Before recommending the optimal stack, can you share your current backend architecture (Node/Laravel/etc.), current database size and peak traffic numbers during promotional events, and whether overselling is already happening in production or this is a preventative upgrade?

  • Muhammad Ather A.

    Hi Mivida,

    A few questions before we finalize the implementation plan:

    1. Which Warehouse Management System (WMS) are you currently integrating with?

    2. Is your existing backend built in Laravel, Node.js, or another framework?

    3. Approximately how many concurrent checkout requests do you expect during peak campaigns?

    4. Are you currently using Redis anywhere in your infrastructure, or will this be a new implementation?

    5. Do you already have monitoring tools such as Grafana, Prometheus, or CloudWatch in place?

    Looking forward to your response.

    Best,
    VConn Pvt Ltd

  • Eight Veer Ltd

    Hi Mivida,

    Before we lock the first delivery phase, we would like to confirm where stock is currently reserved or deducted in the checkout flow. Is this happening at add-to-cart, checkout start, payment authorisation, payment capture, or order creation?

    That answer will shape whether Redis should be used mainly as a queue, a locking layer, a reservation layer, or alongside database constraints. It would also help to know which issue is causing the most pressure today: overselling during concurrent checkout, WMS stock drift, slow SQL under load, or failed/duplicate payment webhooks.

  • CYTNHIA W.

    One question: Is your current database MySQL or PostgreSQL, and do you already have Redis running in your infrastructure or does that need provisioning as part of this work?