How to Scale a Marketplace: Liquidity Before Growth
Decide when to expand a marketplace using liquidity, repeat transactions, operating capacity and bounded acquisition tests—not traffic alone.
Alexander Rocket8 min readUpdated
For most new web and mobile products in 2026, we would build the backend in TypeScript on Node.js, with NestJS and PostgreSQL. Pick Python when the product is mostly data or AI work. Stay on PHP if you are growing a WordPress or Laravel product that already earns money. Pick Java or .NET when a big customer or your own team requires it. Whatever you pick, start on a version that still gets security fixes, use a database you can trust and make sure you can hire for it.
What happened to the 2022 list
In December 2021 this post named five backend technologies to follow: PHP, Python, Java, Node.js and NestJS. All five are still in wide use. What changed is how you should choose between them.
The numbers below come from the Stack Overflow Developer Survey 2026, which had more than 30,000 responses. Each figure is the share of people who answered that question and said they had done extensive work in the technology over the past year.
| 2022 pick | Where it stands now | Our take for a new product |
|---|---|---|
| PHP | Used by 17.7% of respondents; Laravel by 7.6% | Fine for WordPress and Laravel products. We rarely start a new product on it |
| Python | Used by 58.0%; FastAPI by 18.5%, Django by 11.3% | First choice when AI, data or scripts are the core of the product |
| Java | Used by 27.6%; Spring Boot by 12.8% | Good for large company systems and teams that already know it |
| Node.js | The most used web technology in the survey, at 46.4% | Our default for web and mobile backends |
| NestJS | Used by 5.8%, while Express is used by 15.6% | Our default framework on Node.js for products that will grow |
Two more numbers from the same survey matter for hiring. JavaScript is used by 62.0% of respondents and TypeScript by 43.8%. If your web app and your mobile app are written in TypeScript, a backend in TypeScript lets the same people work on all three.
Why the support date matters more than the trend
Every runtime and database has an end date. After it, nobody ships security fixes. A product that launches on an old version starts life with a forced upgrade in its backlog.
Check these before anyone writes code. All dates come from the projects’ own pages: Node.js releases, Python versions, PHP supported versions and PostgreSQL versioning.
| Technology | Start a new product on | Avoid |
|---|---|---|
| Node.js | v26, v24 or v22, all LTS. Node.js says production apps should use only LTS releases | v20 and older, which are end of life |
| Python | 3.14 (bug fixes, planned end of life October 2030) or 3.15 (released October 2026) | 3.11, which gets security fixes only until about October 2027 |
| PHP | 8.4 or 8.5 | 8.2, whose security support ends 31 December 2026 |
| PostgreSQL | 18, supported until 14 November 2030 | 14, whose support ends 12 November 2026 |
If your product already runs on one of the versions in the right column, plan the upgrade now. It is cheaper as a planned task than as a fix after a security alert.
How to choose: four questions
- What does the product mostly do? Accounts, payments, chat, bookings and admin panels suit Node.js well. Model training, data pipelines and heavy number work suit Python.
- Who will look after it in two years? Pick a language you can hire for in your market and budget. A rare language makes every future hire slower.
- What does your first big customer require? Some banks and large companies have an approved list. Ask before you build, not after the pilot.
- What must it connect to? Check that the payment provider, bank feed or AI service you need has a maintained library for your language.
If two answers point to different languages, you can split the work. Keep the main backend in TypeScript and put the AI or data part in a small Python service.
The default stack we would start with
- Write the backend in TypeScript on Node.js, with NestJS. NestJS gives the code a clear structure: modules, tests and a standard way to add features. For a small single-purpose service, Express is enough. Our guide to NestJS, Express and Fastify covers that choice.
- Use PostgreSQL for data. In the 2026 survey, 57.9% of respondents to the database question used it, ahead of MySQL at 35.1% and MongoDB at 19.0%. Start with one relational database unless you have a clear reason not to.
- Redis for caching and background jobs, added when you need it.
- Docker to package the app, and a cloud account in your company’s name.
This is close to what our case studies use. Our web app development page lists Node.js with Nest.js or Express, Python or PHP on the backend, and PostgreSQL, MySQL, MongoDB or Redis for data.
Two examples:
- Ginger Snail, a learning app for law students, runs on Node.js and Nest.js with PostgreSQL, Redis and RabbitMQ, shipped with Docker and Kubernetes. The case page lists 10K requests per second the system can handle and 150 ms request processing.
- Dice Chess is a game that dates back to 1999. We updated its front end and back end on Nest.js, Node.js and PHP with MongoDB. It handles 10,000+ requests per minute.
When we would not pick Node.js
- The product is mostly machine learning or data processing. Use Python.
- Your company already runs Java or .NET and has people who maintain it. Use what they know.
- You need a content site with a blog and a few forms. WordPress may be all you need.
- You need very low-level speed, such as video processing or trading engines. Go or Rust may fit better; in the survey, 16.5% used Go and 18.0% Rust.
What the backend costs in a first version
The backend is usually one of the two biggest parts of a first version, next to the screens. In every example run of our estimate’s math with sample inputs, backend and frontend together took more than half of the hours.
A typical MVP with us costs $5,000 to $15,000 and takes 2 to 4 weeks. For comparison, across 95 agencies the median published MVP starting price is $13,234 (Rocketech MVP Price Index 2026, H2 edition). Those are published prices, not what agencies charge after scoping.
How we would estimate your backend
- Our project estimate turns your brief into user stories. You confirm what is in scope, and every hour in the budget traces back to a story you kept.
- We check the hours the model suggests against what our team actually books on finished projects, then multiply by our published rate of $39-55 an hour.
- You get an hours range, a budget range and a number of weeks. It is a planning range, not a fixed quote.
Uncheck a story and its hours come off. That makes it easy to see what each backend feature costs before you commit. You can run your idea through our project estimate; it takes about four minutes.
What we would do
- Write down the three jobs the backend must do in the first release. Leave the rest for later.
- Pick the runtime and database versions from the table above.
- Use PostgreSQL unless you have a clear reason to use something else.
- Put the cloud account, the domain and the code repository in your company’s name from day one.
- Add logs, error alerts and daily backups before launch, not after the first outage.
- Put version upgrades on the calendar twice a year.
If you have inherited a backend and don’t know what state it is in, start with an audit. Our code audit costs a fixed $3,500, takes 5 working days and tells you what to keep, fix or rebuild.
Looking for a reliable software development team?
Let’s discuss your product idea.
Let’s discuss your product idea.
FAQ
What is the best backend technology for a startup in 2026?
For most web and mobile products, TypeScript on Node.js with NestJS and PostgreSQL. Pick Python when AI or data work is the core of the product, and Java or .NET when your team or a large customer already uses it.
Is PHP still worth using in 2026?
Yes, for WordPress and Laravel products. PHP 8.4 and 8.5 get active support. If you are on PHP 8.2, plan an upgrade, because its security support ends on 31 December 2026.
Should an AI product use Node.js or Python?
Often both. Keep accounts, payments and the API in Node.js, and put the AI or data part in a small Python service. If the whole product is model work, start in Python.
How much does backend development cost for an MVP?
The backend is part of the first version, not a separate bill. A typical MVP with us costs $5,000 to $15,000 and takes 2 to 4 weeks. Across 95 agencies, the median published MVP starting price is $13,234.