Design a collaborative, editable code notebook service with an execution service and a proxy that fetches execution results and returns them to the browser. Users may upload custom function JAR files with a fully qualified class and method name, then submit requests to run that function with arguments. Define RESTful endpoints and request and response schemas for uploading code, submitting executions, fetching logs and results, and cancelling. Discuss sandboxing, dependency management, resource limits, concurrency, and result streaming.

This question evaluates a candidate's competence in designing secure, scalable systems for executing user-supplied code, covering API design, sandboxing and isolation, dependency management, resource limits, scheduling, and streaming proxies for logs/results.

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 hard difficulty System Design question, commonly asked during Technical Screen rounds at Google.

What role is this question designed for?

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

Design executable notebook service APIs | Google Interview Question

Design: Collaborative Notebook with Executable User Functions (JAR Upload)

Context

Design a collaborative, browser-based code notebook service. The system must support real-time editing, execution of user-submitted functions, and a proxy that fetches execution results/logs and returns them to the browser.

Users can upload custom Java JARs, specify a fully-qualified class and method as the entrypoint, and submit executions with arguments. The system must be secure, scalable, and support streaming logs/results.

Requirements

Define RESTful endpoints and request/response schemas for:
1. Uploading user code (JARs) and registering entrypoints
2. Submitting executions (sync/async, with args)
3. Fetching logs and results (polling and streaming)
4. Cancelling executions
Discuss:
- Sandboxing and isolation for untrusted code
- Dependency management for user JARs (Maven coordinates, shading, etc.)
- Resource limits and quotas
- Concurrency model and scheduling
- Streaming logs/results to the browser via a proxy

Make minimal assumptions where the prompt is ambiguous (e.g., use Java 17, JSON over HTTP, and an API Gateway/Proxy).

Context

Requirements

Define RESTful endpoints and request/response schemas for:

Uploading user code (JARs) and registering entrypoints
Submitting executions (sync/async, with args)
Fetching logs and results (polling and streaming)
Cancelling executions

Discuss:

Sandboxing and isolation for untrusted code
Dependency management for user JARs (Maven coordinates, shading, etc.)
Resource limits and quotas
Concurrency model and scheduling
Streaming logs/results to the browser via a proxy

Make minimal assumptions where the prompt is ambiguous (e.g., use Java 17, JSON over HTTP, and an API Gateway/Proxy).

Design executable notebook service APIs

Quick Overview

Design: Collaborative Notebook with Executable User Functions (JAR Upload)

Context

Requirements

Solution

Comments (0)

Design executable notebook service APIs

Quick Overview

Design: Collaborative Notebook with Executable User Functions (JAR Upload)

Context

Requirements

Solution

Comments (0)