Spotify Optimized the Largest Dataflow Job Ever for Wrapped 2020
engineering.atspotify.com
Spotify Optimized the Largest Dataflow Job Ever for Wrapped 2020
1–10 of 135 posts
Re: Spotify Optimized the Largest Dataflow Job Ever for Wrapped 2020
#2If I am reading things correctly with Kafka the workflow equivalent to what's written in the article would be to have your producer produce via hash-based-round-robin (the default partitioning algorithm) based on the key you are interested in into some topic and then your consumer would just read it and your data would already be sorted for the given keys (because within a partition Kafka has sorting guarantees) and also be co-partitioned correctly if you need to read some other topic in with the same number of partitions and the same logical keys produced via the same algorithm. No?
Re: Spotify Optimized the Largest Dataflow Job Ever for Wrapped 2020
#3Re: Spotify Optimized the Largest Dataflow Job Ever for Wrapped 2020
#4Yet, I, as a user still cannot see my playcounts via app or API.
Re: Spotify Optimized the Largest Dataflow Job Ever for Wrapped 2020
#5Re: Spotify Optimized the Largest Dataflow Job Ever for Wrapped 2020
#6Yet, I, as a user still cannot see my playcounts via app or API.
Re: Spotify Optimized the Largest Dataflow Job Ever for Wrapped 2020
#7Yet, I, as a user still cannot see my playcounts via app or API.
Re: Spotify Optimized the Largest Dataflow Job Ever for Wrapped 2020
#8I miss being able to do something simple like listen to music or watch a movie without all my actions being recorded and saved. So I'm back to buying physical media and DRM free downloads.
I'm convinced that it is now important to hold on to older appliances that work without internet access or data collection this plus right to repair gives me hope for the future.
Re: Spotify Optimized the Largest Dataflow Job Ever for Wrapped 2020
#9Yet, I, as a user still cannot see my playcounts via app or API.