I didn't dig deep in to the docs - just played with the demos - but if all data is exposed as 'just' a URL - what implications are there for security? Can someone mod the JS to grab someone else's data associated with my app? They probably have answers for this, but it wasn't apparent in the demos I looked at.
Hey. Yeah, we have an ACL system for specifying who can read/write data at each location. So you can lock down your application data to keep it secure. The API for this is still in flux though, so it's not documented. Coming soon though! :-)
I don't really get the benefits. You don't need servers, but you need to host the JS/html5 application somewhere, even if you don't need to configure the database server etc.
It is nice technology, but I don't really see if it is worth the price (vendor lock-in, technology lock-in, etc.)
Hosting can be handled much more efficiently / easily by someone designed just for content distribution, like a CDN. Our own site is 100% server from a CDN, which makes for very nice scaling characteristics. Also, it's free right now...
Assuming you know how to build and deploy servers; what advantages would Firebase bring over say: a Socket.IO client -> NodeJS server setup where data was being stored and fetched from memory (Redis or some other data-store)?
This could be incredibly useful for full stack developers that need to do mockups quickly, or have clients that are constantly calling them and asking questions like, "Can you build me something like $data_driven_webapp_dujour".
If your client just needs something small, you could host it on Firebase.
I also like the possibility of hosting an entire data driven application on Amazon S3 or Rackspace Cloud Files.
From the How It Works page: "Developers include a JavaScript library in their application which gives them access to a shared data structure (your Firebase). Any changes made to that data structure are automatically propagated to all other clients and to the Firebase servers....If a user modifies a piece of data a callback will be triggered on every client allowing it to respond to the change."
It sounds like every client gets a full copy of the entire database. You wouldn't exactly want to run reddit on this.
How does this work with Meteor? They said it was complimentary. Is there going to be a Firebase Smart Package for Meteor?
Michael Lehenbauer
11:51 AM
Potentially! Meteor supports a pluggable backend, so we're working on plugging Firebase in as the meteor backend. So you get the client-side help that meteor provides and the sophisticated, scalable backend of Firebase.
Sounds pretty cool and is in line with the trend of app logic moving to the front-end. I'm naturally reticent to put all my data eggs in one vendor's API basket, however (assuming this won't be open sourced). App Engine was supposed to scale too and those who bought into that ran into a lot of problems.
So, I've wanted to do a number of things in the iOS / Android space that would require some real time communications and a server. In my quick skim I didn't see a mention of mobile APIs.
