blocks|key|2738097|text|在较低的层次上，web应用程序和web服务是一样的。它们都在http(s)上运行。SOAP只是XML的一个定义良好的版本。REST只是一种HTTP。如果你愿意，你可以让一个web应用程序看起来像web服务，反之亦然。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2738098|主要区别在于基于您所使用的平台的内部开发选项。例如，如果您使用的是Visual+Studio，那么添加一个WCF服务应用程序将为您提供一个默认情况下面向WCF的项目。但是，选择任何其他应用程序类型都不会阻止您添加Web服务。|2738099|由于以下原因，使用SOAP通常是比普通的旧式xml更好的选择：|2738100|2738101|您的用户将期待它，并且很可能已经知道如何阅读它。|unordered-list-item|2738102|您的用户的开发环境将可能知道所有关于SOAP的知识，并能够开箱即用地解释它。(如果您提供了一个WSDL文件，那么许多用户将能够使用脚本在几秒钟内生成您的类。)|2738103|您的消息更可能是定义良好的。我正在做一个项目，在这个项目中，另一方定义了他们自己的随机XML结构，这是一场噩梦。我从来不知道会发生什么，而且它们不同的消息类型之间几乎没有一致性。至少，如果他们同意遵循SOAP，那么我可能会更容易解释他们的消息。|2738104|2738105|entityMap^0|0|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|Q|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|R|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|S|8|@]|9|@]|A|$]]|$1|F|3|-4|5|6|7|T|8|@]|9|@]|A|$]]|$1|G|3|H|5|I|7|U|8|@]|9|@]|A|$]]|$1|J|3|K|5|I|7|V|8|@]|9|@]|A|$]]|$1|L|3|M|5|I|7|W|8|@]|9|@]|A|$]]|$1|N|3|-4|5|6|7|X|8|@]|9|@]|A|$]]|$1|O|3|-4|5|6|7|Y|8|@]|9|@]|A|$]]]|P|$]]

At a low level web applications and web services are kinda the same thing. They both operatate over http(s). SOAP is just a well defined version of XML. REST is kinda just HTTP. If you wanted to, you could make a web application look like web services and visa versa.

The main difference would be internal development options based on the platform you are using. If, for example, you are using Visual Studio then adding a WCF Service Application will give you a project which is by default geared towards WCF. But choosing any other application type won't stop you from adding Web Services.

Using SOAP is generally a better option than plain old xml for these reasons:

<ul>
<li>Your users will be expecting it, and are likely to know how to read it already.</li>
<li>Your users' development environments will likely know all about SOAP and be able to interpret it out of the box. (If you provide a WSDL file then many users will be able to use a script to generate your classes in seconds.)</li>
<li>Your messages are more likely to be well defined. I am working on a project at the moment where the other side have defined their own random XML structure and it is a nightmare to work with. I never really know what to expect, and there is little consistency between their different message types. At least if they had agreed to conform to SOAP then I might have had a much easier time interpreting their messages.</li>
</ul>

blocks|key|2738107|text|如果您的应用程序不需要用户界面，则将其设置为web服务。如果它需要一个用户界面，那么就使用web应用程序。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2738108|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

If your application doesn't need a user interface, then make it a web service. If it needs a user interface, then use a web application.

blocks|key|49344|text|如果我们考虑术语，我认为这是这里的主要问题。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|49345|Web服务是指以任何格式(XML/JSON等)提供数据的软件。通过某种网络接口。该接口可以称为API+(应用程序编程接口)。REST和SOAP是设计API的方法。|49346|应用程序是使用web服务提供的此API的软件。|49347|换句话说，web服务是“服务器”，应用程序是“客户端”。通常服务器为机器服务，客户端为用户服务。|49348|因此，无论您选择以何种方式构建系统，我都会将提供数据的部分称为"Web服务“，将使用数据的部分称为”应用程序“(或"web应用程序”，如果是这样的话)。|49349|在您的示例中，您正在构建一个为多个应用程序提供XML格式数据的web服务。所以我的回答是:构建你已经在构建的东西，并将其命名为web服务。|49350|entityMap^0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|N|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|O|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|P|8|@]|9|@]|A|$]]|$1|F|3|G|5|6|7|Q|8|@]|9|@]|A|$]]|$1|H|3|I|5|6|7|R|8|@]|9|@]|A|$]]|$1|J|3|K|5|6|7|S|8|@]|9|@]|A|$]]|$1|L|3|-4|5|6|7|T|8|@]|9|@]|A|$]]]|M|$]]

