Web services or user protocol?

Question

I have no experience with web services. Historically, I created client-server systems using proprietary communication protocols (even they appear to be XML). I just spent several hours looking at Axis2, and it shuddered in my spine. The WS learning curve scares me, and seeing that the XML environment has so little functionality makes me wonder if this is worth worrying about.

How do you decide if you need to use web services or your own communication protocol? What are the advantages / disadvantages of each approach and which use cases are best suited?

Please post a clear guide, not part of the opinions :)

Answer 1

-API RESTful; .., , (SOAP, XML-RPC ..)

. .

, RESTful API , - , .

Answer 2

"-", W3C, SOAP HTTP. SOAP ; (IMO), , API .

( , ) - , XML-RPC. , ; XML-RPC , bloaty ol XML.

Answer 3

, , - . VB/#.Net . , , .

- . , , . , , . , -, - XML.

Answer 4

, . , -.

. - , .

Answer 5

. Apache libCurl plus libxml2 XML , ++.

PHP, CGI, . , .

Answer 6

- , , , , -, . HTTP - - . XML, , , .

, , / xml . , .

Answer 7

( ) ​​, - (.. , ..). , XML.: -)

, , - . - "" " ".

Answer 8

SOAP XML - ", XML , , ".

. SOAP - - Java.

REST, on the other hand, is much easier. In addition, REST with JSON or REST with YAML is very lightweight and very easy to implement. It builds directly on top of the HTTP protocol outside the field.

REST requires that you define resources (called via URIs) and transactions based on the canonical CRUD rules (GET, POST, PUT, and DELETE). Very simple and canonical.