-1

I'm working on a application that uses SignalR for real-time communication between workstations and sensors. Currently everything runs locally, butI'm planning to move to Azure cloud and I'd love some feedback on the architecture to handle this optimally.

Current Setup (All Local)

Local SignalR Hub (Messaging middleware)

Client Service - communicates with sensor hardware

Frontend acting as an interface for taking images

Message Flow:

User clicks "Take Image"

UI sends message to local SignalR Service

This service routes to the local client by clientId

Local client acquires image from sensor

Response returned back through local client to UI

Image displayed

Now I'm thinking of pushing this SignalR Service to cloud and utilize Azure SignalR Service and also, I'm thinking of deploying the UI over to cloud. Would this setup scale for concurrent 50k workstations taking images?

Improve this question
New contributor
Salman Khan is a new contributor to this site. Take care in asking for clarification, commenting, and answering. Check out our Code of Conduct.
3
  • 1
    First of all: why do you need SignalR? It sounds like simple request-response pattern. Secondly, scalability is not directly related to where the app is hosted. It's more about the internals and details of the app itself. Commented yesterday
  • 1
    "Would this setup scale for concurrent 50k workstations taking images?" In all honesty, how do you expect anyone to answer to this question properly without knowing anything about implementation and any other detail? In any case, this is a question only you can answer, by running perfomance tests and stress tests on your service. Commented yesterday
  • Please edit the question to limit it to a specific problem with enough detail to identify an adequate answer. Commented yesterday

0

Reset to default

Start asking to get answers

Find the answer to your question by asking.

Ask question

Explore related questions

See similar questions with these tags.