Poor Man's Firebase: LevelDB, REST, and WebSockets

http://procbits.com/2014/01/06/poor-mans-firebase-leveldb-rest-and-websockets

by jonpaul • 13 years ago

89 24 13 years ago

procbits.com

octernion2• 13 years ago

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!

rgbrgb• 13 years ago

I think they're not that popular because the potential revenue lift for implementing the features you listed does not seem significant.

octernion2• 13 years ago

Absolutely true! The geek in me sees a sort of halo effect of having those king of features, though, in how much I appreciate a project; I'm sure that's not as easily quantifiable.

nateabele3• 13 years ago

(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. :-)

saraid216• 13 years ago

It seems to be a personal project. Since there aren't any meaningful consequences for writing a bug-ridden, unsupported app, it's way more valuable to reinvent the wheel than to become an expert in someone else's work.

nateabele3• 13 years ago

I know, I'm not saying he's a bad person, I'm just poking a little fun at the mentality that leads to wheel-reinvention as the first and only conclusion.

I still think it's a cool project.

javajosh• 13 years ago

Well, it might also have something to do with money or control, as Firebase is SaaS, and this solution is open source software.

https://www.firebase.com/pricing.html

jaytaylor2• 13 years ago

As an aside, what happens with FireBase when you need more than 30GB of storage in a single app?

yeleti4• 13 years ago

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.

yeleti4• 13 years ago

Just to clarify things a bit; our setup worked fine. The only reason we switched to Firebase was, being a small team, we didnt want to maintain all those servers.

ing33k• 13 years ago

Sounds cool, have you thought about open sourcing what you have buid?

nicklovescode• 13 years ago

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)

yeleti4• 13 years ago

Poor Man's Firebase: LevelDB, REST, and WebSockets

Related Stories