The first question that occurs to me is what are your clients expecting?
Response: Clients expects is they will send the request of one field we need to search the field in our DB and send the response back with few fields in that record.
The big choice for a web service is SOAP versus RESTful architecture. Are your clients committed to one or the other?
Response: No one is committed for any web service. We thought we can implement in SOAP service.
Are they accessing your service by web browser or custom client software?
Response: through web browser
Do clients ever update your database with new data or are all transaction read only?
Response: All the transaction are read only.
Author and all-around good cowpoke
Joined: Mar 22, 2000
This is very clearly suitable for a RESTful architecture service. With utterly no reason to consider SOAP.
REST is an "architecture" ie a Design Pattern controlled by a fixed meaning for the HTTP methods - in your case all user requests are GET - which implies returning the present state of a resource. A traditional web service in other words.