Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

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

procbits.com

Post reply on HN
Print view View original

21–27 of 27 posts

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

#21

Post by octernion »

rgbrgb wrote: post #17
octernion wrote: post #2

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!

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

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.

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

#22

Post by [deleted] »

ing33k wrote: post #13
yeleti wrote: post #11

Earlier quoted context omitted.

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.

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

[deleted]

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

#23

Post by yeleti »

ing33k wrote: post #13
yeleti wrote: post #11

Earlier quoted context omitted.

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.

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

Yes we can open source it. It works pretty well. You will have to maintain these 'minimum' servers to get > 99% availability.

2 NodeJS app servers 1 Redis Master + 1 Slave 3 RIAK cluster (recommended 5)

You might want to checkout https://www.meteor.com/ as well.

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

#24

Post by yeleti »

nicklovescode wrote: post #12

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)

You might like https://www.meteor.com/

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

#25

Post by kayoone »

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.

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

#26

Post by Lazare »

jonpaul wrote: post #20
rakoo wrote: post #19

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/

There is no project... just experimentation with LevelDB. All of those solutions that you provided require an installation of CouchDB on the server side. Therefore, a bit out of scope of building a quick hacky Firebase clone using LevelDB modules.

Actually, that's not true: PouchDB runs on node (via LevelDB) and doesn't need an actual couch server. :)

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

#27

Post by rakoo »

Lazare wrote: post #26
jonpaul wrote: post #20

Earlier quoted context omitted.

There is no project... just experimentation with LevelDB. All of those solutions that you provided require an installation of CouchDB on the server side. Therefore, a bit out of scope of building a quick hacky Firebase clone using LevelDB modules.

Actually, that's not true: PouchDB runs on node (via LevelDB) and doesn't need an actual couch server. :)

I'm not sure about that. The doc [0] says that there are some static files that should be distributed by whatever HTTP server you want (they suggest python's simple http server) After that, it's all js in the browser.

Edit: I see what you mean: Pouchdb-server [1] is a couchdb-compatible server that speaks the same sync protocol. If you don't want to install it, you can work with any hosted couchdb-speaking cloud instance, such as iriscouch [2] or cloudant [3]

[0] http://pouchdb.com/getting-started.html

[1] https://github.com/nick-thompson/pouchdb-server

[2] http://www.iriscouch.com/

[3] https://cloudant.com/

Post reply on HN