As I mentioned above, there are other ways to do what you need using REST servers, an advantage of REST is that the client layers can be developed in any programming language that has JavaScript Object Notation (JSON) support.
JSON has been widely used by web applications because of its ability to structure information in a much more compact way than the XML model, making parsing faster.
In general, the Web Services mentioned by you came to allow applications developed in different languages, running on different platforms, to exchange data between them in a transparent way. The data communication SOAP protocol is structured via XML.
But Web Services uses SOAP over HTTP, that is, only HTTP is not
enough to work with Web Services. SOAP encapsulates messages sent between client and server, resulting in more work and slowing the transmission of information.
A new paradigm that has become a viable alternative to SOAP and well used in multi-tier applications is the Representational State Transfer (REST).
A RESTFul application - a term used to identify a system that follows REST ideas - combines the use of the principles established by the REST technique, such as a stateless client-server protocol, that is, each HTTP message contains all the information needed to understand a request; and a well-defined set of operations that applies to all data processing resources.
The operations of a RESTFul application resemble CRUD operations in traditional data persistence, they are: POST, GET, PUT, and DELETE.
The implementation of all this depends on a lot of things, language, architecture, etc., this is just a general idea.
