<story><title>‘Firebase’ Does for Apps What Dropbox Did for Docs</title><url>http://www.wired.com/wiredenterprise/2012/04/firebase/</url><text></text></story><parent_chain></parent_chain><comment><author>mgkimsal</author><text>I didn&apos;t dig deep in to the docs - just played with the demos - but if all data is exposed as &apos;just&apos; a URL - what implications are there for security?  Can someone mod the JS to grab someone else&apos;s data associated with my app?  They probably have answers for this, but it wasn&apos;t apparent in the demos I looked at.</text></comment>
<story><title>‘Firebase’ Does for Apps What Dropbox Did for Docs</title><url>http://www.wired.com/wiredenterprise/2012/04/firebase/</url><text></text></story><parent_chain></parent_chain><comment><author>jerguismi</author><text>I don&apos;t really get the benefits. You don&apos;t need servers, but you need to host the JS/html5 application somewhere, even if you don&apos;t need to configure the database server etc.&lt;p&gt;It is nice technology, but I don&apos;t really see if it is worth the price (vendor lock-in, technology lock-in, etc.)</text></comment>