Sunday, October 28, 2018

Which approach should I take when building a real-time app with SignalR?

I'm thinking about creating a real-time app. The main application will be WPF-based, and will need to support a few real-time features. Users will be able to move controls around on a canvas. The delta's don't need to be transferred, but the final mouse-up positions will be. The application will also have a text-based chat system among other things.

Let's say that, for every control on the canvas, I have an object in my database. Let's also say that the X's, Y's, Width, and Height are updated in the database on mouse up of the control.

Do you think it would be wise to have client's update the database with their changes... and then simply pass the SignalR enabled web server the Id, Entity Type, and CRUD operation type. Then SignalR will broadcast that message to everyone else and the other client's will pull the data from the DB themselves?

How scalable is this type of approach in general?

Or should I pass the relevant data in my message so the client's don't need to fetch it?

Any pointers to worthwhile resources will be appreciated!

Thanks for looking

Which approach should I take when building a real-time app with SignalR? Click here
  • Blogger Comment
  • Facebook Comment

0 comments:

Post a Comment

The webdev Team