http - Websockets for background processing -
Webcots (Comet, Server Push, ...) to solve problems with long-running HTTP Using a good idea is requests? Imagine that you have an app, make the entire stack on the web app framework, such as DJJongo, or Rail If you want to perform some background processing on the name of the display, it is easy to do this from a programmer perspective, but the problem occurs in the UI.
Users ask for immediate feedback. So thought to me. Io + node. JS + AMQP Messaging was to be used so that after completing background tasks, the information in the browser could be sent back. I like this idea, but it still feels like a lot of engineering, just because we do not want to request a request in our main app for a long time, the idea of competing is to use another, more robust, web server , Which can handle many long-running HTTP requests.
Which one do you feel better?
Yes it is. You can save a lot of data over other techniques, such as continuous or long voting. Let me try to see the part of step 3.
I like this idea, but it still looks like a lot of engineering, just because we have not longed to run requests in our main app for a long time. The idea of competition may be to use another, more robust web server, which can handle many long-running HTTP requests.
Socket.io, Transport Layer and Fallback solution (in the case of website absence) for you. If you want to use the socket.io/node.js/AMPQ stack only for sending and notifications for the message, then it should not be a complex or time-consuming development process, although it may depend on various goods.
Messaging / Notification node By sending JS, you can eliminate your main app for your non-blocking architecture largely, although you will introduce dependence on any other technology.
By choosing a more efficient web server on the other hand, your functionality can be solved for a while, but you can finally scaling your system (either up or out).
Comments
Post a Comment