<story><title>Why SQLite is so great for the edge</title><url>https://blog.turso.tech/why-sqlite-is-so-great-for-the-edge-ee00a3a9a55f</url></story><parent_chain><item><author>jgrahamc</author><text>This no need to compile SQLite into your Cloudflare Worker. We provide it native on our platform as D1. And it gives you replication. &lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;blog.cloudflare.com&amp;#x2F;d1-turning-it-up-to-11&amp;#x2F;&quot; rel=&quot;nofollow&quot;&gt;https:&amp;#x2F;&amp;#x2F;blog.cloudflare.com&amp;#x2F;d1-turning-it-up-to-11&amp;#x2F;&lt;/a&gt;&lt;p&gt;Also, I think the idea of “edge” doesn’t make a ton of sense. What we really need is code and data that move around as needed for the best performance. See: &lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;blog.cloudflare.com&amp;#x2F;announcing-workers-smart-placement&amp;#x2F;&quot; rel=&quot;nofollow&quot;&gt;https:&amp;#x2F;&amp;#x2F;blog.cloudflare.com&amp;#x2F;announcing-workers-smart-placeme...&lt;/a&gt;&lt;p&gt;What people call “edge” is a single optimization bringing code near the user. I think we should go far beyond that. Sure, use something like Cloudflare Workers for your “edge” needs (ie bringing your React app close to the end user&amp;#x2F;doing server side rendering). But don’t stop there because where data resides, what APIs you call are all going to matter.&lt;p&gt;That&amp;#x27;s the vision of something I called the &amp;quot;Supercloud&amp;quot;: &lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;blog.cloudflare.com&amp;#x2F;welcome-to-the-supercloud-and-developer-week-2022&amp;#x2F;&quot; rel=&quot;nofollow&quot;&gt;https:&amp;#x2F;&amp;#x2F;blog.cloudflare.com&amp;#x2F;welcome-to-the-supercloud-and-de...&lt;/a&gt;</text></item></parent_chain><comment><author>haolez</author><text>How&amp;#x27;s D1 meant to be used, since it has a very small maximum size (100mb I believe)? Should I create one database per user, for example? Genuine question.</text></comment>
<story><title>Why SQLite is so great for the edge</title><url>https://blog.turso.tech/why-sqlite-is-so-great-for-the-edge-ee00a3a9a55f</url></story><parent_chain><item><author>jgrahamc</author><text>This no need to compile SQLite into your Cloudflare Worker. We provide it native on our platform as D1. And it gives you replication. &lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;blog.cloudflare.com&amp;#x2F;d1-turning-it-up-to-11&amp;#x2F;&quot; rel=&quot;nofollow&quot;&gt;https:&amp;#x2F;&amp;#x2F;blog.cloudflare.com&amp;#x2F;d1-turning-it-up-to-11&amp;#x2F;&lt;/a&gt;&lt;p&gt;Also, I think the idea of “edge” doesn’t make a ton of sense. What we really need is code and data that move around as needed for the best performance. See: &lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;blog.cloudflare.com&amp;#x2F;announcing-workers-smart-placement&amp;#x2F;&quot; rel=&quot;nofollow&quot;&gt;https:&amp;#x2F;&amp;#x2F;blog.cloudflare.com&amp;#x2F;announcing-workers-smart-placeme...&lt;/a&gt;&lt;p&gt;What people call “edge” is a single optimization bringing code near the user. I think we should go far beyond that. Sure, use something like Cloudflare Workers for your “edge” needs (ie bringing your React app close to the end user&amp;#x2F;doing server side rendering). But don’t stop there because where data resides, what APIs you call are all going to matter.&lt;p&gt;That&amp;#x27;s the vision of something I called the &amp;quot;Supercloud&amp;quot;: &lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;blog.cloudflare.com&amp;#x2F;welcome-to-the-supercloud-and-developer-week-2022&amp;#x2F;&quot; rel=&quot;nofollow&quot;&gt;https:&amp;#x2F;&amp;#x2F;blog.cloudflare.com&amp;#x2F;welcome-to-the-supercloud-and-de...&lt;/a&gt;</text></item></parent_chain><comment><author>dgellow</author><text>Thank for sharing this, that makes lot of sense to me. The focus on running everything on edge has been confusing to me for a while due to the increased db latency. That makes so much sense to dynamically move processing to the best location in the current network instead of the binary choice “close to db”, “close to users”.</text></comment>