If we think the terminology, which I think is the main question here.

Web service refers to software, that serves data in any format (XML/JSON etc.) through some kind of web interface. That interface can be called API (Application Programming Interface). REST and SOAP are ways to design the API.

Application is the software that is using this API provided by the web service.

In the other words, web service is "server" and application is "client". Usually server serves machines and clients serve the user.

So in any way you choose to build your system, I would call the part that serves the data as "Web service" and the part that utilizes the data as "application" (or "web application" if such). 

Sounds like in your case, you are building a web service that provides XML-formatted data for multiple applications. So my answer is: build the thing you are already building and call it web service.

blocks|key|2738193|text|我知道现在回放已经太晚了，但我还是想|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2738194|Web服务方法在以下情况下是好的|2738195|答:仅与webservices的企业集成，如集成分布式模块/applications。|2738196|b.适用于分布式应用程序|2738197|c.多个消费者使用来自信用报告机构的数据，如使用相同服务的银行|2738198|d.消费者需要不同格式的数据-比如一个消费者(客户)想要XML格式的数据，另一个消费者(客户)想要JASON+..etc格式的数据。|2738199|entityMap^0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|N|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|O|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|P|8|@]|9|@]|A|$]]|$1|F|3|G|5|6|7|Q|8|@]|9|@]|A|$]]|$1|H|3|I|5|6|7|R|8|@]|9|@]|A|$]]|$1|J|3|K|5|6|7|S|8|@]|9|@]|A|$]]|$1|L|3|-4|5|6|7|T|8|@]|9|@]|A|$]]]|M|$]]

I know its too late to replay, but still i want

Web Services approach is good if 

a. enterprise integration with only webservices, like integrating distributed modules /applications. 

b. suited for distributed applications

c. more than one consumer for same service
 - like Banks consuming data from Credit Reporting Agency

d. consumers want data in different formats
 - like one consumer(customer) wants in XML format, other would be in JASON ..etc

blocks|key|2528484|text|我想这会帮助你解决你的困惑|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2528485|WEB在行业中有两个主要用例|2528486|企业对消费者(|2528487|+to+consumer，B2C)：每当消费者直接与企业进行交互以满足其需求时，我们总是使用Web应用程序来提供两个企业对企业(B2C)之间的通信:这意味着业务的一部分需要来自另一部分的一些输入/服务。Web-Service总是用来满足企业对企业的需求。通常，消费者从不直接与网络服务交互。我们只与网络应用程序交互，而网络应用程序与网络服务交互以获取信息/数据或进行处理。|ordered-list-item|2528488|2528489|摘自http://coder2design.com/java-interview-questions/|offset|length|2528490|entityMap|0|LINK|mutability|MUTABLE|url|http://coder2design.com/java-interview-questions/^0|0|0|0|0|0|2|1D|0|0^^$0|@$1|2|3|4|5|6|7|V|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|W|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|X|8|@]|9|@]|A|$]]|$1|F|3|G|5|H|7|Y|8|@]|9|@]|A|$]]|$1|I|3|-4|5|6|7|Z|8|@]|9|@]|A|$]]|$1|J|3|K|5|6|7|10|8|@]|9|@$L|11|M|12|1|13]]|A|$]]|$1|N|3|-4|5|6|7|14|8|@]|9|@]|A|$]]]|O|$P|$5|Q|R|S|A|$T|U]]]]

I think this might help you in resolving your confusion

There are two main use cases of WEB in the industry

