International Journal of Computer Applications (0975 – 8887) Volume 158 – No 4, January 2017 20 An Appraisal of Web Applications vs. Web Services with respect to Performance Engineering using Software Performance Engineering Approach Ch. Ram Mohan Reddy Research scholar M S Ramaiah Institute of Technology, Bangalore – 54 India D. Evangelin Geetha M S Ramaiah Institute of Technology, Bangalore – 54 India T. V. Suresh Kumar M S Ramaiah Institute of Technology, Bangalore – 54 India ABSTRACT Web Applications (WA) and Web Services (WS) are emerging as predominating technologies ineffectively usefulness in distributed/service oriented systems. These systems present the challenges for achieving the quality of service (QoS). The Quality of Service can be measured by how well the systems are responding to the customers. The performance of these systems from the user point of view is to be estimated, and appropriate measures have to be taken if the objectives are not being met. At the foremost, a feasibility study needs to be done and correlated to technical and environmental factors. The present paper explains how to consider these factors in assessing the performance of different categories of WA vs. WS. It is illustrated by modeling deployment diagram for web application and web services and also by presenting macro and micro flow diagrams. Keywords Web Services, Web Applications, Technical Factors, UML, Software Performance Engineering 1. INTRODUCTION With the increase in the internet usability and availability on any device, everybody can access the internet with the help of devices ranging from mobiles to computers. Anybody who has a basic smart mobile device can access the internet with ease. This is the reason many companies/businesses try to develop web based applications which will increase the usability of the application by a wide spectrum of people across the globe. A company that has a solution for a problem prefers to develop it as a Web-based application or simply Web Application. These application programs are very easy to develop as there are many frameworks that help in the development of a Web Application within no time. Moreover, these Web Applications are user friendly. Some services are used for general purposes by all the Web Applications. These specifications help in the incorporation of setting certain standards for some web services. These services are general and provide the information about the network being used and different protocols used in the communication process when the user tries to access a Web Application. The components described are operated out using the standards like Web Service Description Language (WSDL), Simple Object Access Protocol API (SOAP) and Universal Description, Discovery and Integration API (UDDI) respectively [10]. The Web Application is for the user so it should have a Graphical User Interface that helps the user in effectively interacting with the software and it also has to have an interface for the web service according to the standards so that the web service provided can help the Web Application work properly as was intended. Figure 1 shows the intricate working of a Web Application and a Web Service using the specified interfaces. Fig. 1 General view of Web service and Web application The three roles that interact with each other to form the basis of a Web Service Architecture are shown in Figure 2. These three roles are Service providers, Service registry, and Service requestor. The Web Applications have software modules with some functionality to support the overall application. These functionalities have to be registered in the service registry of a web service. The service requestor issues the find operation, to the service registry that contains information about the service needed in the service description. The internet is searched for a service provider that provides the same or similar service using the publish operation. These services are the certain general type of services which are identified for all applications trying to incorporate similar services. If a service provider is found, then the developer who needs the web service is bound to the service provider using the bind operation, both exhibiting similar characteristics as they are logical constructs for the same service. Web Application Web service interface Graphical User Interface (GUI)