Requirements and Goals of the System
Our Pastebin service should meet the following requirements:
Functional Requirements
Users should upload or “paste” their data and get a unique URL to access it.
Users will only be able to upload text.
Data and links will automatically expire after a specific timespan; users should also specify expiration time.
Users should optionally be able to pick a custom alias for their paste.
Non-Functional Requirements
The system should be highly reliable, any data uploaded should not be lost.
The system should be highly available. This is required because if our service is down, users will not access their Pastes.
Users should be able to access their Pastes in real-time with minimum latency.
Paste links should not be guessable (not predictable).
Requirements and Goals of the System
Our Pastebin service should meet the following requirements:
Functional Requirements
Users should upload or “paste” their data and get a unique URL to access it.
Users will only be able to upload text.
Data and links will automatically expire after a specific timespan; users should also specify expiration time.
Users should optionally be able to pick a custom alias for their paste.
Non-Functional Requirements
The system should be highly reliable, any data uploaded should not be lost.
The system should be highly available. This is required because if our service is down, users will not access their Pastes.
Users should be able to access their Pastes in real-time with minimum latency.
Paste links should not be guessable (not predictable).
Extended Requirements
Analytics, e.g., how many times a redirection happened?
Our service should also be accessible through REST APIs by other services.