ededddy/spotifyrecords

A Practice Console App to store Spotify Currently Playback into MongoDB

.NET 6 Console Application

Requirements

• NET 6
• Rider / Visual Studio / dotnet-cli
• Kafka Instance
• MongoDB

To Run

1. Setup your Kafka instance
2. Setup MongoDB (Create SpotifyRecord database and CurrentlyPlayingRecords collection)
3. Setup 2 config.json
4. Build and Run

NOTE: You may need to start playing on spotify in order to get record back.

Sample Configs

1. Consumer config

{
  "MongoDB": {
    "connectionString": "mongodb://localhost:27017"
  },
  "Kafka": {
    "BootStrapServers": "PLAINTEXT://172.28.63.150:9092,PLAINTEXT://172.28.63.150:9093,PLAINTEXT://172.28.63.150:9094"
  }
}

2. Producer config

{
  "Spotify": {
    "CLIENT_ID": "<Spotify_APP_Client_ID>"
  },
  "Kafka": {
    "BootStrapServers": "PLAINTEXT://172.28.63.150:9092,PLAINTEXT://172.28.63.150:9093,PLAINTEXT://172.28.63.150:9094"
  }
}

spotifyrecords's Issues

MongoDB duplicated Key

The consumer currently does not have a way to distinguish received message from Kafka is duplicated playing track or not.
Probably need to use a HashSet / Set to do book keeping.
May also need to implement buffer & bulk write to Mongo.

Get Currently Playing Could be null

1. Get Current Playback State
   https://developer.spotify.com/documentation/web-api/reference/#/operations/get-information-about-the-users-current-playback

2. Get Currently Playing Track
   https://developer.spotify.com/documentation/web-api/reference/#/operations/get-the-users-currently-playing-track

Both of them return NULL when the user did not play anything for a while.
However, if user did play something, spotify actually caches and object.