Synchronous message queue
-
I'm busy on the architecture for a 5 year project, that looks like this. Server 1: web server and .NET components (10 kilometers away) Server 2: web services returning data from Oracle. Now the problem is that the idea of message-queuing keeps on coming up. The idea is for the webservices to feed directly off an MQ series queue and return data to Server 1's clients. To me, the whole premise of a queue was "leave x here and I'll get around to servicing it soon". Is this off the track? Can a queue guarentee immediate action on queued items? Should it? Cheers, Simon "Every good work of software starts by scratching a developer's personal itch.", Eric S. Raymond
-
I'm busy on the architecture for a 5 year project, that looks like this. Server 1: web server and .NET components (10 kilometers away) Server 2: web services returning data from Oracle. Now the problem is that the idea of message-queuing keeps on coming up. The idea is for the webservices to feed directly off an MQ series queue and return data to Server 1's clients. To me, the whole premise of a queue was "leave x here and I'll get around to servicing it soon". Is this off the track? Can a queue guarentee immediate action on queued items? Should it? Cheers, Simon "Every good work of software starts by scratching a developer's personal itch.", Eric S. Raymond
SimonS wrote: Now the problem is that the idea of message-queuing keeps on coming up. The idea is for the webservices to feed directly off an MQ series queue and return data to Server 1's clients. Seems reasonable. SimonS wrote: "leave x here and I'll get around to servicing it soon". I did only a minor programming with MSQueue, but the main purpose of it, was availability , that is , the clients can continue to work with the app , even if disconnected from the network, this is a godsend with no time critical apps or jobs/tasks. So in a disconnect world like Internet , it makes perfect sense to inject the information in a queue to be processed . Cheers, Joao Vaz A person who is nice to you, but rude to the waiter, is not a nice person - Natalie Portman (Padme/Amidala of Star Wars)
-
SimonS wrote: Now the problem is that the idea of message-queuing keeps on coming up. The idea is for the webservices to feed directly off an MQ series queue and return data to Server 1's clients. Seems reasonable. SimonS wrote: "leave x here and I'll get around to servicing it soon". I did only a minor programming with MSQueue, but the main purpose of it, was availability , that is , the clients can continue to work with the app , even if disconnected from the network, this is a godsend with no time critical apps or jobs/tasks. So in a disconnect world like Internet , it makes perfect sense to inject the information in a queue to be processed . Cheers, Joao Vaz A person who is nice to you, but rude to the waiter, is not a nice person - Natalie Portman (Padme/Amidala of Star Wars)
Joao Vaz wrote: disconnect world like Internet , it makes perfect sense to inject the information in a queue to be processed To me a queue is/can be asynchronous, so I don't see the usefulness for it in a synchronous web page. :confused: Cheers, Simon "Every good work of software starts by scratching a developer's personal itch.", Eric S. Raymond
-
Joao Vaz wrote: disconnect world like Internet , it makes perfect sense to inject the information in a queue to be processed To me a queue is/can be asynchronous, so I don't see the usefulness for it in a synchronous web page. :confused: Cheers, Simon "Every good work of software starts by scratching a developer's personal itch.", Eric S. Raymond
SimonS wrote: To me a queue is/can be asynchronous, so I don't see the usefulness for it in a synchronous web page. SimonS wrote: synchronous web page. :confused: Well ,for synchronous processing , I not seeing the usefulness either ... But for a asynchronous order system , it's cool, but thinking better , for instance to assure that the system receives all the orders order , it works good , imagine your Server app goes down, and the orders aren't saved sucessfully to the db, you lost the orders ... , but you still have it in the Message Queue, so when the Server goes up again , voila , no orders lost and happy clients :-) It's like in this case of a adding a security layer ... Cheers, Joao Vaz A person who is nice to you, but rude to the waiter, is not a nice person - Natalie Portman (Padme/Amidala of Star Wars)