Show HN: Kvpbase – a new way for developers to store data
kvpbase.tumblr.com
kvpbase.tumblr.com
callback(err, data)
while you suggest doing it like this: callback(data, err)
Apart from being an eyesore, it breaks compatibility with a ton of third-party libs like `caolan/async`.World's Only always screams snake oil to me. Maybe I am being picky but I hate huge statements that are unnecessary and probably untrue.
"HidrateMe, a smart water bottle that syncs to your phone"
and next to it
"Trago - The world's first connected smart water bottle"
They basically pay for one full time developer and it really has worked this last year.
Isn't that exactly what "every database ever" calls triggers?
From the Postgres docs: http://www.postgresql.org/docs/9.4/static/trigger-definition...
> A trigger is a specification that the database should automatically execute a particular function whenever a certain type of operation is performed. Triggers can be attached to tables, views, and foreign tables.
Even NoSQL DB's like redis or riak have the ability to execute user-supplied Lua resp. Erlang.
http://docs.basho.com/riak/latest/dev/advanced/commit-hooks/
Here are a few scalable open source block/object storage systems:
Lustre
Ceph
tahoe-lafs
XtreemFS
These are all opensource.
For example, if I wanted a fast global-coherent CDN, then all I need are webservers and GPFS, with some glue code to allow auth'd uploads/deletes. geographically scalable, with tiered storage levels.
If you want to run on dodgy hardware, then use XtreemFS. but you'll pay a performance price.
I'd be interested in a comparison in developer language(as in graphs code examples etc.), with a github link or similar.