How deeply does Building Web APIs with ASP.NET Core cover SOAP?

Identifies SOAP and the need to compare trade-offs and formats, but does not explain SOAP messages or implementation.

SOAP

As explained in Building Web APIs with ASP.NET Core

SOAP is a messaging protocol specification for exchanging structured information across networks, commonly encoded in XML.

SOAP (Simple Object Access Protocol) is a messaging protocol for exchanging structured information across networks, commonly encoded in XML. Like any web API approach, it needs clear rules and formats so parties can exchange data unambiguously. section 1.1.4

When choosing an approach for a web API, compare SOAP with REST, RPC, and GraphQL. They differ in characteristics, trade-offs, and supported data formats. This overview does not provide steps for implementing SOAP. section 1.1.4

How Building Web APIs with ASP.NET Core covers it

Cover of Building Web APIs with ASP.NET Core

liveBook manning.com

Read Building Web APIs with ASP.NET Core on liveBook Get the book at manning.com

Related concepts

xmluses · XML is a text-based markup language for encoding structured documents and data using elements, attributes, and nested relationships.
RESTalternative to · REST is an architectural style for distributed hypermedia systems that organizes interactions around resources and representations through constraints including a uniform interface, stateless communication, cacheability, and layered components.
contractkind of · An API contract is a specification of the operations, data, and behavioral expectations that govern interactions between software components.
recordkind of · A Kafka record, also called a message, is a data item published to or consumed from a Kafka topic, optionally containing a key, value, and metadata.

This explainer was generated by Manning's knowledge graph from the text of Building Web APIs with ASP.NET Core. The section links point to the parts of the book it draws on.