Keeping it Real with Real-Time Application Architecture
Once upon a time, a static web application was adequate. But back then, so were the Spice Girls.
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.
RavenDB tackles the challenge with its Changes API. You can subscribe to actions where your database lets you know when they occur. 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. Your database must process requests in a time frame of immediately.
See RavenDB CEO Oren Eini demonstrate the lightning fast performance of RavenDB, guiding you through data subscriptions, Changes API, and everything you need to keep up with the current moment.