Live data from Hacker News

FoundationDB 6.0 released, featuring multi-region support

foundationdb.org

51–60 of 72 posts

Re: FoundationDB 6.0 released, featuring multi-region support

#52
post #4

To anyone who is on the fence about putting FoundationDB into production (or at least evaluating it for their use cases), what is the number one thing you think is missing or you're worried about? i.e. - a SQL interface, - pre-packaged data structure libraries, - monitoring, - limitations of FoundationDB itself, - etc. I'm working on a talk for the upcoming FoundationDB Summit and I'd love to address some real-world…

- Secondary Index

- some way to store ordered records to speed up range query

- comparison & benchmarks of FoundationDB vs other distributed DB like TiDB, CockroachDB, ScyllaDB, etc

Re: FoundationDB 6.0 released, featuring multi-region support

#53
post #4

To anyone who is on the fence about putting FoundationDB into production (or at least evaluating it for their use cases), what is the number one thing you think is missing or you're worried about? i.e. - a SQL interface, - pre-packaged data structure libraries, - monitoring, - limitations of FoundationDB itself, - etc. I'm working on a talk for the upcoming FoundationDB Summit and I'd love to address some real-world…

- Secondary Index - some way to store ordered records to speed up range query - comparison & benchmarks of FoundationDB vs other distributed DB like TiDB, CockroachDB, ScyllaDB, etc

Those first two are pretty trivial. Keys are already stored in sorted order in a b-tree. Secondary indexing involves putting the indexed value to the left of the primary key in the key you write.

Re: FoundationDB 6.0 released, featuring multi-region support

#55

How does FDB compare to Spanner as far as the Consistency model and trade offs?

FoundationDB and Spanner both offer external consistency. Spanner does this through synchronized clocks. FoundationDB has a similar clock called TimeKeeper, which is not a clock per se but a counter which advances approximately 1M times per second. Transactions are ordered based on this timestamp.

Re: FoundationDB 6.0 released, featuring multi-region support

#56

Earlier quoted context omitted.

- Secondary Index - some way to store ordered records to speed up range query - comparison & benchmarks of FoundationDB vs other distributed DB like TiDB, CockroachDB, ScyllaDB, etc

Those first two are pretty trivial. Keys are already stored in sorted order in a b-tree. Secondary indexing involves putting the indexed value to the left of the primary key in the key you write.

> Keys are already stored in sorted order in a b-tree

I thought FoundationDB stored data in a hash table. Didn't realize it uses a b-tree. Thanks for the clarification.

> Secondary indexing involves putting the indexed value to the left of the primary key in the key you write

By secondary index I meant having a sort order that's different from the primary key sort order.

Re: FoundationDB 6.0 released, featuring multi-region support

#57

Congrats to the team on the release. Using FoundationDB has been one of the most rock solid NoSQL experiences I've ever had, and I've used a lot. After having a few months to hammer my cluster with fairly low level atomic operations, I can confidently say this thing holds up to pretty much anything you want to throw at it. Coming from the land of HBase and DynamoDB, It's ability to automatically (and intelligently) r…

Any chance of writing up a case study in detail to share your experience and best practice, especially the comparison with other DBs?

Re: FoundationDB 6.0 released, featuring multi-region support

#59
post #32

Earlier quoted context omitted.

100ms+! Ouch. Is that just large amounts of data? Are you guys using pg.native?

No, this is just say a list of messages, not that much of data. We tried to move to pg-native, but it didn't help. Problem was in Sequelize. But in my internal tests even Sequelize was the fastest library on the market.

Looks like you’re blaming Postgres for Something that sounds like Sequelize’s fault. You should try prototyping parts of your application in a language that is better supported. Last I used Sequelize I was disappointed at how poorly it fared compared to other libraries like Django ORM or SQLAlchemy.

Re: FoundationDB 6.0 released, featuring multi-region support

#60

Congrats to the team on the release. Using FoundationDB has been one of the most rock solid NoSQL experiences I've ever had, and I've used a lot. After having a few months to hammer my cluster with fairly low level atomic operations, I can confidently say this thing holds up to pretty much anything you want to throw at it. Coming from the land of HBase and DynamoDB, It's ability to automatically (and intelligently) r…

Could you add some details about your scale?
Post reply on HN