Is a queue server the right solution?
Hi you all,
Here is the deal, in our company (ok I wish it was my company), we are implementing a mobile phone activation system, the main idea is that a client (ivr), talks to an Activation Server (composed by Spring + Pojos + Hibernate) and that the client sends every data that we need for the activation.
But, if for some reason, once we have all our data collected, the activation can’t be completed, because the databases are down, the ivr lost the connection with the activation server, or whatever other problems, we need to store all that data somewhere and wait until the server, databases or activation resources are available so we can complete the activation.
We have in mind 2 solutions
The first one, an awful not so elegant one, but that could work, is to use a database to store all that data (Persist our ActivationData Pojo) and then use a daemon to se if there are any activations awaiting in that database, once the resources are available again.
And the second one, a more elegant one is to use ActiveMq, to queue all our activation objects (Pojos), and once our activation resources are ready to go, ActiveMq, would talk to the Spring Facades to complete the activation.
That’s what we have in mind, but we would like to hear your opinion, if you think we are on the right track with the ActiveMq idea (because that is the one we are inclining for), or if there’s a more easy way to do this please tell, or a more elegant way… we would like to hear your comments… Also we would like to know if anybody has used ActiveMq with Spring, or if our idea is viable or no…
Thanks to everybody
- h e c t o r l a z o -