Microservice Marketplace
35 components, a gateway, a message bus, process orchestration
The source code of a full enterprise-scale marketplace: thirty-five components, twenty-one of them Java and Spring backend services behind a single gateway, each with its own database, an asynchronous bus between them, and business processes described and executed by an orchestration engine rather than scattered through the code as conditionals. This is not a storefront with a cart: it has warehousing, logistics, billing, fiscal receipts, cashback and three separate frontends — for the buyer, the seller and the warehouse.
Building the same from scratch costs on average 40–70% more — that is $42,000–51,000. And even counting the purchase price, adapting a ready product to your task comes out cheaper: you pay for the differences only, not for what is already written and proven in use. This is the studio's estimate, not a measurement: the exact figure depends on how much has to be reworked.
What is included
Services: commerce
- Catalogue: products, categories, attributes, listing moderation
- Search on Elasticsearch: facets, synonyms, ranking
- Sales: orders, cancellations, returns, statuses
- Checkout as a separate service and frontend
- Seller content: reviews, questions, media
- CMS: banners, collections, static pages
Services: money and warehouse
- Payment gateway: collecting payment, holds, refunds
- Billing: settlements with sellers, commissions, reconciliation
- Fiscal service: receipts and reporting to the tax authority
- A receipt generator on NestJS rendering to PDF
- Warehouse: stock, receiving, shipping, stocktaking
- Logistics: delivery, routes, shipment statuses
- Bonuses and cashback as a separate service
Frontends and bots
- Buyer storefront and site on Next.js
- Seller cabinet and platform admin on React
- A warehouse interface (WMS) as a separate application
- An in-house UI kit and icon set shared across all frontends
- A seller bot and a transport-service bot in Telegram
Infrastructure and integrations
- A single Spring Cloud Gateway in front of every service
- An asynchronous RabbitMQ bus between services
- Business processes in the Camunda orchestration engine, not in code
- A PostgreSQL database per service, a shared Redis for sessions and permissions
- Integrations for the Uzbek market: Click, Uzum, Didox, fiscal, reference registries
- Secrets moved out into environment variables, none left in the code
Technologies
- Java 17
- Spring Boot
- Spring Cloud Gateway
- Camunda BPM
- RabbitMQ
- PostgreSQL
- Elasticsearch
- Redis
- React
- Next.js
- NestJS
- Docker
How it earns
- A commission on seller sales — the platform's primary model
- Paid promotion of products in search and collections
- A subscription for an extended seller cabinet
- Warehousing and logistics services charged separately
- Advertising and banners on the storefront
Readiness
The code of a marketplace that ran, not a skeleton: all thirty-five components are written and wired together. But it is an enterprise system, and deploying it is not «bring up a container»: it needs a cluster, separate databases, a message broker, a search cluster and someone to operate all of it. Budget for running costs, not just the purchase price.
What we need from you
- Infrastructure: a cluster, databases, a message broker, a search cluster
- An operations engineer — a microservice system does not run itself
- Contracts with payment systems and a fiscal data operator
- Their own keys for every external integration
- Legal setup of the platform and contracts with sellers
Prices are final, in US dollars, VAT not applicable. Payment by invoice to a legal entity.
// we reply within 20 seconds
A manager is already here, waiting for your message
Write in the chat and tell us what you need built. The first reply arrives within 20 seconds, around the clock — if we miss it, you get 30% off your project. We'll work the task out right there and suggest where to start.
DevUz manager
already here, waiting for your message
By continuing this conversation you agree to the processing of personal data.
Or leave your contacts
The studio has no phone line — write on Telegram or leave a contact in the form, and we reply in the same channel.