Home/ Questions/Q 6583635
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-25T16:26:05+00:00

This is my first project using a NoSQL database and I am wondering how

  • 0

This is my first project using a NoSQL database and I am wondering how to structure my data in the most efficient way.

I am making a small service which stores all songs played by a radio station. Users can “like” the songs. So, basically I have the following data:

Song: Id, Artist, Title
Play: SongId, Time (when was the song played)
Like: SongId, UserName, Time (when did the user click the like button)

I need to run various queries on that data. For example: last X songs played + like count, top played songs in the last X days, who liked a specific song etc.

First I was thinking about storing everything in a single document with nested play and like information. But this makes some of the queries quite complicated and requires me to do stuff like sorting on the client side but I would like to keep the amount of data transfered from the database small.

I was also thinking about caching some of the most used queries in memory. Are there any general recommendations when doing something like that?

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    Since the number of songs, number of plays, number of users are all going to be large, using embedded documents for any of them isn’t going to work so you are forced somewhat to go back to a more relational model and have a collection for each.

    What I would denormalize is to put the song information into the Play document and into the Like document so you can render the playlist and the likes for any user without having to do any ‘joins’ back to the Song collection.

    Song: Id, Artist, Title
    Play: SongId, Time (when was the song played), Artist, Title
    Like: SongId, UserName, Time (when did the user click the like button), Artist, Title, UserId

    • 0