<ol>
<li>Business to Consumer(B2C) : Whenever there is consumer directly
interacting with the business for its needs we always uses a
Web-Application to provide a communication between two parties.</li>
<li>Business to Business(B2B) : It means one part of the business need
some input/services from another part of the business. Always a
Web-Service is used to meet the business to business requirements.
Usually a consumer never interact with the Web-Services directly we
only interacts with a Web-Application and a Web-Application interact
with a Web-Services for information/data or processing.</li>
</ol>

Taken from <a href="http://coder2design.com/java-interview-questions/" rel="noreferrer">http://coder2design.com/java-interview-questions/</a>

blocks|key|2528507|text|Web服务并不总是有UI。它们通常是使用JSON的API，也可以是SOA类型的，主要使用SOAP和XML，也可以是套接字，以及服务器和其他微型web服务等。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2528508|Web应用程序可以通过多种方式组合在一起。有几种方法可以通过编排多个web服务来创建您的应用程序，并且有一个单独的gui来控制它们，这些gui与这些服务相关联。另一种不使用服务的方法是将代码按程序嵌入到你的UI界面应用程序中，或者更好的是，创建一个面向对象的应用程序，它有自己的服务，稍后在模型中分离，控制器访问，并有自己的图形用户界面视图，在后端访问服务，或者甚至更复杂的应用程序，从一些图形用户界面传递A2B，B2B，B2C服务。|2528509|服务并不总是有一个GUI，它们可以有一个CRUD来维护数据，但是一旦你开始拥有这些类型的特性，它就变成了一个独立的应用程序。这些服务被应用到比它们本身更大的东西上。此应用程序创建您的应用程序。它必须有一个目的。通常情况下，需要多个盲人服务才能完成您的应用程序，并且存在某种接口。|2528510|如果你只是盲目地向你的服务发送一个uri请求，然后它盲目地返回json，那就是一个服务。什么是盲目发送这个？如果是你，那就不是一个应用程序。如果是某种crud，那么它就变成了一个应用程序，crud是一个用于访问服务的GUI，作为一个整体，它是一个数据管理应用系统。现在，如果您在前面放置一个层来以网站的方式演示这些数据，您现在就有了一个产品来显示这些数据，一个产品来管理它，数据是真正的产品，并且可以通过web服务访问，它现在是一个完整的应用程序。您为创建此应用程序所做的努力将成为您的应用程序。|2528511|entityMap^0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|J|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|K|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|L|8|@]|9|@]|A|$]]|$1|F|3|G|5|6|7|M|8|@]|9|@]|A|$]]|$1|H|3|-4|5|6|7|N|8|@]|9|@]|A|$]]]|I|$]]

Web services dont always have a UI. They are normally API's using JSON, can also be SOA type using SOAP and XML primarily, can also be sockets, and servers and other micro web services, etc.. 

Web applications can be put together many ways. There are several ways to create your application by orchestration of multiple web services, and a separate gui to control them which ties into these services. The other way which does not use services is to procedurally embed code into your UI interface app, or even better, make an Object Oriented application which has its own services separed in the Model later, which the controller access, and has its own view as a GUI which access the services in the back end, or even more complicated apps that pass A2B, B2B, B2C services from some GUI. 

Services dont always have a GUI, they can have a CRUD to maintain the data, but once you start to have these types of features, it becomes an application in its own right. The services are applied to something greater than themselves. this applying creates your application. It has to have a purpose. Normally it takes more than one blind service to complete your applicatoin, and there is some kind of interface. 

If you just blindly send a uri request to your service, and it blindly sends back json, that's a service. Whats blindly sending this? If you, then not an application. If some sort of crud, then its becoming an application, the crud is a GUI for accessing the services, and as a whole, its a data management application system. Now if you put a layer on the front to demonstrate this data in website fashion, you now have a product to display this data, a product to manage it, and the data which is the real product, and which is accessible via the web service, its now a full on application. Your endeavour at creating this becomes your application.

