freels

6 ms·

1.
Behind Monty Hall's Doors: Puzzle, Debate and Answer? (1991)(nytimes.com)
1 points by freels 1y ago|0 comments
2.
Show HN: We added TypeScript-like schema enforcement to Fauna(docs.fauna.com)
1 points by freels 2y ago|0 comments
3.
by freels 3y ago
Thanks for the shoutout. At some point if you find yourself with some spare time you can check out our new FQL version. It's closer to JS in terms of syntax now, but still a small, relatively functional language.
4.
by freels 3y ago
One might say uncomfortably slow.
5.
Supercharge Your DevOps Workflow with Fauna Schema Language and GitHub Actions(fauna.com)
4 points by freels 3y ago|0 comments
6.
by freels 3y ago
The NoSQL movement overstated how important the A in CAP was. Relatively few systems need _all_ nodes to be available, compared to those that benefit from strong consistency, especially those that live primarily in datacenters/the clou
7.
by freels 3y ago
I'm clearly biased, but at least in my experience, while this is technically true, you're still dealing with XML (and now JSON) shoehorned into a tuple-based context. In other words, there is still a (lossy) translation layer, it
8.
by freels 3y ago
If your current stack is working for you, that's great. The main advantages of Fauna vs say MySQL are going to be: - Fauna is distributed and multi-region and therefore more resilient to hardware or regional outages (for example we bar
9.
by freels 3y ago
Getting the best of both worlds is what we're trying to achieve with Fauna, at least for OLTP use-cases. I'd be curious to hear what challenges with you ran into with other NoSQL databases, though.
10.
by freels 3y ago
While, making it easy (and possible in the first place) to write procedural code directly in a transaction is a core part of FQL's design, it is certainly possible to implement safe read-modify-write via FQL, it's just less effici
11.
Beyond SQL: A relational database for modern applications(fauna.com)
59 points by freels 3y ago|57 comments
12.
by freels 4y ago
They don’t bother and just use search: https://futurism.com/the-byte/gen-z-kids-file-systems
13.
by freels 6y ago
There’s no catch. No database is going to work for every use case, but we’ve built FaunaDB to be general purpose, and suitable for many of them.
14.
by freels 6y ago
Fauna, Inc. | Remote | Full-Time Opportunities | https://fauna.com/company At Fauna, we’re building the serverless database for modern apps built on JAMstack. If you want to work on systems and challenges related to serverl
15.
by freels 7y ago
Calvin has been an elegant protocol to work with in practice, and has pretty radically simplified FaunaDB's implementation of transactions compared to classic 2PC. Writes are committed in one global communication exchange, read isolati
16.
by freels 7y ago
Yes, I was not trying to imply the bugs Jepsen found haven’t been fixed. However the possibility of causal reverse is a characteristic of CRDB’s architecture, so you can still observe it in the latest version.
17.
by freels 7y ago
Isn’t that just describing reintroducing waiting out the uncertainty window in order gain back external consistency? I’m not sure that ends up being substantially different from TrueTime.
18.
by freels 7y ago
I don’t know of an article describing it offhand. The issue arises where each transaction occurs on a different node or set of nodes, and the causal link between them is external to the dbms. In this case, it’s possible for each transaction
19.
by freels 7y ago
Cockroach Labs themselves freely admit CRDB allows for causal reverse anomalies [1], and Kyle reproduced it in his Jepsen analysis [2]. HLCs don't prevent causal reverse, because they don’t guarantee message exchanges synchronously hap
20.
by freels 7y ago
As others have commented, most widely deployed DBMSs provide deadlock-free serializability. FaunaDB is a commercially available implementation of Calvin that makes deadlock free serializable transactions performant in a global environment.
21.
by freels 7y ago
This advice is highly implementation specific and unnecessarily dangerous. For read only transactions, a well designed system will be able to provide SNAPSHOT isolation with little negligible perf impact compared to READ UNCOMMITTED. When c
22.
by freels 7y ago
Serializable Snapshot an implementation strategy for providing Serializable isolation. In PostgreSQL if you ask for Serializable you get SSI.
23.
Demystifying Database Systems: An Introduction to Transaction Isolation Levels(fauna.com)
202 points by freels 7y ago|22 comments
24.
by freels 7y ago
Sorry I can't let this go unchallenged. Again, you are inventing an architectural deficiency where the is none. The log in Calvin is partitioned and does not require all transactions to go through a single physical consensus leader. Th
25.
by freels 7y ago
This take on Calvin is inaccurate: Under contention, a Calvin-based system will behave similarly to others which use optimistic locking schemes for Serializable isolation such as Postgres, or YB itself. There are advantages to the Calvin ap
26.
by freels 8y ago
We are always trying to reduce the learning curve of FQL, but we've gotten a lot of good feedback from those who do take the plunge. That being said, I'd love to provide SQL support eventually, but there were a few reasons why we
27.
by freels 8y ago
It does handle contention well, we haven't emphasized that point well enough yet. Writes never contend on conflicting reads, and serialized reads never contend at all. Accurate clocks are not enough... to really get the benefits that S
28.
by freels 8y ago
No, in FaunaDB, a replica is a group of nodes, within which each node only stores a part of the dataset. One thing that's different from other systems is we make replicas a first-class operational unit to think about. The cluster topol
29.
by freels 8y ago
It's definitely recommended, depending on what you're trying to get out of the result. Happy to help out with query patterns on our community slack https://publicslack.com/slacks/fauna-community/invites&#
30.
by freels 8y ago
Just because failure can happen doesn't mean it's frequent. For the record AWS does this to protect against correlated failure. At their scale, they assume they have some percentage of local nodes down at any given time, so have d

More ›