How FoundationDB works and why it works

Re:How FoundationDB works and why it works by rapsey on Monday September 18, 2023 @02:58AM (#37553126)

FoundationDB replaces MySQL/PostgreSQL (if the tradeoffs are acceptable) or Cassandra. It is a reliable distributed store.

Unless you are running Redis only with nothing else, fdb and redis do not play in the same space.

[ Parent | on HN ]

Re:How FoundationDB works and why it works by diogenes4 on Monday September 18, 2023 @03:00AM (#37553141)

> FoundationDB replaces MySQL/PostgreSQL

Only in terms of transactions across multiple data centers. In every other way vertically scaler sql performs better, especially for your dollar.

[ Parent | on HN ]

Re:How FoundationDB works and why it works by rapsey on Monday September 18, 2023 @03:04AM (#37553166)

Performance is not the only metric. High availability (i.e. no single point of failure) with strong consistency are very important for some.

[ Parent | on HN ]

Re:How FoundationDB works and why it works by diogenes4 on Monday September 18, 2023 @03:05AM (#37553171)

Is availability not an aspect of performance?

But of course, hence why i referenced multidc transactions.

[ Parent | on HN ]

Re:How FoundationDB works and why it works by rapsey on Monday September 18, 2023 @03:11AM (#37553220)

> Is availability not an aspect of performance?

Not to my understanding. Can you elaborate?

[ Parent | on HN ]

Re:How FoundationDB works and why it works by diogenes4 on Tuesday September 19, 2023 @04:49PM (#37576345)

Well, an unavailable service has trivially (perfectly) bad performance. I'm not sure how you'd conceive of performance to exclude availability, or what that conception would give us.

[ Parent | on HN ]

Re:How FoundationDB works and why it works by riku_iki on Monday September 18, 2023 @02:24PM (#37559984)

> FoundationDB replaces Cassandra

I think they have different use cases: fdb when you want transactions, cassandra when you want throughput.

[ Parent | on HN ]