Home > Net >  Server, client, WEB management front-end technology selection for help???????
Server, client, WEB management front-end technology selection for help???????

Time:09-17

Server, client, WEB management front-end technology selection for help???????

1, I want to build a cloud server, he need to manage 300 clients, access to the cloud server using the WEB interface way,
2, state monitoring: the current state of each client need real-time transmission to the cloud server, you can open cloud server the client WEB management interface to view the current status,
3, file backup: each client generated files need to backup to the cloud, the cloud server WEB management interface, can set the timing and upload real-time backup strategy,
4, cloud server WEB management interface: open cloud server WEB management interface, the client can view real-time status, query, statistics and backup file playback file, download file operations, such as

Now determine technology is: cloud use SOCKET TCP server and client communication,
Otherwise I is to use WCF WEB SERVICE or other more suitable technology???????

CodePudding user response:

The problem is bad to say, anyway you feel can do do, what can be implemented, but is the length of time, convenient maintenance, extended or not problems

, as for selection really doesn't matter, how high are high, low had low style
Such as if into a giant experience
Your 2 he can choose the MQTT, redis/etcd cooperate, rabiitemq
Your 3 he can choose quartz
Your 4 can be directly selected MQTTJS, websocket

Ps: choose your own sokect there is no problem, but is to write their own bridging forwarding services, (when for point-to-point operation, you'll have to put the web request, wabapi, websocket, corresponding to the forward to go out, and then forward the received results in corresponding to the requester),
Or that sentence, of course, want how to actually get, such as Akka.net, such as Microsoft's part that goes from also can finish this kind of request (is the actor model, model of Erlang, Erlang is natural dry the ace of the distributed requests), having said that, in fact netmq also become,
Overall scheme, main project size, and you can master yourself to what extent

CodePudding user response:

Personal advice, first look at the "IOT solutions", the BAT, Microsoft has, take a look at how to play a consortium, then revert to what you choose,

At present company mainly for standard is
MQTT + temporal database===============the two pieces will solve the problem of 80%, as for the remaining 20% that's opinion, after all the project details, who are not gods, who can't consider the location of details

CodePudding user response:

Are there any other player to reply?

CodePudding user response:

Your 300 clients all on the cloud? Group of a local area network, local area network (LAN) can set the path directly copying the files to your server, it's so easy? Don't set your client must support passive pull files, how is your server can be configured from the client pull files (regardless of the timing or instant), and what the devil is playing file? Is this your video web site?

CodePudding user response:

The 300 clients are distributed all over the country, is a desktop application, will survive the MP3 files regularly, will take the initiative to connect to the cloud server, need to upload real-time current state, also need to upload the MP3 files regularly,
  •  Tags:  
  • C #