Do you more frequently use REST or SOAP Web services?

Swati Dhingra Profile: editor1
Tags:
REST
SOAP
"I need to update the local inventory database with the inventory information from multiple suppliers. The suppliers provide Web service-based interface. As the application does not have any server side component (the application is a fat client talking directly to the database), is it possible to consume these Web services directly from my application database?"

67 Replies to this discussion

 
There was an error processing your information. Please try again later.
Thanks. We'll let you know when a new response is added.
Send me notifications when other members reply.

REGISTER or login:

Forgot Password?
By submitting you agree to receive email from TechTarget and its partners. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States. Privacy
  • benzx21
    Its simple to use
    10 pointsBadges:
    report
  • navaneett1
    I havent used RESTful yet
    10 pointsBadges:
    report
  • Hexen2k2
    1. Light weight
    2. Performance
    3. Now as the world is moving from Heavy weight applications to apps and multiple devices support (Smart Phone, Tablet etc). REST opens up lot more client for the exposed WebService than SOAP.
    40 pointsBadges:
    report
  • Hexen2k2
    1 Light weight
    2 Performance
    3 Now as the world is moving from Heavy weight applications to apps and multiple devices support that is Smart Phone Tablet etc REST opens up lot more client for the exposed WebService than SOAP
    40 pointsBadges:
    report
  • Hexen2k2

    1. Light weight
    2. Performance
    3. Now as the world is moving from Heavy weight applications to apps and multiple devices support, i.e. Smart Phone Tablet etc. REST opens up lot more client for the exposed WebService than SOAP

    				
    40 pointsBadges:
    report
  • vindvg
    Because the data we are handling is not very complex and we are using the JSON for data transferring. JSON is more efficient than XML as it will be parsed faster than XML(JSON is already in the form of Javascript and all the browsers will understand ).
    Ans also some of the browsers have inbuilt support for JSON
    10 pointsBadges:
    report
  • jimmykong
    unfamiliar with REST
    10 pointsBadges:
    report
  • RahulArbatPatil
    yes, it is easy to use and also doesn't have any restriction on using xml you can use json,csv and many more.
    10 pointsBadges:
    report
  • rsaddal
    easy to code and Rapid application development, management is also very easy.
    security and other related stuff is no big deal.
    10 pointsBadges:
    report
  • noel123
    REST is flexible in terms of usage, can be used in mobile apps. fast execution.
    10 pointsBadges:
    report
  • eswaranarumugam
    Rest
    10 pointsBadges:
    report
  • ashrafwg
    In a lengthy business transaction, using REST is very difficult and required two much development effort.
    Using SOAP, it is easy to develop and manage using the tools available in the market and make monitoring the lengthy process easy
    20 pointsBadges:
    report
  • satish4ru
    I didnt get chance to use rest services. Thats why i want to learn difference between these two.
    10 pointsBadges:
    report
  • santoshghadge007
    Soap is a standard structured web service.
    10 pointsBadges:
    report
  • JetCityBeau
    speed
    10 pointsBadges:
    report
  • vgbiru
    learning
    10 pointsBadges:
    report
  • toohoo
    Because the most of our partners use SOAP. We are a service company in insurance field.
    10 pointsBadges:
    report
  • webservicelover
    While SOAP supports SSL (just like REST) it also supports WS-Security which adds some enterprise security features..
    Rest doesn’t have a standard messaging system and expects clients to deal with communication failures by retrying. SOAP has successful/retry logic built in and provides end-to-end reliability even through SOAP intermediaries
    10 pointsBadges:
    report
  • msg2raghav
    It is easy to use. Support xml as well as json, lightweight. Also, REST is well documented which makes development easy.
    10 pointsBadges:
    report
  • matthew7hayes
    It's includes a well-defined self-documenting contract which reduces the need for external documentation and in many cases, depending on the soap server, provides automatic error checking with soap faults.
    10 pointsBadges:
    report
  • rajiv076
    Till now used SOAP and learning about REST.
    10 pointsBadges:
    report
  • garaddi
    Hiii " i recently used SOAP web services for accessing wcf services from android"
    ,but nw i'm porting to HTML5,now "how can i access those services"???
    10 pointsBadges:
    report
  • vishuawate
    Mostly working on Complex App, and Web Application only.
    10 pointsBadges:
    report
  • Somasundaram
    REST is not reliable because HTTP DELETE can return OK status even if a resource is not deleted .where as SOAP is secured and Reliable
    10 pointsBadges:
    report
  • jalbersh
    Security is not an issue;Protocol is HTTP;Some of the web services were provided;Didn't have to learn a 3rd party WSDL, and the web service client would have to change if the WSDL changes.
    10 pointsBadges:
    report
  • rmarino
    WSDL saves a lot time while service consumers. REST requires word documents to explain what operations are available what parameters to pass.
    10 pointsBadges:
    report
  • Maxine Giza
    It sounds like a lot of people are gravitating towards SOAP!
    1,000 pointsBadges:
    report
  • anantmishra
    soap services
    10 pointsBadges:
    report
  • murthymuddu
    Because i am new to web services and for a starter REST is good
    10 pointsBadges:
    report
  • tjmickol
    legacy services were all developed as SOAP/HTTPS. All new services are being developed as REST/HTTPS - many legacy SOAP/HTTPS services are being reimplemented as REST/HTTPS
    10 pointsBadges:
    report
  • srinivasreddy
    While using REST my application performence is very good compare to SOAP.
    10 pointsBadges:
    report
  • kamprk
    know less on REST.
    10 pointsBadges:
    report
  • Maxine Giza
    Hi kamprk,

    Here is a link to some recent articles we published on REST. I hope it helps! http://ow.ly/u3Bio 
    1,000 pointsBadges:
    report
  • RajibGanguly
    Speed will better than SOAP
    10 pointsBadges:
    report
  • amirmb
    its simple structure and simple to learn. and it's caching abilities
    10 pointsBadges:
    report
  • geofganot
    Rest is faster, lightweight and easy to implement.
    10 pointsBadges:
    report
  • lihy70
    because i don't think SOAP is difficult to learn or use if you're not trying to learn what you may not needed.
    20 pointsBadges:
    report
  • chetanrun
    Till production move...management asked us to go for SOAP. But when the test results came out, it was REST who won the battle.
    10 pointsBadges:
    report
  • KumarNaresh
    Yes,
    Mr. ashrafwg say right,
    In a lengthy business transaction, using REST is very difficult and required two much development effort.
    Using SOAP, it is easy to develop and manage using the tools available in the market and make monitoring the lengthy process easy.

    And another thing are
    While SOAP supports SSL (just like REST) it also supports WS-Security which adds some enterprise security features.
    Rest doesn’t have a standard messaging system and expects clients to deal with communication failures by retrying.
    SOAP has successful/retry logic built in and provides end-to-end reliability even through SOAP intermediaries.
    so seems all these reasons, I think SOAP is better than REST.
    0 pointsBadges:
    report
  • usmcron
    Rest is new to me. I'm doing my first REST project now. Seems pretty easy. I may stop using soap all together after this project.
    10 pointsBadges:
    report
  • Maxine Giza
    Keep us posted on your project, mscrom! It's always nice when a different approach proves to work well.
    1,000 pointsBadges:
    report
  • jenachitta
    Easy to use
    10 pointsBadges:
    report
  • markp1
    Formal contract with external partners.
    10 pointsBadges:
    report
  • mrunmaya1
    easy to learn and start development
    10 pointsBadges:
    report
  • NarayanaSwamy
    A dedicated adapter is required to consume REST services and less secure than SOAP.
    10 pointsBadges:
    report
  • i2097i
    Keep it simple. If RESTful web services are designed and documented well, they simply work.
    10 pointsBadges:
    report
  • amitclavax
    Json format
    10 pointsBadges:
    report
  • shailymittal
    It is more easy to use.
    10 pointsBadges:
    report
  • shdrjones
    My applications require more context to be maintained to facilitate collaberation. I would use REST if pushing my apps onto mobile architectures though.
    10 pointsBadges:
    report
  • tonyeray
    Several reasons, main reason easier to maintain. Change the back end anytime, easy to version. No WSDL worries.
    10 pointsBadges:
    report
  • Maxine Giza
    It sounds like whether REST or SOAP should be used depends on the project at hand.
    1,000 pointsBadges:
    report
  • prafullakumarp
    It is light weight, easy to maintain and easily scalable.
    0 pointsBadges:
    report
  • com450
    DON'T HAVE THE CHOICE IN our current SAP version!?
    10 pointsBadges:
    report
  • johnlaw
    Fast & Flexible & Time-efficient development
    10 pointsBadges:
    report
  • sibaram
    can u please share with me the related topics for both soap and REST .I am a beginner in this PF .
    10 pointsBadges:
    report
  • Maxine Giza
    Hi Sibaram! We have a lot of articles posted on REST and other integration methods here:  http://ow.ly/wukZt. I hope this helps!
    1,000 pointsBadges:
    report
  • umakdpathy
    Currently i am working on SOAP . The reason is i don't have much knowledge on Restful web services.
    10 pointsBadges:
    report
  • sundeepelec
    REST is a still new cup of coffee and need to explore
    10 pointsBadges:
    report
  • Maxine Giza
    Sundeepelec, I like the way you phrased your experience with REST!
    1,000 pointsBadges:
    report
  • muraliP
    Easy to implement
    10 pointsBadges:
    report
  • ahmedkhan
    Project basis on rest
    10 pointsBadges:
    report
  • Arunkumarvarada
    we used earlier SOAP Model... currently migrating to RESTful services
    0 pointsBadges:
    report
  • chaituvella
    REST - lightweight, use this for all communication between Mobile apps and Server.
    10 pointsBadges:
    report
  • jibinthomas
    Architectural decision
    10 pointsBadges:
    report
  • pashamshaik
    I recently got to know about REST
    10 pointsBadges:
    report
  • Maxine Giza
    Pashamshaik, what are your thoughts on working with REST so far?
    1,000 pointsBadges:
    report
  • SampathKumar
    I am using SOAP WSDL webservice using Axis framework [even though is not being updated from 2012] in my application from the past 5+ years.
    0 pointsBadges:
    report

Forgot Password

No problem! Submit your e-mail address below. We'll send you an e-mail containing your password.

Your password has been sent to:

To follow this tag...

There was an error processing your information. Please try again later.

REGISTER or login:

Forgot Password?
By submitting you agree to receive email from TechTarget and its partners. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States. Privacy

Thanks! We'll email you when relevant content is added and updated.

Following