Poor Man's Firebase: LevelDB, REST, and WebSockets
1–10 of 27 posts
Re: Poor Man's Firebase: LevelDB, REST, and WebSockets
#2Pretty 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!
Re: Poor Man's Firebase: LevelDB, REST, and WebSockets
#3[deleted]
Re: Poor Man's Firebase: LevelDB, REST, and WebSockets
#4> (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. :-)
Re: Poor Man's Firebase: LevelDB, REST, and WebSockets
#5This 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.
Re: Poor Man's Firebase: LevelDB, REST, and WebSockets
#6> (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. :-)
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.
Re: Poor Man's Firebase: LevelDB, REST, and WebSockets
#7> (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. :-)
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.
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.
Re: Poor Man's Firebase: LevelDB, REST, and WebSockets
#8> (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. :-)
Well, it might also have something to do with money or control, as Firebase is SaaS, and this solution is open source software.
Re: Poor Man's Firebase: LevelDB, REST, and WebSockets
#9Earlier quoted context omitted.
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.
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.
I'm not sure if this is wheel reinvention, so much as wheel subset reimplementation. The latter of which is a very legitimate practice, quite frankly.
Re: Poor Man's Firebase: LevelDB, REST, and WebSockets
#10Earlier quoted context omitted.
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.
I'm not sure if this is wheel reinvention, so much as wheel subset reimplementation. The latter of which is a very legitimate practice, quite frankly.
You're right. I forgot to put my pedantry hat on before typing that comment.