Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

FoundationDB Document Layer

foundationdb.org

Post reply on HN
Print view View original

11–20 of 36 posts

Re: FoundationDB Document Layer

#11

Post by rubyn00bie »

Soooo stoked. This should make futzing with it to get started a lot easier.

I've been thinking about going to the FoundationDB summit to hopefully learn more... Does anyone have any good resources for learning about it? I've tried a few times but find the documentation a bit hard to grok. Maybe I'm just slow.

Also if you haven't seen it, this is one of the most amazing talks on distributed systems (because it's about testing them) I've ever seen (by Will Wilson from FoundationDB pre-Apple merger): https://www.youtube.com/watch?v=4fFDFbi3toc

Truly mind blowing how good FoundationDB is supposed to be for its use cases, and this Mongo layer is just the business when it comes to helping adoption.

Re: FoundationDB Document Layer

#12

Post by tinyvm »

> Document Layer has a familiar API, and is compatible with the MongoDB® protocol

Was wondering how I would replace MongoDB due to the shift in Licensing become more and more agressive.

Well , I think I found it.

Farewell MongoDB.

Re: FoundationDB Document Layer

#13

Post by rhacker »

I don't know much about foundationDB, but when they say API compatible, are they referring to the technical TCP/IP connection stack, or ALSO the concepts of collections and the query language of MongoDB (such as aggregations, find, limit, etc..)

In other words can I throw a giant aggregation query with all mongo's various crazy query language syntax and it will.. work the same?

Re: FoundationDB Document Layer

#14

Post by sbr464 »

rhacker wrote: post #13

I don't know much about foundationDB, but when they say API compatible, are they referring to the technical TCP/IP connection stack, or ALSO the concepts of collections and the query language of MongoDB (such as aggregations, find, limit, etc..) In other words can I throw a giant aggregation query with all mongo's various crazy query language syntax and it will.. work the same?

It doesn't support the aggregation framework currently.

Here is a list of differences:

https://foundationdb.github.io/fdb-document-layer/known-diff...

Re: FoundationDB Document Layer

#15

Post by rubyn00bie »

rhacker wrote: post #13

I don't know much about foundationDB, but when they say API compatible, are they referring to the technical TCP/IP connection stack, or ALSO the concepts of collections and the query language of MongoDB (such as aggregations, find, limit, etc..) In other words can I throw a giant aggregation query with all mongo's various crazy query language syntax and it will.. work the same?

Here's what seems to me comprehensive list:

https://foundationdb.github.io/fdb-document-layer/known-diff...

Looks like there are definitely some shortcomings, but also some wins... From the link:

> Sessions

> MongoDB® has introduced sessions in v3.6. The Document Layer doesn’t support sessions yet. Sessions in MongoDB® enable better consistency guarentees. It’s important to note that, even though the Document Layer doesn’t support sessions, it has better consistency guarentees by default due to FoundationDB backend.

Re: FoundationDB Document Layer

#16

Post by justaaron »

tinyvm wrote: post #12

> Document Layer has a familiar API, and is compatible with the MongoDB® protocol Was wondering how I would replace MongoDB due to the shift in Licensing become more and more agressive. Well , I think I found it. Farewell MongoDB.

more like a scaling issue, as mongo is master-slave and a distributed horizontally scaled world can't live with such a bottleneck.

Re: FoundationDB Document Layer

#17

Post by justaaron »

i think we are going to generally see more and more object to key-value mapping layers as the latter are widely available via cloud providers, and one basically needs something in the spirit of persistent-volume-claims from kubernetes land in the database layer that can be fulfilled by some key-value backend...

Re: FoundationDB Document Layer

#18

Post by spullara »

sbr464 wrote: post #14
rhacker wrote: post #13

I don't know much about foundationDB, but when they say API compatible, are they referring to the technical TCP/IP connection stack, or ALSO the concepts of collections and the query language of MongoDB (such as aggregations, find, limit, etc..) In other words can I throw a giant aggregation query with all mongo's various crazy query language syntax and it will.. work the same?

It doesn't support the aggregation framework currently. Here is a list of differences: https://foundationdb.github.io/fdb-document-layer/known-diff...

Can someone who uses MongoDB at scale (many machines, single db) talk about how big gap is between what FDB supports and what their application uses?

Re: FoundationDB Document Layer

#19

Post by sfilargi »

FoundationDB always sounded amazing, BUT, the way they disappeared when it was bought by Apple left a bitter taste in my mouth and I don't think I would ever trust them enough to build my business around their product.

Re: FoundationDB Document Layer

#20

Post by tracker1 »

justaaron wrote: post #16
tinyvm wrote: post #12

> Document Layer has a familiar API, and is compatible with the MongoDB® protocol Was wondering how I would replace MongoDB due to the shift in Licensing become more and more agressive. Well , I think I found it. Farewell MongoDB.

more like a scaling issue, as mongo is master-slave and a distributed horizontally scaled world can't live with such a bottleneck.

Depends on your deployment specifics and your requirements. I would say that a replica set of mongodb may be faster, but a sharded replica set in mongo may be slower than a local cluster of foundation with the document layer interface.
Post reply on HN