northstar702

11 ms·

61.
Show HN: Aggregate Functions in FaunaDB(fauna.com)
1 points by northstar702 7y ago|1 comments
62.
by northstar702 7y ago
One hopes that GraphQL abstractions will enable the decoupling. So if you opt for a database that offers GraphQL natively, it might address the issue. You do have to learn the GraphQL ecosystem (new tools/language etc.)
63.
Show HN: Stateful Serverless Apps Using FaunaDB with Next.js on ZEIT(zeit.co)
6 points by northstar702 7y ago|1 comments
64.
Comparing Distributed SQL Performance – Yugabyte/ Amazon Aurora / CockroachDB(blog.yugabyte.com)
10 points by northstar702 7y ago|0 comments
65.
Show HN: Announcing the FaunaDB Add-On for Netlify(netlify.com)
49 points by northstar702 7y ago|19 comments
66.
Show HN: FaunaDB Add-On for Netlify Platform(docs.fauna.com)
1 points by northstar702 7y ago|0 comments
67.
Trend-Spotting with Stackoverflow and GitHub(fauna.com)
1 points by northstar702 7y ago|0 comments
68.
Remote Joins with Hasura and FaunaDB(blog.hasura.io)
2 points by northstar702 7y ago|0 comments
69.
by northstar702 7y ago
Is there any scenario where you wouldn't want to use a serverless db? Makes me wonder why any db shouldn't be serverless in this data and age for the benefits that you mention.
70.
Question: What factors are contributing to the growing interest in GraphQL?
4 points by northstar702 7y ago|1 comments
71.
by northstar702 8y ago
Would you give some more insight into your opinion? What latency/performance are you targeting -- have you tried using a system like this to arrive at your conclusion?
72.
by northstar702 8y ago
Scala/Java
73.
by northstar702 8y ago
Thanks, we appreciate the shoutout.