Web Services is still a quite new technology, and everyone knows how to make full use of them. With my experience (I have built a complete enterprise software product in the Web Services under construction), I found that Web Services has two main purposes: integrate multiple systems together, and use functional functions as a function function. Components are provided to remote calls. This article I will introduce questions that need to pay attention to when using the latter method.
When you want to use Web Service to submit a new function or service to the client that may be called remotely, you need to take into account many factors. Whether this function is used for internal or external customers or collaborators, you start designing a master before you start a new Web Service project in Visual Studio .NET to save you a lot of time. For example, it will make sense to provide a functional function as a web service as a web service when requested to access the exclusive database and / or it is difficult to implement local deployment or cost. Functions used to perform simple calculations do not require access to exclusive data, and is not so complicated in terms of local deployment or maintenance.
When functional functions require a complex installation process or a complex, expensive hardware configuration, using Web Services may be your best choice. In this case, the function function is used as a web service to solve a lot of trouble for your customers because they don't have to deploy it locally. If you often need a new version of a functional function, then you should also consider using Web Services. A Web Service will provide an easy way to release an upgraded version of all customers who use the function function without having to re-deploy it every time a new version is released. The function of providing access to exclusive data is not easy to provide access to the exclusive data through the Web Service interface. In any case, the client needs to get data, and the Web Service is obviously a better way than transmitting a normal file (FLAT file). Finally, it is best to provide functional functions that often change data as Web Services. In updating data speed and changes in data size will make the advantages of remote access exclusive data more obvious.
The deployment problem is the most important factor when you decide whether to provide a functional function as a web service. Web Services makes the software's deployment easier. For example, if you build a guide driving app, you don't need to worry about how to install the map software. Or if you have a functional function that needs to be upgraded, you don't need to return to the company every month, let them help you deploy updates.
I would like to choose Web Services wisely however, you have to understand all aspects of Web Services, and they also have advantages and disadvantages. Of course, before starting your project, you have to confirm that it is more shortcomings. Otherwise, you only need to use the new Web Service where you are in your resume.
For example, a Web Service running in other architectures is not as reliable as running in your own server. Even if the best network protects the most complete and maintenance, it is not completely reliable in certain aspects. You must be able to prove to your customers, whether it is internally or outside, there is a great advantage in Service's deployment and maintenance to make up for the shortcomings of the remote access function in an introverted network. .
I like to use a square root function function to illustrate a typical "error" using the WEB Service example (see Table 1). Although this scene is a bit exaggerated, it can explain the problem. The square root function function does not reflect any advantages provided by Web Service, but the opposite is reflected all of its defects. It is not difficult to deploy it, and it doesn't (at least recently), because it is necessary to make redeployment, so that the Web Services deployment advantage cannot be reflected. Moreover, it does not need to access any database or exclusive data to implement the computing function. However, it does need to send functional function requests to the web server, which will cause Web Service to perform very slow due to its own inherent slow or no network link issues. In this case, a small function like a square root can cause a large application of a large application to stop. When you try to Web Services for the first time, it will try to publish some application functions as Web Services - some functions that translate bitmap into JPEG or compress bitmap data. These functional functions may be very convenient, but they are not suitable for providing Web Services. When the data may be useful to other departments, internal department-to-department (D2D) Web Services may apply to all functional functions, even some functional functions that are difficult to deploy. Web Services provides a great way to quickly efficiently implement the software deployment and maintenance within the company, without having to access Web Services other than the firewall. Because D2D Web Services is running inside your network, this reduces the possibility of the program interrupt due to network issues, and the level of Volume is more easier to predict.
When a department is used to construct a program that needs to access the data controlled by other sectors, the sectors holding these data will set a data output process to transfer a normal file containing the data to the required department, so that they You can import the data into the database. Unfortunately, this extremely inconvenient sharing data method is still very common. Web Services provides a better way to share ordinary file data for internal department data. Web Services is not to transfer raw data over the past to let client programs yourself, but more let you control, which will provide computing capabilities instead of data for calculating. This is not only a more stable information sharing method, but it also provides a mechanism to enhance and data-related business rules.
Although the same method is used, the evaluation of function functions that need to be provided through Web Services to the outside is still very important. The Web Service provided by an external company is more dangerous. However, this hazard will be counted by them with a distribution process across firewalls without having to deploy service, and see Table 2).
Considering the following questions When you recommend a functional function as a web service to your business partner or user, you need to explain whether its advantage is greater than the disadvantage. Consider the answer to these questions will help you:
How high is the function of this function?
How many sensitive data is incoming or outputting Web Service?
What is the data source? How long is it updated? Is it open?
How long have you participated in the new version of this feature?
Who is controlling the architecture of Web Service? Is the architecture reliable?
Web Services has the potential for most IT companies, especially in software deployment, but you can't use it anywhere. You have to avoid it in any meaningless to use the functional function or service to do Web Services. Sometimes it is necessary to deploy locally.
About the Author:
Douglas Kerwin is the founder and president of Metaverse Corporation, which is located in Princeton, N.J., mainly engaged in the Web Content Management software as a service, and its products take Microsoft to the development platform. You can contact him through dkerwin@metaverse.cc.
