> One of the biggest impediments to double-digit-gigabyte databases is performance This line in the
One of the biggest impediments to double-digit-gigabyte databases is performanceThis line in the blog really got me thinking. I've always been using D1 with the assumption that one day this could be the primary database for the various products I'm building on Cloudflare. Reading the latest blog I somehow got the feeling that the aim is to scale D1 horizontally (aka number of databases as opposed to size of each individual database).
(Question for Matt probably) How do you envision D1 as a product? Are you aiming to build it to a point where it can be the primary database for an org? Or is D1 positioned to be on the smaller side (say up to 50GB) and powering smaller microservices in a larger architecture?

