The sqlite db is on disk sync'd down to the clients from our service.
The client is responsible for checking with our servers and, if rule updates are found, downloading a new database file. To avoid locking and contention issues, these are each uniquely named, and which DB is "current" is just updated.
Note: This is only in "managed" mode. If you'd rather, you can distribute a SQLite database of the rules alongside your app.
michaelbuckbee|1 year ago
The client is responsible for checking with our servers and, if rule updates are found, downloading a new database file. To avoid locking and contention issues, these are each uniquely named, and which DB is "current" is just updated.
Note: This is only in "managed" mode. If you'd rather, you can distribute a SQLite database of the rules alongside your app.
TheDong|1 year ago
Due to the magic of the page cache, the answer to that can be "both".
If the sqlite database is being read often and not being written, the page cache will be valid and reads will pretty much never go to the filesystme.