Design a Timestamped Cloud Credit Ledger with Rebates, Merges, and History

Question

Design a timestamped cloud credit ledger that manages credit operations like rebates, merges, and maintains a history of transactions.

Codemia · Accepted Answer

To design a timestamped cloud credit ledger, we need to consider the following requirements:
1. **Unique Timestamps**: Each operation must have a unique timestamp.
2. **Operations**: The system should support operations like credit allocation, rebates, and merging credits.
3. **History Tracking**: The system must maintain a history of all operations for auditing purposes.
4. **Performance**: The system should efficiently handle a large number of operations and queries.

The high-level architecture of the credit ledger can be divided into several components:
- **Operation Manager**: Handles incoming operations and ensures they are processed in the order of their timestamps.
- **Credit Ledger**: A data structure (like a balanced tree or a hashmap) to store current credits associated with each workspace.
- **History Log**: A separate log that records all operations for auditing and rollback purposes.
- **API Layer**: Provides endpoints for clients to interact with the ledger.

For storing the credits and operations, I would use:
- **HashMap**: To quickly access and update the credit balance for each workspace.
- **Sorted List**: To maintain the history of operations in chronological order, allowing for efficient retrieval and auditing.
This combination allows for O(1) access time for updates and O(log n) for historical queries.

One major trade-off is between consistency and availability. Using a distributed system could enhance availability but may complicate consistency. To scale the system:
- **Sharding**: Split the ledger across multiple servers based on workspace IDs.
- **Caching**: Implement caching for frequently accessed data to reduce load on the database.
These strategies help maintain performance as the number of operations increases.

Here is a simplified Python implementation for processing a rebate operation:
```python
class CreditLedger:
    def __init__(self):
        self.credits = {}
        self.history = []

def rebate(self, timestamp, workspace_id, amount):
        if workspace_id not in self.credits:
            self.credits[workspace_id] = 0
        self.credits[workspace_id] -= amount
        self.history.append((timestamp, 'rebate', workspace_id, amount))

def get_balance(self, workspace_id):
        return self.credits.get(workspace_id, 0)
```
This code snippet demonstrates how to manage rebates while maintaining a history of transactions.

Design a Timestamped Cloud Credit Ledger with Rebates, Merges, and History

Coinbase

What the Interviewer Expects

Key Topics to Cover

How to Approach This

Possible Follow-up Questions

Sharpen Your Skills on Codemia

Sample Answer

Requirements

High-Level Design

Submit Your Answer

Coinbase Software Engineer Interview Guide

Related Questions

Design a scalable Search System

Design a Video Streaming for Rippling

Design a Load Balancing Service

Design a Image Processing Service

Build a high-throughput Image Processing Pipeline