Win a copy of Re-engineering Legacy Software this week in the Refactoring forum
or Docker in Action in the Cloud/Virtualization forum!
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic

webservice design pattern

 
Laxman Nagalla
Greenhorn
Posts: 10
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi All,

I need to understand which one is the best design pattern for my requirement.

We are the servers needs to provide the web service to clients. Clients send the request with the request we need to search the field in our database and send the multiple values as response.

Suggest which design pattern fit.

 
Vijitha Kumara
Bartender
Posts: 3913
9
Chrome Fedora Hibernate
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
It looks bit vague when you say like that. What options have you looked at here? You can send a SOAP response or similar in this case? What particular issues you have faced?
 
William Brogden
Author and all-around good cowpoke
Rancher
Posts: 13056
6
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
We are the servers needs to provide the web service to clients. Clients send the request with the request we need to search the field in our database and send the multiple values as response.


You need to flesh out your requirements before starting to think about abstractions like design patterns.

The first question that occurs to me is what are your clients expecting?

The big choice for a web service is SOAP versus RESTful architecture. Are your clients committed to one or the other?

Are they accessing your service by web browser or custom client software?

Do clients ever update your database with new data or are all transaction read only?

Bill
 
Laxman Nagalla
Greenhorn
Posts: 10
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Thanks William for your response.

Below is my answer for your questions.

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.
 
William Brogden
Author and all-around good cowpoke
Rancher
Posts: 13056
6
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
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.

Bill

 
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic