Computability evaluation of RESTful API using Primitive Recursive Function

New value-added business, generated by Web service composition in BPEL, provides more powerful and flexible features. SOAP-based web services invoked in BPEL are heavy with redundant information and lower performance. RESTful Web service is brought forward to new value-added business as an alternative solution. However, it's a big challenge to compose RESTful Web services with SOAP-based Web Services in SOA BPEL business processes. BPEL is not designed to use RESTful Web services because these types of services do not use WSDL to describe themselves. This paper proposes a novel approach for integrating RESTful Web services and SOAP-based Web services in business processes described in BPEL. The approach is applied to a practical multimedia conference BPEL process, and the experimental data show the stability of the new RESTful BPEL process with a higher performance.

Service Oriented Architecture (SOA) has been widely adopted by industries due to its ability to provide increased interoperability among heterogeneous systems. SOA is realized through web services which can be either based on the style of Remote Procedure call(RPC) and SOAP protocol or on the Representational State Transfer(REST) style and HTTP. RESTful web services are increasingly becoming popular in the industry because of their simplicity, uniform interface, statelessness and cacheability benefits. The ability to efficiently select and integrate appropriate heterogeneous services available on the web dynamically at runtime is essential in the development of the applications based on web services. Whenever a single web service cannot satisfy the functionality required by the user, there should be a possibility to combine several existing services together in order to fulfill the request. This need has triggered a considerable number of research efforts on the composition of web services. Although several works have focused on the composition of SOAP based web services, there has not been adequate effort towards the composition of RESTful services. However, due to the above- mentioned advantages offered by the RESTful web services, it will be beneficial to design an application as a composition of such RESTful services. Towards this objective, this paper investigates two different approaches for composing the REStful web services specifically designed for health care domain, one using the Jopera tool and another using hypermedia.

Novel trends in Web services technology challenge the assumptions made by current standards for process-based service composition. Most RESTful Web service APIs, which do not rely on the Web service description language (WSDL), cannot easily be composed using the BPEL language. In this paper we propose a lightweight BPEL extension to natively support the composition of RESTful Web services using business processes. We also discuss how to expose the execution state of a business process so that it can be manipulated through REST primitives in a controlled way.

RESTful Web service composition with BPEL for REST

REpresentational State Transfer (REST) is considered as one standard software architectural style to build web APIs that can integrate software systems over the internet. However, while connecting systems, RESTful APIs might also break the dependent applications that rely on their services when they introduce breaking changes, e.g., an older version of the API is no longer supported. To warn developers promptly and thus prevent critical impact on downstream applications, a deprecated-removed model should be followed, and deprecation-related information such as alternative approaches should also be listed. While API deprecation analysis as a theme is not new, most existing work focuses on non-web APIs, such as the ones provided by Java and Android.To investigate RESTful API deprecation, we propose a framework called RADA (RESTful API Deprecation Analyzer). RADA is capable of automatically identifying deprecated API elements and analyzing impacted operations from an OpenAPI specification, a machine-readable profile for describing RESTful web service. We apply RADA on 2,224 OpenAPI specifications of 1,368 RESTful APIs collected from APIs.guru, the largest directory of OpenAPI specifications. Based on the data mined by RADA, we perform an empirical study to investigate how the deprecated-removed protocol is followed in RESTful APIs and characterize practices in RESTful API deprecation. The results of our study reveal several severe deprecation-related problems in existing RESTful APIs. Our implementation of RADA and detailed empirical results are publicly available for future intelligent tools that could automatically identify and migrate usage of deprecated RESTful API operations in client code.

Internet is providing the platform for accessing different kinds of services in a distributed and heterogeneous environment. Software components are available on Internet in the form of Web Services. Service Oriented Architecture (SOA) possesses various characteristics by executing Web Services using Simple Object Access Protocol (SOAP). SOAP has certain limitations such as tightly coupled invocation, performance in terms of response data, non-uniform interface and no hyperlink support. These limitations can be resolved by implementing principles of Representational State Transformation (REST). REST is an architectural style implemented by resources known as RESTful Web Services. At present, light-weight RESTful services are dominating the development of services due to simplicity of RESTful architecture. Service access and invocation is simple in RESTful framework as it uses Uniform Resource Identifier (URIs) and Hyperlinks. In this paper, we explore the idea of RESTful Service Mashup by integrating individual Web Services which can satisfy end users' requirements. For this work, we propose a recursive algorithm. The implementation work is on Android 2.2 (froyo), API level 8 and above. It is supported on most of Android based mobile devices.

The need for adaptability in software is growing, driven in part by the emergence of autonomic computing. In many cases, it is desirable to enhance existing programs with adaptive behavior, enabling them to execute effectively in dynamic environments. Existing web service invocation and adaptation mechanisms are limited only to the scope of web service choreography in terms of web service selection. Such a scope hardly leaves ground for a participating service in a choreographed flow to re-adjust itself in terms of changed non functional expectations. In this paper we used Aspect oriented programming (AOP) to invoke Web Services (WS) and Representational State Transfer (REST) web services and to enable dynamic adaptation in existing programs. We propose an approach to implement dynamic adaptability especially in Aspect weaving at the time invoking web services and REST web service. We have used AspectJ; Java based language to create aspects in Eclipse supported framework.

S2O: A smart objects orchestrator framework based on the web of things

Computer computer-based information systems at an institution are often built in stages and separately. Data integration between subsystems is not well connected. The results in differences in the data structures or the number of records between one subsystem and another so that the data presented is not aligned. This study aims to design and implement a RESTful Web Service so that other information subsystems can use employee data from the Management Information System. The four stages in this research are observing the information system currently running, analyzing the data integration needs, designing and coding the RESTful Web Service API, implementing and testing the response time.

