Tagged posts: 'performance'
When Quarkus was first released, the industry was focused on microservices. But Quarkus is just as well suited for large monoliths, whether you're modernizing existing systems or building new ones from scratch. In large applications, build times quickly become a bottleneck, and we've made significant improvements here. Let's discuss these!
This post explores how Quarkus speeds up development, cuts costs, and streamlines cloud-native Java.
This blog post invites you to discover how Quarkus can help your company cut costs, streamline development, and modernize your Java stack for today’s cloud-native world.
By
Leveraging Quarkus build-time metaprogramming capabilities to improve Jackson's serialization performance
By
By carefully fixing and designing a performance test to ensure that only Quarkus is being stressed, throughput improves from 1.75 req/sec to nearly 26,000 req/sec
Understand when and how to use the Quarkus IO thread and its influence on microbenchmarks.
By
Quarkus has so far been focused on start-up time and memory footprint, but runtime performance is important as well. Find out how well Quarkus performs in both Native and JVM modes.
