mORMot Open Source

I use SOAP many years... since 2001 and last year too.

Its is standardized.
Self documented.

Each technology there is a place.
It is necessary to know it and to apply.

For REST it is necessary to add Swagger or RAML for documenting.
If this public API, then it is mandatory.

In my opinion, SOAP benefits in stable/conservative systems with public API (Java/NET/BigFatEnterprise :-) .

REST benefits in dynamic programs, with a quickly cycle of development/changes.
After stabilizing - we add documentation.

> Even SOAP is not standard
WOW!
I don't know the technology having more than standards.
Another thing is that not all libraries support it standards.

SOAP overengineering, is the fact.
It not quickly, but is standardized.
More then one serialization format.
More then one transport layer.
In real life, everything is limited XML/HTTP.
As a result, this is Enterprise Level solution.

Realization of SOAP in Delphi is based on WebBroker.
If somebody writes provider for WebBroker who will use HTTP.SYS as HTTP stack layer, it will be the decision.

We can use SOAP(and any WebBroker) with Indy as Self Hosted Server App/Service
or ANY WEB server extension module that support Delphi:
CGI/ISAPI/Apache shared module.
FastCGI dont support by Delphi :-( in the box.

>At least SOAP 1.0.
As CLIENT Delphi build-in support SOAP 1.3 in any of serialization scheme (RPC|Document)/(Encoding|Literal).
As Server, in native mode, RPC/Encoded only.
Besides complexity is the reason of it.

The producer of Delphi7 (Borland) wrote in documentation (is inexact):
If you need Document/Literal style - use .NET Delphi version.

RemObject's SDK has support of any SOAP dialect, but everything source code should be rewritten.
Lazarus/FreePascal community can offer WST-WebServiceToolkit, SOAP 1.1 only.

mORMot, on the contrary, proposes the solution, other than SOAP.
Quickly cycle of development.
Big capacity.
...and REST

REST is fast and simple alternative to SOAP.
These are the opposed Worlds.