51–60 of 148 posts
Another great step in the right direction. That being said, I do believe the hardest part of all these attempts to abstract backends is authentication and security models. It seems to me that most of these services launch before figuring out that critical part of the puzzle.
Mongo for storage backend
Node.js client is Faye
Scala + Netty backend
custom JS client supporting "IE7+, Opera 10+, Safari / Chrome (recent versions), FF3.0+"
Earlier quoted context omitted.
Good question. Meteor is an application framework, like Ruby on Rails. Firebase is a database, like MySQL. We both think that application development is going to radically change in the future and we're both building products that promote a new way of developing apps. We're stoked about Meteor and see our products as very complementary.
Could Firebase be used as a database for Meteor? (i.e. replacing Mongo)
Earlier quoted context omitted.
Good question. Meteor is an application framework, like Ruby on Rails. Firebase is a database, like MySQL. We both think that application development is going to radically change in the future and we're both building products that promote a new way of developing apps. We're stoked about Meteor and see our products as very complementary.
Could Firebase be used as a database for Meteor? (i.e. replacing Mongo)
Tools used (from the chat): Mongo for storage backend Node.js client is Faye Scala + Netty backend custom JS client supporting "IE7+, Opera 10+, Safari / Chrome (recent versions), FF3.0+"
Another great step in the right direction. That being said, I do believe the hardest part of all these attempts to abstract backends is authentication and security models. It seems to me that most of these services launch before figuring out that critical part of the puzzle.
We're using authentication in our Firebase app and it works wonderfully. Although all data is visible on the Firebase backend, we simply put pointer ids in Firebase, so no identifying data is publicly visible.
This is cool. But can someone explain how data is secured in Firebase or Meteor? From the Leader Board sample: // Use setWithPriority to put the name / score in Firebase, and set the priority to be the score. userScoreRef.setWithPriority({ name:name, score:newScore }, newScore); How about I just change newScore to 100,000 in the debug window?
Good catch : ) We mention this briefly in our FAQ. We actually do have security in place (notice you can't enumerate other people's data for instance in our own tutorial), but the API is far from complete and we have no docs yet. There will be a full-fledged security model coming over the next few months.
This sounds like Model-as-a-service from the MVC pattern.
Another great step in the right direction. That being said, I do believe the hardest part of all these attempts to abstract backends is authentication and security models. It seems to me that most of these services launch before figuring out that critical part of the puzzle.
We're using authentication in our Firebase app and it works wonderfully. Although all data is visible on the Firebase backend, we simply put pointer ids in Firebase, so no identifying data is publicly visible.
Can't people find an alternative to the word "real-time" that hasn't already been used for 30 years to mean something entirely different? (As in, real-time systems, real-time operating systems, etc.) I'm not trying to put down Firebase, I imagine it's great.