If your traffic is mostly GETs and you don't need SOAP's complex WS-* security thingees, RESTful services will be MUCH MUCH easier to implement.
Thousands of times per minute should not be a problem.
Where are your clients and how do they connect?
One under-appreciated advantage of sticking to HTTP and servlets is the ease with which you can monitor the service from anywhere with a browser.
Joined: Jan 19, 2011
The clients can be all over the world and one server somewhere in Europe. This web service must respond 99% with another string and I figured that GET is the best approach. Of course, I will add SSL on top. Any suggestions on a way to do the encryption and decryption?