Live data from Hacker News

FoundationDB Document Layer

foundationdb.org

21–30 of 36 posts

Re: FoundationDB Document Layer

#21

Is there any reason to expect fundamental inefficiencies with this approach vs a vertically integrated approach like a conventional document store? Any other downsides? I ask because this seems like to obviously good an idea to be true, so I need to look for the flip side before I get to excited. Otherwise, this laying seems like the obvious approach, and I can only lament that it's taken this long.

Haven't dug in, but depends on if there's a system in place to support multiple indexes on your documents and how the system uses them. This could be a relatively small or huge impact depending on your interface requirements, sorting etc.

Re: FoundationDB Document Layer

#22
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.

Well that’s just a ridiculously uninformed statement. Of course mongodb scales horizontally. I can share many success stories of massive scale with mongodb.

Re: FoundationDB Document Layer

#23

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…

That talk was glorious. "We want to build a database, but first we need to build a simulator for the database, but first we need to write a compiler to help us write the simulator." It would be self-parodying engineering hubris if it hadn't worked.

Re: FoundationDB Document Layer

#24

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.

It's all open-source and out there now though, so I don't think you really need to trust them, right?

Re: FoundationDB Document Layer

#28

Can someone write a Google Datastore layer so that I can finish my appengine/datastore adventure once and for all?

well there is https://github.com/AppScale/appscale which probably has some kind of layer on top of cassandra that will emulate it.

but it's a really big project... (But you can run just the Datastore: https://github.com/AppScale/appscale/tree/master/AppDB)

Re: FoundationDB Document Layer

#29
Sounds kind of "old" tech to have different layers for supporting different data models. Like the native multi-model approach of ArangoDB much better.

Their aggregation framework is pretty neat and the database also has full graph capabilities. Heck, I can even combine joins and graph traversal in the same query.

Re: FoundationDB Document Layer

#30
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.

It's like hard slap straight in the face. They changed license because they perceived that multibilion giant(s) feasts and earn money upon their work and gives back not that much. In return giant just slaps
Post reply on HN