unless I'm missing something or something changed recently, you couldn't use Cache API to match KV's

unless I'm missing something or something changed recently, you couldn't use Cache API to match KV's new architecture, since KV 2.0 is something more close to Tiered Caching with generic + regional tier (which is Enterprise), and the Cache API doesn't interact with tiered caching at all.
KV would be faster over D1 if eventual consistency is fine/if you can have data cached for a while (and your data fits it), especially with its recent improvements.
(It would be cool if Cache API got Tiered caching one day 🙂 )
Was this page helpful?