List pattern
Whenever a list appears in a real-world use case, use the Cassandra data type the List pattern in the column family. Whenever the list in the real-world use case mandates the order of items, the List data type in Cassandra is ideal. Whenever there is a need to store the same value or object multiple times in the data store, the List data type in Cassandra is the best type to go with.
Motivations/solutions
In the normalized RDBMS tables, whenever there is a need to have a list of things associated with an entity, the easiest, no-brainer approach is to have a one-to-many relationship of two tables. When reports or other business processes need all these pieces of data together, a multi-table join is used. The joins on multiple tables always perform badly when the number of records in the tables are huge. This affects the read performance as well as the write performance. The performance is affected because of two reasons. One, as mentioned earlier, is the need to do table joins...
