REVIEW PAPER ON PERFORMANCE OF RESTFUL WEB SERVICES

Transcription

1 REVIEW PAPER ON PERFORMANCE OF RESTFUL WEB SERVICES Miss.Monali K.Narse 1,Chaitali S.Suratkar 2, Isha M.Shirbhate 3 1 B.E, I.T, JDIET, Yavatmal, Maharashtra, India, monalinarse9990@gmail.com 2 Assistant Prof, I.T,JDIET,Yavatmal,Maharashtra,India, chaitali.suratkar61@gmail.com 3 B.E, I.T, JDIET, Yavatmal, Maharashtra, India, shirbhate.isha@gmail.com ABSTRACT Web services are refers to the technologies that allow for making connection. Web services applications exchange authentication or arithmetic services. In this paper we talk about REST architecture and service selection which consist of Selecting a service algorithm for web services. Communication and information technologies are designed in the direction of support and predict the long-lasting changes of the information society, while new economic, social and cultural dimensions. Here we present a draw near to design and validate RESTful composite web services. Web services are moving towards mobile world as a new rising technology for applications communication. Smart web services and mobile device are becoming well-liked.to exchange information among the application in standard way is the main aim of web services. Mobile devices are physically low processor speed, limited memory, limited battery, constrained devices and slow intermit wireless connection. These types of communication between the applications are based on REST principle. To overcome this type of problem the RESTful architecture is used. REST is a lightweight, easy and better choice. In this paper performance of RESTful web services based on different metric for Mobile environment is taken into consideration. Keywords: MOBILE WEB SERVIC, RESTFUL, SOAP INTRODUCTION There were technologies such as common Request Broker Architecture (CORBA), Remote Method Invocation (RMI) and Distributed Component Object Model (DCOM), these was used to create client and server applications. Web services have machine-readable interfaces that create the task of communicating data between machines to reduce time and human efforts. Set of standards and programming methods for sharing data between different software applications, moreover Web services is a standardized way to distribute services on the Internet. Web platform, the operating system, and the programming language. So distributed functionalities, which may be running on different hardware platforms, may be operating in distinct operating systems, or may be written in different programming languages, can communicate through web Service interfaces. REST architectural style aims at producing scalable and extensible web services using technologies that play well with the existing tools and infrastructure of the internet these are used in highly coupled distributed systems, in which both server and client are dependent on each other. Compatibility and security problems arise when we use these technologies. This kind of traffic will block by firewall and proxy servers. Highly coupled systems are mostly used for intranet applications because platform and technology used is already known or same on both server and client side [1]. REST principles are suitable for open communities that allowed RESTful applications to decouple clients from servers where each side can progress independent from another services. The Simple Object Access Protocol (SOAP) is defined in XML. Since it is based on text and self-describing, SOAP messages can express data between services in heterogeneous computing environments without worrying about conversion problems, t here are many other Web Service specifications. Different web services published over the internet can be composed to form a composite web service such that the composed web service fulfils new service goals using the functionality of partner web services. Automated systems, for example hotel reservation systems, are often built as stateful composite services that require a certain sequence of method invocations that must be followed in order to fulfil service goals. Designing and developing such stateful composite services with REST features is not a trivial task and requires rigorous

2 approaches that are capable of creating reliable web services. The distributed computing systems become more and more important in the new world dominated by the Information Technologies. This has resulted in recent standardization effort of distributed computing architecture, which is known as Service Oriented Architecture (SOA). The main component of this architecture is the Web Service. 1.1 Model of Mobile Application Using Web REST Services we have proposed an Android mobile client that uses REST services in instruct to obtain information about the phone calls for a company that has many mobile devices. The mobile application must meet economical conditions and technical requirements: It covers many mobile device types, run-ning at least Android 2.3.3; The authentication of the same screen of companies, divisions and simple users; access to available reports for each user, depending on the selected reporting peri-od; The data are viewing as graphs The data are viewing the messages. Fig-1: The sections of the application To perform these functions, we divide the application into 5 sections: Reports - reports can be viewed here; Charts - to view graphs; Messages - for viewing messages The data presented by the mobile application is through the REST web services offered by the web application. We used the technique described in [1] and we add some new fea-tures in order to meet the requirements de-scribed in [1]; this involves calling a web service through an Android service that does not block the user interface. There are many advantages of using a service, among which the most important are the following:

