An empirical study of multi-threading paradigms Reactive programming vs continuation-passing style

Komolov, Sirojiddin; Askarbekuly, Nursultan; Mazzara, Manuel

doi:10.1145/3418688.3418695

Cited by 3 publications

(2 citation statements)

References 6 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…It appeared that when a carrier thread shares locks with virtual threads it might cause a deadlock situation. To manage access to locks, the JDK uses a queue 12 : a thread that can't access a lock will enqueue itself and wait to be notified by the previous member of the queue that the lock has been released. If both the virtual thread and its carrier are waiting for the same lock and the virtual thread is notified first, it will wake up and will want to resume its computation.…”

Section: Quarkus-virtual-threadsmentioning

confidence: 99%

“…This has led to the development of asynchronous user APIs such as asynchronous callbacks, promises, and reactive streams. However, this paradigm represents a fundamental shift from the traditional synchronous and imperative approach, potentially leading to increased development and maintenance overhead [10,12]. Consequently, mainstream programming languages like Golang, C#, Python, JavaScript, and Java are increasingly emphasizing the provision of asynchronous communication primitives that strike a balance between preserving developer experience and facilitating asynchronous communication effectively.…”

Section: Introductionmentioning

confidence: 99%

See 1 more Smart Citation

Considerations for integrating virtual threads in a Java framework: a Quarkus example in a resource-constrained environment

Navarro

Ponge

Mouël

et al. 2023

Proceedings of the 17th ACM International Conference on Distributed and Event-Based Systems

View full text Add to dashboard Cite

Virtual threads are a highly anticipated feature in the Java world, aiming at improving resource efficiency in the JVM for I/O intensive operations while simplifying developer experience. This feature keeps the traditional thread abstraction and makes it compatible with most of the existing Java applications, allowing developers preferring synchronous imperative abstractions to benefit from better performance without switching to asynchronous and reactive programming models. However, limitations currently hinder the usability of virtual threads. These limitations must be considered when building a piece of software around virtual threads for they might have non-trivial effects. This paper (i) discusses the different strategies envisioned to leverage virtual threads in the Quarkus framework, (ii) gives an overview of the final implementation, (iii) presents the benchmark used to characterize the benefits of using virtual threads in a typical container environment where resources are scarce compared to using Quarkus with traditional thread pools and Quarkus with reactive libraries ; (iv) results are interpreted and discussed. Our study reveals that the integration of virtual threads in Quarkus doesn't perform as well as Quarkus-reactive. This seems to be due to a mismatch between the core hypothesis of Netty and virtual threads regarding the amount of threads available.

show abstract

Section: Quarkus-virtual-threadsmentioning

confidence: 99%

Section: Introductionmentioning

confidence: 99%

Considerations for integrating virtual threads in a Java framework: a Quarkus example in a resource-constrained environment

Navarro

Ponge

Mouël

et al. 2023

Proceedings of the 17th ACM International Conference on Distributed and Event-Based Systems

View full text Add to dashboard Cite

show abstract

Comparative analysis of reactive and imperative approach in Java web application development

Iwanowski¹,

Kozieł²

2022

jcsi

View full text Add to dashboard Cite

The subject of this study was to compare web applications created using the imperative and reactive approaches in Java. For this purpose, two applications with the same functionalities were developed using both approaches. The study looked at the performance, stability and time-consumption of implementation of each application. Based on the obtained results, it was found that the reactive application processes queries faster, uses less CPU, and is more stable in the case of handling many simultaneous requests, where the processing time is greater than 10 seconds. No significant differences were observed in using the computer's RAM by the applications. In addition, the study showed that reactive application takes more time to create.

show abstract

Introductory Programming in Higher Education: A Systematic Literature Review

Rodrigues,

Monteiro,

Osório

2022

View full text Add to dashboard Cite

An empirical study of multi-threading paradigms Reactive programming vs continuation-passing style

Cited by 3 publications

References 6 publications

Considerations for integrating virtual threads in a Java framework: a Quarkus example in a resource-constrained environment

Considerations for integrating virtual threads in a Java framework: a Quarkus example in a resource-constrained environment

Comparative analysis of reactive and imperative approach in Java web application development

Introductory Programming in Higher Education: A Systematic Literature Review

Contact Info

Product

Resources

About