TE
科技回声
首页24小时热榜最新最佳问答展示工作
GitHubTwitter
首页

科技回声

基于 Next.js 构建的科技新闻平台,提供全球科技新闻和讨论内容。

GitHubTwitter

首页

首页最新最佳问答展示工作

资源链接

HackerNews API原版 HackerNewsNext.js

© 2025 科技回声. 版权所有。

Gun – “Self-hosted Firebase”

66 点作者 pimpl将近 10 年前

7 条评论

rubiquity将近 10 年前
&gt; <i>Because gun is not a database (NoDB), it is a persisted distributed cache. The fatal flaw with databases is that they assume some centralized authority. While this may be the case initially when you are small, it always ceases to be true when you become large enough that concurrency is unavoidable. No amount of leader election and consensus algorithms can patch this without facing an unjustified amount of complexity. Gun resolves all this by biting the bullet - it solves the hard problems first, not last. It gets data synchronization and conflict resolution right from the beginning, so it never has to rely on vulnerable leader election or consensus locking.</i><p>That&#x27;s some of the most hand-wavy drivel I&#x27;ve ever read.
评论 #10144923 未加载
评论 #10144889 未加载
Lazare将近 10 年前
Seems a <i>lot</i> like CouchDB&#x2F;PouchDB. Which makes the fact that the words &quot;couch&quot; and &quot;pouch&quot; do not appear anywhere on this page rather concerning to me, because the obvious questions I have are:<p>1. How is this better than CouchDB<p>2. How does this differ from CouchDB<p>3. Why did you not implement this on top of CouchDB<p>The lack of mention suggests the developers either have no clue what already exists, know that their solution can&#x27;t compete with existing solutions, <i>or</i> don&#x27;t really care about being better and are just having fun implementing their own system from scratch. None of those answers make me want to take a deeper look.
评论 #10146212 未加载
yid将近 10 年前
&gt; It requires zero maintenance and runs on your own infrastructure.<p>I don&#x27;t understand how these two claims are not contradictory.<p>&gt; All conflict resolution happens locally in each peer using a deterministic algorithm.<p>How exactly does this happen? Via CRDTs? Consensus? How do you handle conflicts?<p>I&#x27;m very skeptical about this sort of largely content-free copy fronting what should be a pretty complicated distributed system.
评论 #10146238 未加载
评论 #10144821 未加载
jvehent将近 10 年前
see also <a href="http:&#x2F;&#x2F;kinto.readthedocs.org&#x2F;en&#x2F;latest&#x2F;" rel="nofollow">http:&#x2F;&#x2F;kinto.readthedocs.org&#x2F;en&#x2F;latest&#x2F;</a>
评论 #10144854 未加载
hiou将近 10 年前
Also see <a href="http:&#x2F;&#x2F;hood.ie" rel="nofollow">http:&#x2F;&#x2F;hood.ie</a> for what appears to be a similar goal.
marknadal将近 10 年前
Just now noticed my project was on HN! Awesome, thanks to whoever submitted it. Will be replying to the comments now.
curiousjorge将近 10 年前
how does this not have more votes? im skeptical about the self hosted firebase claim, for instance, how would you scale this?
评论 #10144732 未加载