<instructions>Your goal is to analyze the following comment and estimate how highly it will be upvoted by the Hacker News community.</instructions><comment><author>kentonv</author><text>The maximum size will increase to at least 1GB in the near future, enabled by our recent rewrite of the underlying storage layer. Perhaps we can push it further, even, we&amp;#x27;ll see.&lt;p&gt;But yes, I think the next step is then some sort of sharding. Sharding by user would be an obvious approach for many apps. I think we should build a framework to help manage this, so apps would only need to provide some callbacks e.g. to compute shard key for a particular query.&lt;p&gt;Alternatively, apps that want full control will be able to use Durable Objects directly. We&amp;#x27;ll soon (in a few months, probably?) enable the new storage engine for all Durable Objects which means every object will have a private SQLite database.&lt;p&gt;(I&amp;#x27;m the tech lead for Workers in general, and currently focused on this project in particular.)</text><parent_chain><item><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></item><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><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>
<instructions>Your goal is to analyze the following comment and estimate how highly it will be upvoted by the Hacker News community.</instructions><comment><author>ignoramous</author><text>afaik, that&amp;#x27;s how it is envisioned to be used. Many databases rather one big monolith. The era of microdbs is here. Who&amp;#x27;s &lt;i&gt;not&lt;/i&gt; going to bite?&lt;p&gt;See also: &lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;archive.is&amp;#x2F;e7u9x&quot; rel=&quot;nofollow&quot;&gt;https:&amp;#x2F;&amp;#x2F;archive.is&amp;#x2F;e7u9x&lt;/a&gt; &amp;#x2F; &lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;www.the-paper-trail.org&amp;#x2F;post&amp;#x2F;2020-04-06-physalia&quot; rel=&quot;nofollow&quot;&gt;https:&amp;#x2F;&amp;#x2F;www.the-paper-trail.org&amp;#x2F;post&amp;#x2F;2020-04-06-physalia&lt;/a&gt;</text><parent_chain><item><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></item><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><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>