blocks|key|49382|text|我猜想web应用程序与web服务的事实是部署因子比率不同，这意味着web应用程序的部署将被限制(局部)，就像web服务(全局)的情况一样。另外，当我们想到UI透视图时，更好的选择是Web应用程序，但当我们想到编程和数据传输透视图时，则主要针对web服务。Web应用程序需要使用servlets和Spring+mvc等框架。另一方面，如果您想将相同的应用程序部署到多个平台，请通过Rest/Soap实现将其作为web服务，以便web应用程序的行为变为服务。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|49383|总之,|49384|+++WebService+++=

+++++++++++++++++(RestApi/Soap)++++#+added+
+++++++++++++/+++++++++%7C+++++++++\
(client1)---(Web+Application)---(clientN)|code-block|syntax|javascript|49385|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|K|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|L|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|M|8|@]|9|@]|A|$G|H]]|$1|I|3|-4|5|6|7|N|8|@]|9|@]|A|$]]]|J|$]]

I guess the web application vs web service is the fact that the deployment factor ratio vary meaning the deployment of a web application would be limited (locally ) to what as in case of a web service (globally).
Plus, When we think of UI perspective better option is the Web application but when we think of programming and data transfer perspective mainly go for a web service.
Web application requires use of servlets with frameworks like Spring mvc etc. On the other hand, if you want to deploy the same application to multiple platforms make it a web service via Rest/Soap implementations so that the web applications behaviour gets changed to rather a service.

In short,

<pre><code> WebService =

 (RestApi/Soap) # added 
 / | \
(client1)---(Web Application)---(clientN)
</code></pre>

blocks|key|2738269|text|这是了解它的一个简单方法：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2738270|Web应用程序的方式，供人类阅读。它可以通过浏览器访问。|offset|length|style|BOLD|2738271|鉴于|2738272|Web服务的方式为计算机可读。它可以从任何语言或平台访问。|2738273|例如：|2738274|基于Yatra.com(Java的服务)应用传送基于Paypal.com(Python的服务)应用|2738275|entityMap^0|0|0|8|0|0|0|6|0|0|2|9|Q|A|0^^$0|@$1|2|3|4|5|6|7|R|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|S|8|@$D|T|E|U|F|G]]|9|@]|A|$]]|$1|H|3|I|5|6|7|V|8|@]|9|@]|A|$]]|$1|J|3|K|5|6|7|W|8|@$D|X|E|Y|F|G]]|9|@]|A|$]]|$1|L|3|M|5|6|7|Z|8|@]|9|@]|A|$]]|$1|N|3|O|5|6|7|10|8|@$D|11|E|12|F|G]|$D|13|E|14|F|G]]|9|@]|A|$]]|$1|P|3|-4|5|6|7|15|8|@]|9|@]|A|$]]]|Q|$]]

This is a simple way to know about it:

Web Application means for human beign can read. 
it is accessed through browsers.

Whereas 

Web Services means for computers can read. 
it is accessed from any languages or platform.

For example:

Yatra.com(Java based services) application communicate Paypal.com(Python based services) application

I know this is an old question and must have been answered hundred times already, but I am not able to find a satisfactory response as yet.

I am creating an application which will be used by other applications (mobile/ web) to fetch the data. Now I have 2 options:

<ol>
<li>Create my application as a simple web application.</li>
<li>Create a web service.</li>
</ol>

A web service looks more sophisticated where any client will provide the data in a specified format (SOAP/ REST) and my app will parse the request and return the data asked by client. How the data will be used is not my app's problem.

My question is that same can be achieved by a simple web app accepting the request in XML format and responding with an XML response. Gut feeling is that a web service will be a better way to go for this kind of service where we are not sure who all will be using it. But are there any specific advantages of using a web service over a simple web app?

Web Service vs Web Application

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

我知道这是一个老生常谈的问题，肯定已回答了上百次，但我至今仍未能找到满意的答案。我正在创建一个应用程序，该应用程序将被其他应用程序(移动/ web)用来获取数据。现在我有两个选择：将我的应用程序创建为简单的web application.Create web服务。web服务看起来更复杂，任何客户端都将以指定的格式(SO...

问Web服务与Web应用程序
EN

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问Web服务与Web应用程序EN

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问Web服务与Web应用程序
EN