API Development Research Articles

Best Practices for Designing Scalable REST APIs in Cloud Environments

This research paper explores the best practices for developing scalable Representational State Transfer (REST) APIs in cloud environments. As the demand for robust and high-performance APIs continues to grow, developers face numerous challenges in designing and implementing scalable solutions. This study examines various aspects of API development, including architectural principles, cloud-native technologies, performance optimization techniques, and security considerations. By synthesizing current research and industry practices, this paper provides a comprehensive guide for practitioners and researchers in the field of API development for cloud environments.

Security measures implemented in RESTful API Development

Protecting Application Programming Interfaces (APIs) is crucial for securing sensitive data and ensuring the stability of web applications. This paper examines the effectiveness of key security practices, focusing on token-based authentication and password hashing techniques. It highlights the use of JSON Web Tokens (JWT) for authentication, detailing how JWTs enhance data security by incorporating claims and expiration details to mitigate unauthorized access risks. The paper also covers the application of `bcrypt` for password hashing through the `passlib` library, demonstrating its role in safeguarding user passwords from potential threats. In addition, the research addresses other vital security practices such as managing token storage securely, utilizing OAuth2 for credential exchange, and handling errors with HTTP exceptions. The study further underscores the importance of secure configuration practices, including the management of secret keys and token expiration for session management. Recommendations are also provided for improving API security, including rate limiting, input validation, HTTPS encryption, and CORS policy settings. This analysis aims to offer a comprehensive overview of effective API security measures and their implementation in contemporary web development. The security measures in place include Token-Based Authentication using JSON Web Tokens (JWT) to ensure secure data exchange through tokens, which incorporate claims and expiration dates to minimize unauthorized access. Passwords are protected via `bcrypt` hashing, facilitated by the passlib library, safeguarding user credentials in the event of a security breach. Token management practices emphasize secure storage methods to prevent unauthorized access and misuse. Credential exchange is managed through the OAuth2 Password Flow, adhering to the OAuth2 framework for safe credential handling and access token provision. Error handling is addressed through HTTP exceptions to effectively manage authentication-related issues and uphold error reporting integrity. Additionally, configuration and session management involve stringent key management practices to secure secret keys used for token signing and the establishment of token expiration times to limit their validity period, thus enhancing overall session security.

Smart e-waste management: a revolutionary incentive-driven IoT solution with LPWAN and edge-AI integration for environmental sustainability.

Managing e-waste involves collecting it, extracting valuable metals at low costs, and ensuring environmentally safe disposal. However, monitoring this process has become challenging due to e-waste expansion. With IoT technology like LoRa-LPWAN, pre-collection monitoring becomes more cost-effective. Our paper presents an e-waste collection and recovery system utilizing the LoRa-LPWAN standard, integrating intelligence at the edge and fog layers. The system incentivizes WEEE holders, encouraging participation in the innovative collection process. The city administration oversees this process using innovative trucks, GPS, LoRaWAN, RFID, and BLE technologies. Analysis of IoT performance factors and quantitative assessments (latency and collision probability on LoRa, Sigfox, and NB-IoT) demonstrate the effectiveness of our incentive-driven IoT solution, particularly with LoRa standard and Edge AI integration. Additionally, cost estimates show the advantage of LoRaWAN. Moreover, the proposed IoT-based e-waste management solution promises cost savings, stakeholder trust, and long-term effectiveness through streamlined processes and human resource training. Integration with government databases involves data standardization, API development, security measures, and functionality testing for efficient management.

Utilization of Box Behnken Design for the Development and Evaluation of Luliconazole-loaded Nanoemulgel

Pharmaceutical research is always looking for novel ways to distribute drugs and developing these methods to increase the effectiveness of existing medications. The physicochemical characteristics of the drug determine the dose form. Lipophilic API development is a result of recent discoveries in high-throughput screening. A topical broad-spectrum antifungal agent is luliconazole. Due to its lower water solubility, topical administration is limited, and topical absorption is confined. The stratum corneum’s lipid phase’s solubility of the medication also serves as a rate-limiting step for penetration. Because fungal infections impact the skin’s epidermis, dermis, and deeper layers, medicine administration must be tailored to target high drug concentrations at the layers of the epidermis and dermis

