We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
We use a Redis store for the shortened links. There were two reasons we made this choice:
After running this in production for 9+ months, we've seen the database grow to nearly 15 GB. The cap at Compose, where this is hosted, is 17 GB.
Let's think about the right choice for this use case, in terms of
The text was updated successfully, but these errors were encountered:
No branches or pull requests
We use a Redis store for the shortened links. There were two reasons we made this choice:
After running this in production for 9+ months, we've seen the database grow to nearly 15 GB. The cap at Compose, where this is hosted, is 17 GB.
Let's think about the right choice for this use case, in terms of
The text was updated successfully, but these errors were encountered: