Requirements

Functional Requirements:

• Allow users to browse and search available conference rooms by time slot, capacity, location (building/floor), and equipment (projector, video).
• Enable users to create, update, and cancel room bookings, including room, time, organizer, and optionally participants.
• Prevent double-booking of rooms by ensuring that concurrent booking attempts are serialized.
• Send users email or push notifications when a booking is confirmed, updated, or cancelled, and send reminder notifications before the meeting starts.
• Support user authentication and authorization with role-based access controls: regular users can book rooms, admins can manage room inventory and settings.

Non-Functional Requirements:

• Reliability and accuracy of a data.
• Strong consistency as if one user reserves the room then the other needs to see it booked. such as preventing double-booking through database transactions or locking mechanisms.
• High availability (system responds in max. 2 seconds). expected availability percentage (e.g., 99.9%+)
• Low latency

Capacity Estimation

There are arount 100

Estimate the scale of the system. Consider daily active users, read/write ratio, storage requirements, bandwidth, and any relevant QPS calculations...

API Design

Admin Panel with restricted privilidges:

1) Creating rooms:

POST: /api/rooms

2) Updating rooms:

PUT: /api/rooms/:roomId

3) Deleting rooms:

DELETE: /api/rooms/:roomId

User:

1) Searching rooms:

GET: /api/rooms

Params: start_from, end_to, equipments, capacity

2) Book room:

POST: /api/rooms/:roomid

Params: start_from, end_to

return 200 or already booked

High-Level Design

Describe the overall system architecture. Identify the main components needed to solve the problem end-to-end. Use the diagramming tool to create a block diagram.

Database Design

Define the data model. Identify the main entities, their attributes, and relationships. Consider the choice of database type (SQL vs NoSQL) and justify your decision based on access patterns...

Detailed Component Design

Deep dive into 2-3 key components. Explain how they work, how they scale, discuss tradeoffs, capacity, and any relevant algorithms or data structures.