Implementing Continuous Integration and Deployment Strategy: Cloversy.id RESTful API Development

The software development cycle involves testing and deployment stages that can be laborious and time consuming, especially in collaborative projects that involve several developers. Implementing Continuous Integration (CI) and Continuous Delivery (CD) offers a solution to streamline this process. This study presents a case study of the Cloversy.id RESTful API project, highlighting challenges encountered during development and the implementation of a new system using GitHub Actions as the DevOps tool. The research resulted in the adoption of a new system, which replaces the conventional practices previously employed by the Cloversy.id development team. Using flow charts, the study meticulously mapped out the development flow, pinpointing bottlenecks and areas for optimization within the cycle. In particular, the implementation of a CI/CD pipeline resulted in a notable improvement, with a 35% increase in speed for CI and a remarkable 39% enhancement for CD. GitHub Actions played a pivotal role in automating critical tasks, reducing the reliance on manual intervention, and minimizing the dependency on team leaders. The platform's features, including detailed logs and email notifications, empowered team leaders and developers alike to take informed actions swiftly. Furthermore, the study highlights the novelty of integrating CI / CD considering factors such as branching strategy, code review practices, testing methodologies, deployment methods, and infrastructure.

Performance Comparison Between Laravel and ExpressJs Framework Using Apache JMeter

Modern web application development requires selecting an optimal framework to ensure maximum efficiency and performance. This research compares two leading frameworks, Laravel (using PHP) and Express.js (using JavaScript), in the context of building RESTful APIs. The purpose of this research is to compare the performance of Laravel and Express.js through performance testing, with a focus on the API response to student data access in the MySQL database. The research method used is performance testing which involves realistic test scenarios and performance metrics such as response time. The research results provide a deep understanding of the performance advantages and disadvantages of Laravel and Express.js in API development. This research helps developers choose a framework that suits project needs, considering efficiency and speed in developing RESTful APIs. The test results show the superiority of the Laravel framework with an average response time of 1745.7 ms faster than Express.js. This Laravel is better suited for applications with high concurrent user access, while Express.js is a good choice for applications with a lower number of simulated users. Framework selection must consider both response speed and specific application needs and consider the specifications of the server used. The implication of this research can help developers optimize web application development, increase efficiency, and ensure maximum performance according to the project goals

API development for an online store

The article examines contemporary approaches to developing online stores, with a primary focus on crafting APIs to ensure the effective operation of the store in the online realm. A survey of prevalent solutions and literature in the field has enabled the identification of key challenges and unresolved issues. Through the analysis, it was discerned that many small online stores encounter speed and scaling issues attributed to non-optimized API development. The article underscores the significance of leveraging modern technologies, such as Node.js, JavaScript, and PostgreSQL, to streamline development and enhance productivity. The article outlines the work's objective—creating an efficient API for an online store—and defines the research task. It elucidates the importance of utilizing Node.js, JavaScript, and other tools to secure endpoints with Guards, thereby improving system security and reliability. In the Development Environment and Tooling section, a range of tools, including JavaScript, Node.js, Nest.js, PostgreSQL, Git, and WebStorm, are detailed for implementing the online store's API. Emphasis is placed on how these tools contribute to ensuring system reliability and speed. The adoption of the Nest.js framework is highlighted as pivotal in crafting a secure and efficient API for the online store. The incorporation of Guards effectively segregates controllers and provides robust protection for endpoints. Consequently, this integration has simplified the enhancement of the store's functionality, rendering it more reliable and flexible for future developments.

Application of BIM to Rebar Modeling of a Variable Section Column

A planar construction drawing is usually used to guide the construction of reinforced concrete structures in the construction industry. Due to a lack of effective technical methods, the accuracy of rebar engineering lofting is insufficient. The rejection rate of rebar is high, which results in high processing costs. Under the background of intelligent construction and BIM technology, the prefabricated factory adopts an automatic production mode to concentrate on steel bar processing, which improves production quality and processing efficiency and reduces production costs. Based on Revit secondary development, using the C# programming language, combined with the Revit API development interface, an automatic 3D modeling plugin for a reinforced concrete variable cross-section column is developed. The BIM model of steel bars is quickly generated, and the engineering quantity of steel bars is automatically calculated, which saves time for the designer to build the BIM model. It is conducive to the automatic assembly and intelligent construction of reinforced concrete engineering, which promotes the information and intelligent development of reinforced concrete structure construction.

