databrecht

6 ms·

1.
by databrecht 3mo ago
It's just insane how different experiences are. I've let it spin for 2 days on difficult tasks for my job, it found very complex esoteric race condition bugs which were genuinenly the type of "will take you 5 days to figer ou
2.
by databrecht 5y ago
There is value in both, at Fauna we provide GraphQL out the box. Using Fauna directly would eliminate an indirection and is probably slightly more efficient. However, if there is a GraphQL layer like Prisma in between you could essentially
3.
by databrecht 5y ago
Which should be the case, depending on what you do you will probably experience 10-50ms read latencies. Look for Evan's answers why the measured values here are higher.
4.
by databrecht 5y ago
No it's not, that price is far far smaller and should not impact pure reads. This is probably an artifact of an anti-pattern where the same documents are constantly updated which creates significant history. At this point, that can hav
5.
by databrecht 5y ago
Region selection is coming up if that interests you. We are actively working on it :)
6.
by databrecht 6y ago
Exactly! That's how I've built until now, a mix of databases. But it's also harder to manage. Database vendors notice this and that results in databases that start offering alternative ways of modeling.
7.
by databrecht 6y ago
Freeform flexibility is one aspect, but a document-style could also simply be a preference for how you want to structure your data or typically has an impact on how joins happen (if the document-database offers joins). Those joins will work
8.
by databrecht 6y ago
'NoSQL' can be transactional and relational. The question should always be: "this is my problem, what's the best database?". NoSQL is such a huge bucket that the original question doesn't make sense imo. So is
9.
by databrecht 6y ago
I would go a step further, you can't even talk about NoSQL vs SQL. It's about database features, the join patterns, how scaling happens, both are overlapping more and more and will continue to overlap more. Products built on SQL a
10.
by databrecht 6y ago
Exactly, but it goes further than that. The mentality never made sense since the term NoSQL never made sense to start. It's amazing how many people use a term that just originated from a meeting to talk about alternative databases. How
11.
by databrecht 6y ago
Social media are typically quite heavy on tree traversals. That kind of pattern is very similar to trying to resolve a deep ORM query or a deep GraphQL query which also doesn't map very well on 'traditional' relational databa
12.
by databrecht 6y ago
Easy searching is definitely in our roadmap but for people who might pass by I did want to point out that you can already get some form of text search due to the way we index arrays. You can easily write a sort of 'inverted index'
13.
by databrecht 6y ago
If I'm not mistaking, Dynamo's streaming is pulling under the hood. I suppose it depends on how frequently it pulls how quickly the price goes up and how expensive such a pull is in reads. In Fauna we have temporality as a first-c
14.
by databrecht 6y ago
> Why do this? One possibility is that the ways that Fauna actually is better than DynamoDB are too subtle to get anyone's attention. They're real and useful, but not ridiculous. The people who actually use DynamoDB at massive
15.
by databrecht 6y ago
At the bottom of this page you can see the regions (and future regions) https://fauna.com/features . Since Fauna is inspired by Calvin we are not dependent on clocks like Spanner to deliver global consistency and can run on
16.
by databrecht 6y ago
It's at the same time miss-education through over-simplification IMHO although it was never intended like that. Availability is never 100% so everything is far more subtle. I'd prefer that teaching would focus on resolution strate
17.
by databrecht 6y ago
It also doesn't really overcome CAP. As far as I understood, it just comes so close that people perceive it as a CAP system but technically it's still a CP system. Which can also be achieved without atomic clocks though nowadays:
18.
by databrecht 6y ago
Assuming something in the same vein as fizx with the addition that it's probably very similar to what Join Monster tries to solve: https://github.com/join-monster/join-monster
19.
by databrecht 6y ago
I'm wondering how FaunaDB's GraphqL would suit you? It's basically: "drop in schema, get API". You can't do everything that you'll ever need yet but you can go quite far and the implementation of each quer
20.
by databrecht 6y ago
Thanks, that's valuable feedback :) We indeed are currently providing a lot of building blocks that can solve a wide range of scenarios but did not focus too much yet (until now) on providing easy out-of-the-box combinations of those b
21.
by databrecht 6y ago
Did you check FaunaDB by any chance? I'm wondering whether their ABAC systems + UDFs would satisfy your needs.
22.
by databrecht 6y ago
I wonder, given your experience, did you ever try FaunaDB? It grew from the not optimal experience when scaling databases like Cassandra etc @ Twitter. Consistent + relational + multi-region.
23.
by databrecht 6y ago
Tbh I don't think that makes sense since it depends on what your definition of NoSQL is. Some people say 'no relations' others say 'no sql' others say 'eventual consistency'. Some people call FaunaDB NoSQL
24.
by databrecht 6y ago
Good to know in that case, that you can create as many databases as you want in one FaunaDB account and even create databases in databases (parent keys get access to child databases) and probably won't get these issues. e.g. I run inte
25.
by databrecht 7y ago
It makes less sense to categorize them as NoSQL. It implicitly means 'eventual consistency' and 'no relations' depending on who you ask. Some of the 'NoSQL' databases offer some consistency features, other dist
26.
by databrecht 7y ago
Interesting, you might want to check out FaunaDB if you like the Serverless idea. Disclaimer: I work there but stumbled on your article after my hours.
27.
by databrecht 7y ago
> So in reality I think the only really scalable part here is the database. And scalability in databases has no universal solution and the ones that exists come with the load of caveats. I do wonder what limitations and caveats you are t
28.
by databrecht 7y ago
Exactly!! I still think that people do not think enough about the cost of NOT scaling nowadays. And especially, what is it going to cost when I can't scale and I have to change course. I recently heard a podcast where they said: "
29.
by databrecht 7y ago
Did you try FaunaDB by any chance? I'm interested in how people who have worked with DynamoDB and Firestore would perceive FaunaDB once they get started. Imho it's is the most serverless database on the market at this point due to
30.
by databrecht 7y ago
Are you looking for something inside IBM cloud? If not, FaunaDB might be interesting? It's a serverless database, pay as you go (with free tier), security layer for client to DB connections, strongly consistent, scalable and distribute

More ›