Fig 1 - available via license: Creative Commons Attribution 4.0 International
Content may be subject to copyright.
Source publication
The paper describes the implementation of organic benchmarks for Java EE and ASP.NET Core, which are used to compare the performance characteristics of the language runtimes. The benchmarks are created as REST services, which process data in the JSON format. The ASP.NET Core implementation utilises the Kestrel web server, while the Java EE implemen...
Contexts in source publication
Context 1
... Java APIs to provide features, which are useful in an enterprise setting, such as dependency injection (CDI, EJB), transaction management (JTA) and dynamic webpage functionality (JSP, JSF), as well as features for creating web services (JAX-RS, JAX-WS), at the same time also shortening the development time and the software complexity ( Fig. 1) [6]. The development is organised with the Java Community Process (JCP) and based on Java Specification Requests ...
Context 2
... TESTING APIS The communication between the back-end and the APIs to be tested varies more as there is not a unified data format, differences existing from one benchmark to the next; however, they share a common lifecycle (Fig. 11). The test execution is implemented with the ES6 async and Promise functionality, which allow for parallelisation of iterations, depending on the parameters set in the front-end. As soon as a response from the API is received, it is logged to Redis and that iteration is forgotten apart from it. Fig. 7. A diagram of network requests and ...
Context 3
... can be explained with the hardware constraints (the amount of RAM available to the servers) causing the API runtime to be terminated by the operating system, after exhausting all of the available resources (Fig. 12). While the implementations of the StringBuilder concept, provided by the standard libraries, were used in both implementations, for both Java and ASP.NET Core, it appeared that ASP.NET Core's usage of memory was slightly less optimised; therefore, it could not successfully run the tests with the resources provided. This behaviour was ...
Similar publications
his research aimed to develop an information system supporting research on rubber (ISSR) in Thailand. This system was designed as a web application with responsive web design. The rubber database was developed with MySQL, used Apache Server as a Web Server and programed with PHP-script. High Chart, Google Chart API and Java Technology were used to...
Citations
... Similarly, various research efforts have attempted to compare performance across diverse technologies. Yet, they, too, have faced the limitation of needing a comprehensive test suite adaptable to various scenarios or technological environments [6][7][8]. ...
Application Programming Interfaces (APIs) are available in virtually every programming language. These interfaces make it easier to develop software by simplifying complex code into a more straightforward, manageable structure. APIs provide a standardized interface that allows different applications to communicate and connect easily, streamlining the software development process and making it more efficient and effective. Performance testing of a web API refers to evaluating the performance characteristics of an API accessible via the web. This process involves analyzing performance aspects such as response time, reliability, scalability, and resource utilization. This work defines a test battery using specific open-source tools to assess Web API performance. The tests used are load, stress, spike, and soak tests replicating various scenarios of the volume of users accessing the service or simulating a denial-of-service attack. These tests aim to determine how well an API can manage a substantial volume of traffic and transactions while upholding satisfactory performance standards. Applying Web API performance testing will also enable organizations to implement suitable measures for enhancing performance and guaranteeing smooth user interaction, pinpointing bottlenecks, constraints, or prospective problems in the API’s architecture and execution. These tests can also demonstrate the technology’s limitations and benchmarking, helping determine a more suitable production platform.
... W artykule postawiono hipotezę badawczą, że technologia Express zapewnia wydajniejsze rozwiązanie do tworzenia REST API niż Spring. [5]. Autorzy zwrócili uwagę na istotność niezmienności środowiska testowego przez cały okres przeprowadzania eksperymentu, dlatego aplikacje zostały wdrożone na serwer VPS (ang. ...
The purpose of this article is a comparative analysis of two technologies for building applications in REST architecture. A Java-based development framework - Spring, and a framework designed for JavaScript language and Node environment - Express.js were analyzed. The test application was designed and implemented in both studied technologies. Using the Apache JMeter tool, HTTP request processing times were measured by operating on simple text data. The experiment was based on 5 scenarios repeated for a different number of users in the range of 10 to 100, with a constant number of executed requests to the server. The analysis conducted showed that the application implemented in Express.js handles HTTP requests up to 249% more efficiently than its counterpart in Spring.
... If the database is overloaded at the time when the background service needs to be executed, the background service monitors the database load and executes the query when the database load falls below a certain value. The data is then compared, and if the cache contains the outdated data, the background service refreshes the cache [12]. Caches must be able to quickly return the result when they are overloaded, so it is a challenge for the development teams to find a cache system that can respond to the high workload of their applications. ...
... A direct comparison study often offers crucial insights that may help to choose one technology over the other. For example, there are a number of studies that assess the performance of Java EE with ASP.NET (Kronis and Uhanova, 2018;Hamed and Kafri, 2009;Hamed, 2009). However, studies that compare the performance of ASP.NET Core with Node.js are scarce and authors are not aware of any of them published in literature to date. ...
... The overall performance of both technologies is similar and comparable, none of them is significantly faster or slower [6]. As both technologies are open source, they support various third-party frameworks. ...
Many existing web portals make the learning of children and preparations of teachers easier, however, only few of them combine all desired functionalities. For this reason, an education information portal is being developed with the application of modern architectural patterns, the utilization of a microservices architecture and the ASP .NET Core framework.
In recent years, with the rapid development of information technology, the combination of mobile communication and Internet technology appears in all walks of life. The concept of smart city has gradually entered the daily life of community residents. Smart city is a new concept proposed by combining Internet of Things, cloud computing and mobile Internet technologies to achieve a safe, comfortable, convenient and efficient living experience. By investigating the current actual situation of smart city, this paper analyzes some specific requirements and overall development direction of smart city, and makes a detailed analysis of the functional requirements of the system. A smart city management system based on Java programming language and B/S architecture is designed. The design of the back-end management terminal of the system is based on B/S architecture and adopts the MVC framework. The whole system is divided into three basic levels: interface display layer, logical control layer, data access and data model layer. Through the lightweight Web container management work provided by the framework to achieve the management of smart city, greatly improve the management efficiency of managers. This paper conducts a pressure test on the smart city management system, and the test results show that both the system concurrency and the system resource occupation can meet the daily use requirements.KeywordsComputer applicationSmart cityManagement systemMVC pattern
