News for hackers. Stuff that matters.
Re:Rearchitecting: Redis to SQLite by jitl on Wednesday September 25, 2024 @11:20AM (#41648480)
We used this model to distribute translations, feature flags, configuration, search indexes, etc at Airbnb. But instead of SQLite we used Sparkey, a KV file format developed by Spotify. In early years there was a Cron job on every box that pulled that service’s thingies; then once we switched to Kubernetes we used a deamomset & host tagging (taints?) to pull a variety of thingies to each host and then ensure the services that use the thingies only ran on the hosts that had the thingies.

In Ruby we called this “hammerspace” https://github.com/airbnb/hammerspace

Re:Rearchitecting: Redis to SQLite by michaelbuckbee on Wednesday September 25, 2024 @03:31PM (#41651004)
1. Very cool

2. If you were making it today would you just use SQLite?

Re:Rearchitecting: Redis to SQLite by skevy on Wednesday September 25, 2024 @03:38PM (#41651067)
Yes, we would. And likely will switch to SQLite at some point in the future. (source, I work adjacent to these systems at Airbnb)
Re:Rearchitecting: Redis to SQLite by otterley on Thursday September 26, 2024 @04:54PM (#41663251)
In Kubernetes, pod affinities (not taints) are the typical and preferred mechanism used to ensure pods are scheduled on the same node as their dependencies.