When to use SignalR and when to use WebServices?

See more:

C#

SignalR

WCFServices

I Am new to WebServices, so I started to learn about them by creating a project. My idea was to create a REST based WCF service with JSON which is consumed by a Windows Application. This Windows application Post's data to the service and the service stores them in DB. Now, I thought, I will add a WebClient which can actually show the data received from the Windows Clients. To display data on my WebClient, I created a self-hosted Signal R console App, which communicates with my WCF service and gets the data to the WebClient.

Now, I realized that I can send data directly to my SignalR server from my WindowsClient and my SignalR server can route it to WebClient, without needing WCF Service in between. Also, I can even send message from my WebClient to Windows clients using SignalR. If I had to use my REST WCF service to send asynchronous messages to clients, then I need to change from WebhttpBinding (which I used for REST) to netTCPBinding and make it a duplex service which is more complicated....and it will no longer be REST compatible

So my question is when I am able to do everything with SignalR, why and where do I need to use WCF or any webService?

Please let me know if there is anything wrong in my understanding...Thanks in advance.