Node.js Game Backend & Web3 API
Budget: $10,000 – $20,000 USD
I’m building a casual online game that lets players jump in instantly, while also giving enthusiasts the option to own in-game items on the blockchain. I’m looking for an experienced backend engineer to take full ownership of the server side.
What I need you to do
• Architect a scalable, modular backend in Node.js that cleanly separates core gameplay services from the optional Web3 layer.
• Design an efficient PostgreSQL schema for player profiles, matchmaking, leaderboards, inventories, and game telemetry.
• Expose well-documented REST (or GraphQL, if you believe it suits the use case better) endpoints that my Unity client and future live-ops tools can consume.
• Integrate an optional asset-ownership flow—think minting, transfers, and verification—without forcing blockchain on players who don’t want it. Ethereum-compatible chains such as Polygon are preferred, but I’m open to your recommendation.
• Apply best-practice security hardening, robust logging, and graceful error handling from day one.
• Package everything with Docker, provide CI/CD scripts, and supply automated unit, integration, and load tests.
• Hand over clear API docs, an ER diagram, sequence diagrams for the Web3 calls, and a deployment playbook so my team can operate the stack confidently.
What success looks like
• A clean, well-commented Node.js codebase that spins up locally with `docker-compose up`.
• All core game endpoints respond in <100 ms under typical load in staging.
• Web3 features run behind a feature flag and do not block normal gameplay if a chain is slow or unavailable.
• Postman (or Swagger) collection covering every public endpoint, plus markdown docs my designers can read.
If you’ve delivered gaming backends, crypto-enabled apps, or high-throughput APIs before, I’d love to see links or brief case studies. Let’s build something players will love—and developers can trust.
What I need you to do
• Architect a scalable, modular backend in Node.js that cleanly separates core gameplay services from the optional Web3 layer.
• Design an efficient PostgreSQL schema for player profiles, matchmaking, leaderboards, inventories, and game telemetry.
• Expose well-documented REST (or GraphQL, if you believe it suits the use case better) endpoints that my Unity client and future live-ops tools can consume.
• Integrate an optional asset-ownership flow—think minting, transfers, and verification—without forcing blockchain on players who don’t want it. Ethereum-compatible chains such as Polygon are preferred, but I’m open to your recommendation.
• Apply best-practice security hardening, robust logging, and graceful error handling from day one.
• Package everything with Docker, provide CI/CD scripts, and supply automated unit, integration, and load tests.
• Hand over clear API docs, an ER diagram, sequence diagrams for the Web3 calls, and a deployment playbook so my team can operate the stack confidently.
What success looks like
• A clean, well-commented Node.js codebase that spins up locally with `docker-compose up`.
• All core game endpoints respond in <100 ms under typical load in staging.
• Web3 features run behind a feature flag and do not block normal gameplay if a chain is slow or unavailable.
• Postman (or Swagger) collection covering every public endpoint, plus markdown docs my designers can read.
If you’ve delivered gaming backends, crypto-enabled apps, or high-throughput APIs before, I’d love to see links or brief case studies. Let’s build something players will love—and developers can trust.