TE
TechEcho
Home24h TopNewestBestAskShowJobs
GitHubTwitter
Home

TechEcho

A tech news platform built with Next.js, providing global tech news and discussions.

GitHubTwitter

Home

HomeNewestBestAskShowJobs

Resources

HackerNews APIOriginal HackerNewsNext.js

© 2025 TechEcho. All rights reserved.

Real World Database Latency

42 pointsby evanweaverover 3 years ago

3 comments

aeyesover 3 years ago
What&#x27;s going on with the latency for the US region on the status page? <a href="https:&#x2F;&#x2F;status.fauna.com&#x2F;#day" rel="nofollow">https:&#x2F;&#x2F;status.fauna.com&#x2F;#day</a><p>1 second for writes and 400ms for reads? Looks like this has been going on for a week but there is nothing posted about it on the status page.
评论 #28623180 未加载
evanweaverover 3 years ago
&quot;There are three kinds of lies: lies, damned lies, and benchmarks.&quot; - Mark Twain<p>What other methods does the community use for measuring distributed latency?
评论 #28609184 未加载
评论 #28610492 未加载
tysontover 3 years ago
To add a bit of color from the author, the content in the article was informed by my experience building distributed systems at Microsoft, Amazon, and Riot Games. At Riot we sharded our playerbase for a number of reasons (including complexity of matchmaking), but we may have chosen a different approach if we had a service like Fauna that could push data closer to players at the edge. With centralized relational databases, cross-region calls to load account info, entitlements, etc. would have been a very jarring experience in the client.<p>I&#x27;ve seen a number of database companies publish blog posts and put out tweets offering a competing point of view: that single-region is enough and multi-region doesn&#x27;t matter. Would love to engage with that crowd here and get their perspective on the content in the blog post.
评论 #28612714 未加载