Poor Man's Firebase: LevelDB, REST, and WebSockets (opens in new tab)

> (As an aside, it seems that it would work most of the time in most of environments that I'd try, but for some reason, it rarely worked in one). So I needed to find a new solution.

'Instead of debugging the one environment, I'll just reimplement the entire service!'

Obviously. :-)

This is quite nice.

Before we (https://www.tesla.im) switched to Firebase we had (still have) our own realtime system built with NodeJS, Websockets, Amazon SQS (as backup to ensure messages don't get lost) and a RIAK cluster.

I don't want to sound negative towards you project, but why not use CouchDB [0], along with TouchDB [1] for mobiles and PouchDB [2] for the browser ?

[0] https://couchdb.apache.org/

[1] http://touchdb.org/

[2] http://pouchdb.com/

Pretty cool project! I remember the pleasure I got out of (partially) re-implementing the Pusher API.

I wonder why real-time features aren't more popular? Real-time order status, live-updating maps, the list goes on!

Would love if someone produced a decent open source firebase-clone with turn-key angularfire integration. I really want to use it, but some of my clients are not OK with having data stored on someone else's server(rationally or not)

I built an npm module with a very similar goal - an open source alternative to FireBase. It's open source at https://npmjs.org/package/waferdb

i always thought that firebase should be easy to replicate with some node + express REST + websockets + client code if you plan on doing a bigger longterm project with sensitive data. For smaller projects (experiments, campaign related stuff) firebase should be fine.