How to Develop Organometallic Catalytic Reactions in the Pharmaceutical Industry

From a careful analysis of the recent literature, it seems clear that many transition-metal-catalyzed processes used in API synthesis are developed without resorting to any kind of kinetic analysis. Even acknowledging that some of these processes were developed for early development projects and did not need to be thoroughly optimized, the lack of kinetic work is surprising. This Perspective suggests that, in addition to the utilization of modern technologies such as high-throughput experimentation (HTE) and classical optimization tools such as Design of Experiments (DOE), a modest level of kinetic analysis is necessary to develop truly effective catalytic reactions. We offer some basic theoretical considerations and suggest some rather simple tools which can be employed to integrate kinetic analysis of catalytic steps into API development.

Blockchain and API Development to Improve Relational Database Integrity and System Interoperability

Technological developments have resulted in a trend of cryptocurrencies that use a technology called blockchain to create and record all transactions made into a digital ledger. Along with the emergence of the trend of cryptocurrencies, this development has also resulted in crimes that hit the digital world, such as data leakage and cyber espionage. This threat can be prevented by applying blockchain technology to the database that has been used. Therefore, we need a system that can facilitate the use of blockchain technology and can process data from an existing relational database into a blockchain-based database. The system developed in this study was built with the FastAPI framework that uses the Python programming language and the React framework that uses the Javascript programming language. This system was tested using Katalon and Wireshark software to perform throughput testing and man-in-the-middle attacks. Evaluation of this system is assessed based on the average throughput time and also the results of Wireshark packet capture. The system designed in this research is expected to help overcome interoperability problems when using blockchain and improve relational database integrity. The results of the test show that the system is safe from man-in-the-middle attacks while sending data through API and has a faster throughput time than BigchainDB system by 4.151 seconds.

PENGEMBANGAN REST API UNTUK INFORMASI PASAR TRADISIONAL DI KOTA YOGYAKARTA DENGAN METODE INCREMENTAL

Traditional markets in the city of Yogyakarta offer many unique things for both locals and tourists. There has yet to be an effort to centralise information on traditional markets which highlights its characteristics, including its uniqueness. Through this study, we designed a REST API that provides a service to access information on traditional markets in the city of Yogyakarta. The information available includes class, alternative names, location, description, history, facts, facilities, uniqueness, photos, and stalls. This service can be used by governments or other parties through external applications ensuring data accuracy. We used an incremental approach made of three iterations. Each iteration consisted of needs analysis, system design, API development, and testing and evaluation. This approach provided a more focused and targeted development based on the functional needs of each iteration. Each iteration was tested both on Postman and a web application. The result of this REST API is a JavaScript Object Notation (JSON) which can be easily processed by external applications.

API Development Increases Access to Shared Computing Resources at Boston University.

Within the last few decades, increases in computational resources have contributed enormously to the progress of science and engineering (S & E). To continue making rapid advancements, the S & E community must be able to access computing resources. One way to provide such resources is through High-Performance Computing (HPC) centers. Many academic research institutions offer their own HPC Centers but struggle to make the computing resources easily accessible and user-friendly. Here we present SHABU, a RESTful Web API framework that enables S & E communities to access resources from Boston University's Shared Computing Center (SCC). The SHABU requirements are derived from the use cases described in this work.

API-led Connectivity Using Mulesoft For Healthcare