3 We can start the services from different parts of an android application, including other services or Broadcast Receivers; the service does not block the user inter-face, making it ideal for operations that take place on a longer time period. Thus in this application all calls to web ser-vices will follow the following pattern: Activity Fragment Services Frag-ment Activity. The service that was creat-ed extends IntentService class in a new thread by calling the sent web service parameters. 2. SERVICE SELECTION In contrast to the task of composing Web services the selection of the right services strongly depends on the costs of a specific service or the objects or meta-data that a service can give. For instance there may be a variety of services informative the location of certain uniqueness, but at different costs or with different accuracy. The same applies for more composite service like e.g. flight booking, where a user has to know if the service offers a certain flight that satisfy his or her requirements, before using the service. Therefore two aspects are essential for service selection Which is: The service has to: be generally able to achieve the needed task offer the specific object/data the user is interested in Thus users first have to question all probable services that usually perform their task, if they will also suit their specific require. Considering that a set of services has been discovered, we will present the best quality for each specific user. We will first revisit our appealing example, then state the algorithm and perform a test interface. Assume that our user Michael has to book a flight from California for his business trip to Boston. Since the business meeting starts at 3 p.m. on the 10th of November, he has to reach destination till noon to have some time left to get to the business site. Besides, he wants to fly business class. Let us think how this algorithm works progress our example: Michael desires to book a flight. First we have to find out all unlike services that allow performing the task of booking a flight and check, if flights meeting Michael's criteria are accessible (step 1). A keyword search on service metaphors might result in a list of four services for flight booking given in table 1.

4 Table-1: Discovered Services for Flight Booking The next step is arrangement out what limits are necessary to guarantee the observance of the hard constraints (step 2). Since our query specifies leaving, coming, coming date and class, we have to discard the Air Travel financial system service, as class input limits provided. Step 3 for supplementary limits past the hard constraints and gets leaving date, airline, cost and non-stop. Now in step 4 Michael's summary knowledge has to be queried for preferences with respect to these additional limits and reveals that Michael generally uses to fly Delta Airlines and prefers non-stop flights. Some general preferences from the domain could also be applied like "everyone prefers a short travelling time". However, because it is a industry trip, we may get no data regarding preferred prices from Michael. Thus no limit for the value will be given in the queries. 3. ADVANTAGES OF REST STYLE Simplicity: REST client can be accessed from any browser (however, this is only true for GET method. Data design demand requires also the XML wrapper). Lighter on Bandwidth: information on the wire are bare xml elements (not wrapped within the <Envelope><Body> tags). REST application security rules can be setup using the http standards: the administrator (or firewall) can discern the intent of each message by analyzing the HTTP command used in the request. A GET request can forever be considered secure because it can't, by definition, alter any data. 4. DISADVANTAGES OF REST STYLE There is uncommon standard established yet for the official REST service explanation. REST requests (especially GET method) are not appropriate for huge amount of information. REST doesn't wrap all web services principles, like Transactions, Security, Addressing, Trust, and Coordination.

5 5. CONCLUSION Moving towards implementing Web applications that consume a large variety of Web services is the next build-up in application space and the mobile application market is searching for solutions to empower mobile devices with Web services combination while minimizing the existing performance issus In these paper Service Selection are shown. From the above analysis we concluded a RESTful web service is a better alternative than any other web services. And we also shows advantages of restful web service and disadvantages of restful web service. The RESTful web services have better performance than any other alternative web services in wired and wireless communication network. The RESTful web services comprise less message sizes and response time.and also the Selecting a Service algorithm are shown in this paper. They are lightweight, easy and Self-Descriptive. Therefore, RESTful offers a good solution for the popular of implementations, with higher flexibility and lower transparency. REFERENCES [1] Performance Evaluation of RESTful Web Services for Mobile Devices International ArabJournal of e- echnology, Vol. 1, No. 3, January 2010 [2] International Journal of Scientific and Research Publications, Volume 3, Issue 5, May 2013 ISSN Services Based on SOAP and REST Principles [3]Informatica Economică vol.17, no. 2/2013 Web Services in Mobile Applications [4] Informatica Economică vol.14, no.3/2010 Consuming Web Services on Mobile Platforms [5] The Second International Conference on Innovations in Information Technology (IIT 05) AFRAMEWORK FOR PROVIDING MOBILE WEB SERVICES