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) repartition data based on write throughput has been an administrative breakthrough for me.<p>Looking forward to additional use cases I can throw at this beast of a system.<p>Kudos to you guys!
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?<p>i.e.<p>- a SQL interface,<p>- pre-packaged data structure libraries,<p>- monitoring,<p>- limitations of FoundationDB itself,<p>- etc.<p>I'm working on a talk for the upcoming FoundationDB Summit and I'd love to address some real-world questions or issues people have.
Shameless plug here, but if anyone wants to benchmark in-memory vs. NVMe NAND SSD vs. NVMe Intel Optane DC SSD performance, we're looking for someone with FoundationDB expertise to give it a shot and share their learnings with the community. Make a request for a server by posting a new issue at our Github page [1].<p>Basically, I'm curious to know how FDB's memory engine performs compared to the SSD engine with a standard NAND SSD and an Intel Optane DC SSD. Something along the lines of the throughput per core and latency results on the FDB performance page [2].<p>[1]: <a href="https://github.com/AccelerateWithOptane/lab/issues" rel="nofollow">https://github.com/AccelerateWithOptane/lab/issues</a>
[2]: <a href="https://apple.github.io/foundationdb/performance.html" rel="nofollow">https://apple.github.io/foundationdb/performance.html</a><p>Disclosure: I'm working at Intel and help manage our open source lab with our friends at Packet.
So, FoundationDB is a pretty low level distributed key-value store with transactions.<p>Most applications will need something higher level, like a SQL or document db frontend which could be built on top.<p>I'm curios what people have started using FoundationDB for.
Any interesting stories to share?
If someone want to chat about FoundationDB and want to ask about our (while limited) experience building messaging on top of FDB, please feel free to join our small room: <a href="https://app.openland.com/joinChannel/updnSlD" rel="nofollow">https://app.openland.com/joinChannel/updnSlD</a>
The upgrade instructions are firmly in the lolwut category. The database is just not available during the transition. I think they should focus on fixing their protocol such that multiple versions can run at the same time, and rollbacks are possible.