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

31–36 of 36 posts

Re: FoundationDB Document Layer

#31

Post by brazzledazzle »

pxtail wrote: post #30
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.

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

I’ll never understand why we collectively wag our fingers at individuals or companies that try to keep the likes of Amazon from building a profitable service off of their hard work then contribute back little-to-nothing. Would redis, mongodb and dgraph have even considered alternate licensing if companies like Amazon had thrown them a minuscule amount of funding and patches? We can’t know because they didn’t. And then we sneer at them for having the audacity to try to stay open but stop these giants from using them and throwing them away.

Re: FoundationDB Document Layer

#32

Post by mikece »

I'm a little confused. Does the "layers" concept mean the data which is stored in the core can be accessed in any valid manner that the layers allow? Or stated differently: if I've got a dumpster fire of data in a MongoDB that should have been in an RDBMS but moving to SQL would be too risky/slow would this allow me to schlep my Mongo data to FoundationDB and have the app continue to use the Mongo access methods while I start switching APIs over to querying by SQL in batches instead of One Big Volatile Move?

Re: FoundationDB Document Layer

#33

Post by sigstoat »

mikece wrote: post #32

I'm a little confused. Does the "layers" concept mean the data which is stored in the core can be accessed in any valid manner that the layers allow? Or stated differently: if I've got a dumpster fire of data in a MongoDB that should have been in an RDBMS but moving to SQL would be too risky/slow would this allow me to schlep my Mongo data to FoundationDB and have the app continue to use the Mongo access methods whil…

foundationdb is just a KV store that doesn't even authenticate clients connecting to it. the idea is you put layers in front of it to take nice structured requests (of some sort) and turn them into transactional KV manipulations, while also doing things like authentication, access control, logging, whatever else you need.

so you could (hypothetically, if such software existed), have this mongo layer, and then another layer off to the side which took SQL queries, and figured out how to turn them into KV queries against the data that the mongo layer has stored.

more realistically, you could have your SQL clients know how to talk to foundationdb directly (making them into the layer; presumably they're a web backend or something already), and they could know how to execute the high level operation they want to perform against the KV data stored by the mongo layer. conveniently skipping all of the SQL translation that there isn't software for.

Re: FoundationDB Document Layer

#34

Post by thefounder »

wsh91 wrote: post #27
thefounder wrote: post #25

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

Is there anything we could be doing to serve you better?

Yes, let me run datastore on my servers. Surely I may use your cloud offer but in certain cases I need to run it on my servers. I can't build/invest in tools/drivers for a proprietary cloud service.

Re: FoundationDB Document Layer

#35

Post by thefounder »

merb wrote: post #28
thefounder wrote: post #25

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 )

I already tried it...it looks good on paper but bad in practice. Think of a graveyard where appengine go.

Re: FoundationDB Document Layer

#36

Post by thefounder »

rckclmbr wrote: post #26
thefounder wrote: post #25

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

Be the change you want to see

I think it's not worth it. I rather not use Datastore for anything from now on. You have to cut your losses at some point. We are using microservices so it's not hard to make the change(though we loose some tools we designed for datastore).
Post reply on HN