|
|
|
|
|
|
by 0x457
837 days ago
|
|
|
Because SQLite is in process. Usually, when you start thinking about cache, you have more than one application server. Each application server running its own cache make cache invalidation a nightmare (I worked in a company where one genius did that and caused a lot of troubles). Don't show me any sqlite replication things because that's not how you want your cache to work. My issue with running PostgreSQL as cache would be its thread per connection model and downsides of MVCC for cache. |
|
|