How do I approach System Design interview questions?

System Design questions require understanding of core concepts and practice. PracHub provides solutions with explanations to help you master system design interviews.

What difficulty level is this interview question?

This is a medium difficulty System Design question, commonly asked during Technical Screen rounds at Booking.com.

What role is this question designed for?

This question is commonly asked for Software Engineer candidates at Booking.com during technical interviews.

Compare heap, stack, Protobuf, gRPC, SQL, CI/CD | Booking.com Interview Question

Quick Overview

Compare heap, stack, Protobuf, gRPC, SQL, CI/CD evaluates requirements, scale assumptions, API/data design, architecture, trade-offs, failure modes, and rollout in a realistic interview setting. A strong answer states assumptions, handles edge cases, explains trade-offs, and shows how to validate the result clearly.

Compare heap, stack, Protobuf, gRPC, SQL, CI/CD

Technical/Phone Screen: Core Systems and Data Concepts

You are interviewing for a Software Engineering role. Answer the following multi-part question concisely and clearly:

What is the difference between stack and heap memory?
Compare Protobuf and JSON for data serialization.
Compare gRPC and traditional RPC mechanisms.
When is event streaming (e.g., Kafka) appropriate?
When should you use a table join in SQL?
What does SQL stand for?
What does CI/CD stand for?

Constraints & Assumptions

Preserve the scope, facts, inputs, and requested outputs from the prompt above.
If the prompt leaves a detail unspecified, state a reasonable assumption before relying on it.
Keep the answer interview-ready: concise enough to present, but concrete enough to implement or evaluate.

Clarifying Questions to Ask Guidance

Clarify users, core use cases, read/write patterns, scale, latency, availability, and data retention.
State explicit assumptions before making sizing or architecture decisions.
Prioritize the functional path first, then address reliability, security, observability, and rollout.

What a Strong Answer Covers Guidance

A scoped requirements summary with concrete non-goals and success metrics.
API, data model, architecture, consistency, capacity, and operations.
Reasoned trade-offs among simple and scalable designs, including bottlenecks and failure modes.
A validation, monitoring, migration, and launch plan appropriate for the risk level.

Follow-up Questions Guidance

What breaks first at 10x traffic or data volume?
How would you degrade gracefully during dependency failures?
What metrics and alerts would prove the design is healthy after launch?

Quick Overview

Technical/Phone Screen: Core Systems and Data Concepts

You are interviewing for a Software Engineering role. Answer the following multi-part question concisely and clearly:

What is the difference between stack and heap memory?

Compare Protobuf and JSON for data serialization.

Compare gRPC and traditional RPC mechanisms.

When is event streaming (e.g., Kafka) appropriate?

When should you use a table join in SQL?

What does SQL stand for?

What does CI/CD stand for?

Constraints & Assumptions

Preserve the scope, facts, inputs, and requested outputs from the prompt above.

If the prompt leaves a detail unspecified, state a reasonable assumption before relying on it.

Keep the answer interview-ready: concise enough to present, but concrete enough to implement or evaluate.

Clarifying Questions to Ask Guidance

Clarify users, core use cases, read/write patterns, scale, latency, availability, and data retention.

State explicit assumptions before making sizing or architecture decisions.

Prioritize the functional path first, then address reliability, security, observability, and rollout.

What a Strong Answer Covers Guidance

A scoped requirements summary with concrete non-goals and success metrics.

API, data model, architecture, consistency, capacity, and operations.

Reasoned trade-offs among simple and scalable designs, including bottlenecks and failure modes.

A validation, monitoring, migration, and launch plan appropriate for the risk level.

Follow-up Questions Guidance

What breaks first at 10x traffic or data volume?

How would you degrade gracefully during dependency failures?

What metrics and alerts would prove the design is healthy after launch?

Compare heap, stack, Protobuf, gRPC, SQL, CI/CD

Quick Overview

Compare heap, stack, Protobuf, gRPC, SQL, CI/CD

Compare heap, stack, Protobuf, gRPC, SQL, CI/CD

Technical/Phone Screen: Core Systems and Data Concepts

Constraints & Assumptions

Clarifying Questions to Ask Guidance

What a Strong Answer Covers Guidance

Follow-up Questions Guidance

Submit Your Answer to Earn 20XP

Compare heap, stack, Protobuf, gRPC, SQL, CI/CD

Quick Overview

Compare heap, stack, Protobuf, gRPC, SQL, CI/CD

Compare heap, stack, Protobuf, gRPC, SQL, CI/CD

Technical/Phone Screen: Core Systems and Data Concepts

Constraints & Assumptions

Clarifying Questions to Ask Guidance

What a Strong Answer Covers Guidance

Follow-up Questions Guidance

Submit Your Answer to Earn 20XP