Design a resilient bootstrap API

Q: Design a resilient bootstrap API

This question evaluates skills in resilient API aggregation, fault-tolerant microservice orchestration, and reliability engineering, focusing on defining API contract semantics and handling partial failures at the architectural/system-design level (service-to-service abstraction); category/domain: System Design.

Q: 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.

Question

You are given three internal services (or internal APIs):

User Service : GET /user-to-consumer?user_id=... → returns { consumer_id, user_profile... }
Payments Service : GET /payment-info?consumer_id=... → returns { payment_methods... }
Address Service : GET /address-info?consumer_id=... → returns { addresses... }

Design and implement a Bootstrap API:

Endpoint: GET /bootstrap?user_id=...
It must return a response that aggregates:
- user/profile information
- payment information
- address information

Key requirement: the endpoint should be as resilient to failures as possible (downstream timeouts/errors/partial outages). Describe:

The API contract (including what happens on partial failures)
The service orchestration logic (ordering, concurrency)
Reliability strategies (timeouts, retries, circuit breakers, fallbacks, caching)
Observability and operational considerations

Assume typical microservice constraints and that downstream services may be slow or intermittently unavailable.

Design a resilient bootstrap API

Quick Overview

Solution

Comments (0)