Which technology is faster in sending data websocket, signalr, WCF or sqlchangenotification

Question

1.00/5 (1 vote)

See more:

, +

I wanna to build a stock exchange application : 
which is a form have datagridview and its data change in it immediately (reel-time) 
- it will be something like this =>  <a href="https://lh5.ggpht.com/-VgRRhU78EWxw6LsOUj4OaPnmQKafEQfaJ_xgua9_jYu1goexHSkI-cLj-J0lLGGYQ=h900"></a>[<a href="https://lh5.ggpht.com/-VgRRhU78EWxw6LsOUj4OaPnmQKafEQfaJ_xgua9_jYu1goexHSkI-cLj-J0lLGGYQ=h900" target="_blank" title="New Window">^</a>]  - 
it will be a desktop application what i ask for the fastest technology not the easiest to coding so which one i must use : 
1.websocket (itself) 
2. wcf 
3. signalr 
4.sql change notifications 
5.or there's other technology i must use 
there's a note that the application clients will be thousands or millions 
and maybe use windows xp or at most it will be windows 7 (who will use 8 or 10 will be so few)

What I have tried:

1.websocket (itself) 
2. signalr 
3. sql change notifications

Posted 20-Sep-17 2:22am

ZhEaIsNsAaBn

Add a Solution

Comments

Dave Kreskowiak 20-Sep-17 9:10am

Considering every communication channel is going only add hundreds of milliseconds to what's displayed, the problem is not the channel. It's going to be your processing of the data and how you're going to render it.

From the description of the application type, tweaking out milliseconds isn't going to get you anything in the market.

ZhEaIsNsAaBn 20-Sep-17 10:50am

milliseconds isn't a problem
but what i mean which technology can work on a big number of users connected in same time to get the same data from my server with a big stability and without any problems
where the users will just have windows xp
coz the competition between this programs is in which app is faster than other

Dave Kreskowiak 20-Sep-17 11:30am

To support "millions" of users will require serious infrastructure on the server side, both hardware and software. That infrastructure is going to have a massive effect on the speed of the data you're pushing. Again, it's not the type of communication channel.

Typically, something like this might be broadcast over UDP. It's connectionless so is less stressful on servers as they don't have to maintain state, but it does not guarantee delivery to any client.

That's up to you. Is guaranteed delivery of data a requirement? That depends on your application and the data you're sending. If it is, that's going to require the servers maintain connections and state. That means you're going to need a server for every 50,000 users, or less.

How is your app going to disseminate the data to all of these servers?

How are you going to manage that state?

Again, you're concentrating on the wrong thing.

Graeme_Grant 20-Sep-17 17:24pm

Fyi, SignalR is build on top of a number of protocols including websocket.

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)