Semantic annotation of Web Services has emerged as an efficient solution to automatic service discovery, composition, invocation and interoperation tasks. In this paper a three-level automated semantic classification mechanism of SOAP and Restful Web Services is examined by taking into account the textual description of Web Services. The proposed approach provides a mechanism for categorizing any Web Service into application domains, prototype operations and prototype i/o into the predefined ontology. The effectiveness of the proposed methods is validated through extensive experiments.

The NERSC Web Toolkit (NEWT) brings High Performance Computing (HPC) to the web through easy to write web applications. Our work seeks to make HPC resources more accessible and useful to scientists who are more comfortable with the web than they are with command line interfaces. The effort required to get a fully functioning web application is decreasing, thanks to Web 2.0 standards and protocols such as AJAX, HTML5, JSON and REST. We believe HPC can speak the same language as the web, by leveraging these technologies to interface with existing grid technologies. NEWT presents computational and data resources through simple transactions against URIs. In this paper we describe our approach to building web applications for science using a RESTful web service. We present the NEWT web service and describe how it can be used to access HPC resources in a web browser environment using AJAX and JSON. We discuss our REST API for NEWT, and address specific challenges in integrating a heterogeneous collection of backend resources under a single web service. We provide examples of client side applications that leverage NEWT to access resources directly in the web browser. The goal of this effort is to create a model whereby HPC becomes easily accessible through the web, allowing users to interact with their scientific computing, data and applications entirely through such web interfaces.

The Business Process Execution Language (BPEL) has become the standard in Web service composition, so that been adopted by industries to create mission critical services. The business process reliability especially business process consistency when some services failed is critical to composite services especially involving various organizations. However, it is difficult to conduct business process reliability testing for composite services due to complex business process in service composition, remote deployed services and long time testing duration. Little research is done to test fault tolerance capabilities of composite services only from low level. This paper proposes a technique on how to test the reliability of composite service defined in BPEL from the view of business semantics with little cost using fault injection. We present an approach for reliability testing of web services by using service stubs with semantic faults instead of real services which can be placed at service provider side or service consumer side. Dislike existing studies, we focus on how to find the reliability problems associating with business process - called semantics as the problems are not pure coding error but faults related to business process. In addition, the behavior of composite services in BPEL is analyzed when there are faults in orchestrated services invoked. Finally, a case study is given to show the whole process of reliability testing for composite web service.

Today, REST APIs have established as a means for realizing distributed systems and are supposed to gain even more importance in the context of Cloud Computing, Internet of Things, and Microservices. Nevertheless, many existing REST APIs are known to be not well-designed, resulting in the absence of desirable quality attributes that truly RESTful systems entail. Although existing analysis show, that many REST APIs are not fully REST compliant, it is still an open issue how to improve this deficit and where to start. In this work, we introduce a framework for the structural analysis of REST APIs based on their description documents, as this allows for a comprehensive, well-structured analysis approach that also includes analyzing the corresponding API description languages. A first validation builds on a set of 286 real world API descriptions available as Swagger documents, and comprises their transformation into a canonical metamodel for REST APIs as well as a metrics-based analysis and discussion of their structural characteristics with respect to compliance with the REST architectural style.

In the fast-evolving software market, the demand for rapid development of digital solutions, especially prototypes and MVPs, is increasing. Creating a functional backend requires skilled developers, adding costs and extending timelines, even for early-stage projects. This underscores the need for automated backend deployment tools, especially for startups and smaller teams. Building RESTful APIs, essential for most software products, demands expertise in server architecture, database management, and security. Current technology offers partial solutions through tools like Node.js, RethinkDB, Nginx, and JWT for secure data exchange, yet integrating these into a cohesive, low-maintenance system that adapts dynamically to client-side demands remains challenging. This research proposes an automated backend software solution that enables rapid, low-cost server deployment tailored for MVPs and scalable applications. The system allows users to specify only database and table names; fields are dynamically created and indexed upon receiving POST requests, ensuring high performance. An integrated React-based administrative panel facilitates user management and secure, multi-client access, enabling flexible, multi-tenant usage on a single infrastructure. This solution minimizes backend development costs, optimizes database performance, and lays the groundwork for future automated backend solutions that accelerate product deployment. Formulation of the problem. Modern development demands efficient creation of RESTful backend services with minimal time and resource investment, especially for prototypes and MVPs. Companies and teams often need to hire skilled developers even for basic server logic, increasing development costs. Automating backend infrastructure deployment has become crucial to expedite product release and optimize expenses. Target. To create automated software for backend server development that enables users to easily deploy REST API services. The system should include adaptive database and table structure creation, automatic data indexing for high performance, and an administrative panel for managing requests and databases. Results. A server based on Node.js and RethinkDB was developed, supporting JWT authentication and integrated with an administrative panel built with React and React-Admin. Users only need to specify the database and table names, and the server then automatically adapts and indexes fields upon receiving POST requests, ensuring high query processing performance. With automatic indexing and flexible table handling, this system is suitable for both MVPs and high-load products. Practical significance. This automation system significantly reduces the time and costs required to establish backend infrastructure, making it valuable for small teams and startups. Its high performance and flexibility provide an effective solution for long-term operation under high loads, giving users a universal and powerful tool for backend application deployment.

Data is one of the most important things in this information and information technology era that evolving now. Currently, the government still has not used the public data maximally for administrative purposes. Utilization of this big population data is the creation of a web service application system with REST API where this data will be open and accessible to those who have access. One of the institutions that use this service is the Manpower and Transmigration Service where this system can make the Dinas staff more efficient to create and register job search cards using available community data. This application is able to provide and facilitate many parties, such as data administrators to monitor data usage, registration employee in input data, and people able to register independently.
 Index Terms—Web service, API, Rest api, People data