Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
voidmain
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
21 ms
·
241.
▲
by
voidmain
8y ago
Yes, it's really serializable isolation. The real kind, not the "doesn't exhibit any of the named anomalies in the ANSI spec" kind. We can selectively relax isolation (to snapshot) on a per-read basis (by just not crea
242.
▲
by
voidmain
8y ago
Well, it's infrastucture. Moreover, it's infrastructure for infrastructure! So if that sounds super boring you don't have to be excited :-) But I would tell the story something like this: state storage is the root of (almos
243.
▲
by
voidmain
8y ago
No, it's always been possible to have as little as one fdbserver process and have a complete key/value store. Internally it is "microservices" though - it will start a "proxy", a "resolver", a "
244.
▲
by
voidmain
8y ago
It's more like you would build a better Elasticsearch using Lucene to do the indexing and FoundationDB to do the storage. FoundationDB will make it fault tolerant and scalable; the other pieces will be stateless.
245.
▲
by
voidmain
8y ago
Well, if you want ACID then you are going to have to pay for at least one geographic round trip per committed transaction. (So why not go active/passive, and have at least one of your datacenters be fast?) But what if you have dif
246.
▲
by
voidmain
8y ago
Yes, conflict resolution is for most workloads a pretty small fraction of total resource use so you usually don't need a ton of resolvers (I think out of the box it still comes configured with just one?), but it can scale conflict reso
247.
▲
by
voidmain
8y ago
FoundationDB is not Byzantine fault tolerant.
248.
▲
by
voidmain
8y ago
You only have to write to the coordination state when there is a failure. You can commit millions of transactions in the happy case without ever doing such a write. And failure detector performance and other engineering concerns are usual
249.
▲
by
voidmain
8y ago
The satellite mode that I described is an active/passive mode. One region is accepting reads and writes; the other is just replicating everything. When it looks like the active region is in trouble, the asynchronous replication is &quo
250.
▲
by
voidmain
8y ago
Nitpick: To be fully live, a partition needs a majority of the coordinators and at least one replica of each piece of data (if you don't have any replicas of something unimportant, you might be able to get some work done, but if you
251.
▲
by
voidmain
8y ago
The number of coordinators is separate from the number of boxes. You don't have to have a coordinator on every box. I think you can set the number of coordinators to be even, but you never should - the fault tolerance will be strictly
252.
▲
by
voidmain
8y ago
It's somewhat hard to answer your questions because the architecture (and hence, terminology) of FoundationDB is a little different than I think you are used to. But I will give it a shot. FoundationDB uses optimistic concurrency, so
253.
▲
by
voidmain
8y ago
FoundationDB stores 2N+1 copies of some "coordination state" and does a consensus algorithm whenever it is updated. But this state doesn't contain a copy of your data; basically think of it as storing a replication configurat
254.
▲
by
voidmain
8y ago
I think it's just saying that it's willing to place two of the three replicas in a datacenter, for example if one of the three datacenters is down. This has downsides, since losing a datacenter will make it aggressively fill up
255.
▲
by
voidmain
8y ago
I saw @spullara do pretty neat stuff with our log files in Wavefront. Will you guys think about open sourcing tooling? Apple is realistically never going to do that stuff.
256.
▲
by
voidmain
8y ago
It is serializable and totally uncompromising. Philosophically pretty much everything defaults to the safest possible thing. It can't tolerate N failures from N+1 nodes . It can tolerate N failures with N+1 copies of your data . In
257.
▲
by
voidmain
8y ago
The fault tolerance is pretty much flawless. You won't be able to get the database "stuck" or see anomalies. But performance is going to suck if you run server nodes over unreliable connections. I have trouble seeing a Found
258.
▲
by
voidmain
8y ago
HBase and Cassandra both provide much weaker guarantees. At best they can support compare-and-set operations that are local to a single region/"row", whereas FoundationDB lets you do optimistic transactions (and consistent re
259.
▲
by
voidmain
8y ago
I think Citus is not really ACID. Spanner (and to an extent its less mature OSS descendants Cockroach and TiKV) has more comparable goals, but is fairly different architecturally. For example, FoundationDB only requires N+1 replicas instead
260.
▲
by
voidmain
8y ago
The storage engine is and always was a fairly heavily modified asynchronous version of sqlite's btree. It's been extremely reliable, which was always our top priority, and the performance isn't bad. But honestly when there w
261.
▲
by
voidmain
8y ago
I'll try to give you a quick introduction. The architecture talk I recorded for new engineers working on the product ran to four or five hours, I think :-). In short, it is serializable optimistic MVCC concurrency. A FDB transaction ro
262.
▲
by
voidmain
8y ago
The client is complex and needs very sophisticated testing, so there is only one implementation. All the language bindings use the C library.
263.
▲
by
voidmain
8y ago
Hey, we should get lunch some time!
264.
▲
by
voidmain
8y ago
Your wish is granted! https://news.ycombinator.com/item?id=16877395
265.
▲
by
voidmain
8y ago
Will said what I wanted to say, but: me too. I'm super happy about this and grateful to the team that made it happen! (I was one of the co-founders of FoundationDB-the-company and was the architect of the product for a long time. Now
266.
▲
by
voidmain
8y ago
We used Zulip (then a commercial product) at FoundationDB, and really liked it. We had teams in two cities. The threading, which they sell as the core feature, is nice, and does make it more usable for "important" conversations t
267.
▲
by
voidmain
8y ago
I doubt a lack of "new computers" is the problem, but https://directpay.irs.gov/directpay/payment currently reads: Direct Pay This service is temporarily unavailable. We are working to resolve the issue. Plea
268.
▲
by
voidmain
8y ago
Yeah, this is basically a variation of the POTAXOR strategy [1]. Well, whatever it takes to get it into the hands of sick people! But I think it is a commentary on the system that it will take decades after we had good evidence for keta
269.
▲
by
voidmain
9y ago
Hoping that governments are going to outlaw surveillance, when they are the biggest practitioners and customers of surveillance, seems... optimistic.
270.
▲
by
voidmain
9y ago
The best thing to come out of Mars One is the satirical ad campaign by the state of South Dakota. "Why die on Mars when you can live in South Dakota?" [1] http://money.cnn.com/2015/04/21/news/ec
More ›