A static web application was adequate for the era of Spice Girls and Backstreet Boys.
Today, users expect a lot more.
A real-time application involves far more interactions with the server, delivering a lot more information to your users.
If another user updates a document that you are working on, a real-time application will tell you that right away. If other updates are coming in, they happen live.
This is the real-time baseline requirement: Your website and application must continuously update what’s going on.
That can put quite a load on your server.
It challenges your browser. Does it keep asking the server “Was there a change? Was there a change?” or will it reverse that by having the server notify the client when something does change.
Developing that type of solution is non-trivial.
RavenDB tackles it for you with its Changes API feature. You can subscribe to actions where your database lets you know when they occur.
For example, if something changes on an invoice, you don’t have to ask. This impact magnifies if you have multiple applications listening to what is happening inside one database.
As the database notifies you, you can notify your users and they can do something with that.
Real-time applications have super short time constraints. Pages must be rendered fast. Updates always have to happen now. Your database must process requests in a time frame of immediately.
See RavenDB CEO Oren Eini demonstrate the lighting fast performance of RavenDB, guiding you through data subscriptions, Changes API, and everything you need to keep up with the current moment.