Reconsider link storage

[mshmsh5000]

We use a Redis store for the shortened links. There were two reasons we made this choice:

1. The data model couldn't be simpler, so we wanted a simple storage technology
2. We need the most lightweight storage possible, given the very bursty write patterns during SMS broadcasts

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

• Scalability
• Operational cost
• Hosting options