Skip to main content

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

Required fields*

9
  • 12
    Scroll down a bit on that page: "Instead of typical HTTP requests, the Firebase Realtime Database uses data synchronization—every time data changes, any connected device receives that update within milliseconds. Provide collaborative and immersive experiences without thinking about networking code". Clients don't have to poll, they get notified of data changes. Commented Apr 15, 2017 at 9:26
  • 3
    Ah okay, so the difference is not really about how quickly the data is stored, it's more about the fact that the database can send push notifications about changes to clients in real time? And with for example Backendless the clients would have to manually poll the database to see the changes? That makes sense, but it's a bit confusing name for it... I guess "Notificating database" or "Observable database" doesn't sound as catchy though... Commented Apr 15, 2017 at 9:36
  • 1
    A further source of confusion was that Wikipedia says that a realtime database uses "[...] timing constraints that represent a certain range of values for which the data are valid. That makes it sound like a realtime database is more like a non-persistent temporary cache than a permanent storage solution? I guess that's not at all what Firebase mean with their terminology? Commented Apr 15, 2017 at 10:05
  • 1
    Also, if the server supports HTTP long polling, isn't that effectively the same thing? Commented Apr 15, 2017 at 10:39
  • 3
    It's not "a realtime database". It is the "Firebase Realtime Database". It's just a product name. You might just as easily wonder what "a Firebase" is. Commented Apr 15, 2017 at 15:39