Design a cloud resource marketplace platform
PremiumBackend systemHard
- Distributed transactions
- Stream processing
- Resource allocation
Quick answer
This backend system interview question asks you to design a cloud resource marketplace platform. Aim for a design that meets its requirements at the stated scale, then explain its main components, data flow and trade-offs. Interviewers want to see how you scope the problem, size it and defend each choice.
The problem
Design a Cloud Resource Marketplace Platform. As AI and compute demands skyrocket, organizations with spare infrastructure (Providers) want to lease their unused GPUs and CPUs to external developers (Consumers).
Providers list available capacity pools with minimum asking prices. Consumers submit workloads (e.g., a distributed ML training job) with maximum bid prices. The platform must operate an auction matching engine to pair workloads with resources, dispatch the workload, and continuously ingest telemetry to meter usage. Finally, it must translate this telemetry into exact financial billing settlements without dropping data or double-charging.
What must a cloud resource marketplace platform do?
- Resource Discovery & Auction: Continuously match incoming Consumer bids with Provider asks based on resource type (e.g., A100 GPU), region, and price.
- Workload Placement: Once a match is made, issue a secure lease and dispatch the workload definition to the Provider's agent.
What scale should you design for?
Use these numbers in your estimates.
The scale numbers unlock with this questionUnlock
Key concepts
- Distributed transactions
- Stream processing
- Resource allocation
- Event driven
- Financial systems
How you’ll practise
- Requirements
- Estimate
- API and data
- High-level design
- Deep dives
- Wrap-up
Lala, personalized to you, gives a hint when you ask and reviews your design when you are ready.
What do interviewers look for?
In any backend system design round.
- Clarifies the requirements before drawing anything
- Uses a few numbers that actually change the design
- Draws a clear path from the client to storage
- Picks storage and caching with reasons, not by habit
- Explains what breaks first under load and how to fix it
- States trade-offs openly instead of claiming a perfect design
Questions people ask about this interview question
- Which design type is this question?
- It is a backend system question. You design a cloud resource marketplace platform and explain your choices the way you would in an interview.
- Is this question asked at entry level?
- It is marked Hard. It suits engineers preparing for senior interviews, where you are expected to drive the discussion and go deep on trade-offs.
- What should I cover first?
- Start with the requirements: what the system must do, how well it must do it and which numbers change the design. Agree on scope with the interviewer before you design anything.
- Can I practise it for free?
- It is a premium question. Sign up and unlock it once for 10 credits; it then stays unlocked. When you finish, Lala, your personalized AI mentor, can review your design for 30 credits.
Related questions
Updated · Written by the SevyDevy team