How do I design a table in Cassandra for a TinyURL use case?

Question

Recently I came across a well-known design problem. 'Tiny URL'

What I found was people vouching for NoSQL DBS such as DynamoDB or Cassandra. I've been reading about Cassandra for a couple of days, and I want to design my solution around this DB for this specific problem.

1. What would be the table definition? If I choose the following table definition:

Create table UrlMap(tiny_url text PRIMARY KEY, url text);

Wouldn't this result in a lot of partitions? since my partition key can take on around 68B values (using 6 char base64 strings)

Would that somehow affect the overall read/write performance? If so, what would be a better model to define the table.

Answer 1

Lot's of partitions is fine, think of it as using c* as a key value store.