The API-led business model is a new way of thinking about how to engage with partners and customers through APIs. The traditional approaches were designed for business use cases having limited endpoints and speed of delivery is not critical. Traditional approaches include P2P and E2E. To overcome these drawbacks, a new approach of API-led connectivity is used. The primary aim of API-led connectivity is to allow the integration flows to be reused by means of many events and to be reused within the integration platform. This paper focuses on creating an API- led network which is agile, reusable, and fits business requirements. This network will be built for the health care system using Allscripts and Fitbit APIs. To implement API -led networks in this paper MuleSoft platform is used and API is built using the API development cycle. Depending on the business requirements on the search for API and connector already present on Anypoint App exchange. Using available component flow is created to connect EHR system systems and different devices like Fitbit. Both API are protected with OAuth 2.0 which is handled with a separate flow for initiating the communication between the system and source API. After doing the required transformation to data fetch from source API data is pushed to the Salesforce object. Using different services provided by Mulesoft, an API-led network was built in which EHR and the Fitbit device were integrated. As this development process followed agile behavior it helped in meeting business requirements for building networks. The data was successfully fetched, processed, and transferred from the EHR system and the Fitbit device to the Salesforce object.

Characterization, in vitro dissolution, and pharmacokinetics of different batches of efavirenz raw materials

