Design Pastebin

Functional Requirements:

• Users can create a new paste by submitting text content.
• Each paste is assigned a unique URL for sharing and retrieval.
• Users can specify an expiration time for the paste (e.g., 1 hour, 1 day, 1 week, never).
• Anyone with the URL can view the paste until it expires.
• Optionally, users can delete their paste before expiration (if we want to support this).

Non-Functional Requirements:

• High availability: The service should be accessible at all times.
• Low latency: Pastes should be created and accessed quickly.
• Scalability: The system should handle increasing numbers of pastes and reads.
• Data durability: Pastes should not be lost before their expiration.
• Security: Only users with the correct URL can access a paste; no unauthorized access.
• Abuse prevention: The system should prevent spam and excessive usage (e.g., via rate limiting).