Objective To perform the solid-state characterization and the in vitro-in vivo correlation (IVIVC) of three batches of efavirenz (EFV) active pharmaceutical ingredients. Significance EFV is an effective anti-HIV drug. Due to the poor aqueous solubility, the rate and extent of EFV absorption deeply depend on its dissolution characteristics. Methods Thermal analyses, x-ray diffraction, and particle size distribution were performed. The saturation solubility and dissolution profiles were assessed in 0.5% (w/v) sodium lauryl sulfate (SLS), fasted-state simulated intestinal fluid (FaSSIF), and fed-state simulated intestinal fluid (FeSSIF) using a flow-through cell. Each batch was orally administered to Wistar rats and the pharmacokinetic parameters were correlated with those obtained from in vitro dissolution. Results All batches of EFV consisted polymorph I. EFV-A presented the lowest particle size distribution [d(v,0.5) = 197.8 µm; d(v,0.9) = 444.6 µm] followed by EFV-B [d(v,0.5) = 223.9 µm; d(v,0.9) = 481.1 µm], and EFV-C [d(v,0.5) = 240.8 µm; d(v,0.9) = 497.3 µm]. The saturated solubility in FaSSIF was 36% and 40% of that in FeSSIF and SLS, respectively. EFV-A presented the fastest rate and largest extension of dissolution than EFV-B and C (79.15%, 69.93% and 54.22%, respectively, as well as the highest maximum plasma concentration. Levels B, C, and multiple-C of IVIVC models were achieved. Conclusion The FaSSIF medium discriminated the dissolution profiles of EFV APIs. Small differences in particle size distribution had a significant impact on the biopharmaceutical parameters of EFV, suggesting that strict control of such parameter is an important aspect during API development and drug formulation.

Development of API Middleware and Mobile Application for a Job marketplace by Using RESTful API and Mobile Development Framework

The research is conducted based on the nationwide goals of Indonesia proposed in the Nawacita document, where one of the big goals is to improve the human resource greatly. Providing a good medium such as a job marketplace can be part of improving the human resource. Since most of Indonesian citizen nowadays has easy access to internet, which can ease their way of using a job marketplace application. Creating a job marketplace application may minimize a number of unemployment in Indonesia. Addition to that, through a focus group discussion, it has been discovered that respondents find job marketplace such as JobStreet and Indeed jobs does not satisfy respondents’ UI and UX view towards the application. The objective of this research is to create a job marketplace mobile application that is useful and easy to use for users. The prototype mobile application is developed using react native, and a middleware that is developed using Express JS is made alongside to bridge data to the mobile application. To assess the prototype mobile application, two evaluation method is used which is User Experience Questionnaire (UEQ) and Questionnaire User Interface Satisfaction (QUIS). 6 respondents were allowed to examine prototype application, and answer the questionnaire. The result of the evaluation both shows positive results from both questionnaires.

Actor concurrency bugs: a comprehensive study on symptoms, root causes, API usages, and differences

Actor concurrency is becoming increasingly important in the development of real-world software systems. Although actor concurrency may be less susceptible to some multithreaded concurrency bugs, such as low-level data races and deadlocks, it comes with its own bugs that may be different. However, the fundamental characteristics of actor concurrency bugs, including their symptoms, root causes, API usages, examples, and differences when they come from different sources are still largely unknown. Actor software development can significantly benefit from a comprehensive qualitative and quantitative understanding of these characteristics, which is the focus of this work, to foster better API documentation, development practices, testing, debugging, repairing, and verification frameworks. To conduct this study, we take the following major steps. First, we construct a set of 186 real-world Akka actor bugs from Stack Overflow and GitHub via manual analysis of 3,924 Stack Overflow questions, answers, and comments and 3,315 GitHub commits, messages, original and modified code snippets, issues, and pull requests. Second, we manually study these actor bugs and their fixes to understand and classify their symptoms, root causes, and API usages. Third, we study the differences between the commonalities and distributions of symptoms, root causes, and API usages of our Stack Overflow and GitHub actor bugs. Fourth, we discuss real-world examples of our actor bugs with these symptoms and root causes. Finally, we investigate the relation of our findings with those of previous work and discuss their implications. A few findings of our study are: (1) symptoms of our actor bugs can be classified into five categories, with Error as the most common symptom and Incorrect Exceptions as the least common, (2) root causes of our actor bugs can be classified into ten categories, with Logic as the most common root cause and Untyped Communication as the least common, (3) a small number of Akka API packages are responsible for most of API usages by our actor bugs, and (4) our Stack Overflow and GitHub actor bugs can differ significantly in commonalities and distributions of their symptoms, root causes, and API usages. While some of our findings agree with those of previous work, others sharply contrast.

PRIMENA APIGEE PLATFORME ZA UPRAVLJANJE API-JEM

U ovom radu objašnjeni su osnovni koncepti API menadžmenta i komponente platforme Apigee za upravljanje aplikacionim programskim interfejsima. Prikazana je arhitektura platforme i REST principi na koje se ona oslanja. Predstavljene su najčešće korišćene polise za upravljanje zahtevima, kao i osnovni bezbednosni principi sa akcentom na OAuth framework. Opisani su koncepti deljenih tokova, keširanja i rukovanja greškama i kroz implementaciju rešenja prikazan je rad u okviru platforme za rešavanje problema u praksi.

The Delivery of Flexibility from the Application of QbD to API Development

This paper by IQ consortium member companies will describe how the application of the ICH Q11 vision for enhanced QbD development can lead to flexibility through differentiated outcomes for elements of API manufacture, such as the control strategy and lifecycle change management. Two further articles, in addition to this introductory paper, will present a series of case histories which address such flexibility and exemplify opportunities for the further development of the ICH Q11 vision.

Intensive summer course in robotics – Robotcraft

This paper describes a two-month summer intensive course designed to introduce participants with a hands-on technical craft on robotics and to acquire experience in the low-level details of embedded systems. Attendants started this course with a brief introduction to robotics; learned to draw, design and create a personalized 3D structure for their mobile robotic platform and developed skills in embedded systems. They were familiarize with the practices used in robotics, learning to connect all sensors and actuator, developing a typical application on differential kinematic using Arduino, exploring ROS features under Raspberry Pi environment and Arduino – Raspberry Pi communication. Different paradigms and some real applications and programming were addressed on the topic of Artificial Intelligence. Throughout the course, participants were introduced to programming languages (including Python and C++), advanced programming concepts such as ROS, basic API development, system concepts such as I2C and UART serial interfaces, PWM motor control and sensor fusion to improve robotic navigation and localization. This paper describes not just the concept, layout and methodology used on RobotCraft 2017 but also presents the participants knowledge background and their overall opinions, leading to focus on lessons learned and suggestions for future editions.

Comparative Study of Data Sending Methods for XML and JSON Models

Data exchange between different devices and applications has become a necessity nowadays. Data is no longer stored locally on the device, but in the cloud. In order to communicate with the cloud and exchange data, web services are being used. To keep the communication consistent across different devices and platforms, the data needs to be formatted using a standard data format, such as JSON or XML. This paper compares both standards and provides an in depth analysis of their performance. In order to perform the analysis a web API was built in the PHP framework Laravel, which was then tested with the help of the API development environment called Postman for different number of transferred items.