Blog - page 44
On January 22, 2020, we were informed that Quarkus had won the DeveloperWeek DEVIES Awards in the category of Best Innovation in: Code Frameworks/Libraries. As a Kubernetes-native Java stack, Quarkus represents a fundamental shift in modern application development that makes Java a great fit for cloud-native application architectures, such as containers, microservices and serverless. Java developers are able to use Quarkus to build applications that have a faster startup time and take up significantly less...
Since its first release, Quarkus lets you create resilient applications with MicroProfile Fault Tolerance. It uses SmallRye Fault Tolerance to provide this functionality. At the time SmallRye Fault Tolerance was born, Hystrix was still a thing and was chosen to be the core of the implementation. The choice turned out to be sub-optimal. The library itself is not developed anymore. Moreover, changes in the MicroProfile Fault Tolerance specification made it impossible to satisfy the specification...
With the announcement that Quarkus 1.1 was available in December 2019, and after a tremendous effort from all the contributors and community, we’re excited to announce that Quarkus 1.1 is Eclipse MicroProfile 3.2 compatible! MicroProfile 3.2 was released November 2019, bringing updates to the Metrics and Health specifications, but what is MicroProfile and why do I care? MicroProfile creates specifications for developing microservices with Enterprise Java, making compatibility with MicroProfile a key feature of Quarkus....
An overview on currently available IDE integrations for Quarkus.
If like me you have met Quarkus and fell in love, you started implementing your backend and you started to feel so light and quick, click clack, whoot whoot… in a woosh, your lightning fast native container is ready to be sent on your brand new Kubernetes cluster 🤙 This is awesome!! Mmmeahh you may have forgotten a detail… have you thought about the fate of your first production exception (please be honest with me...
1.1.1.Final fixes several issues mostly in our Kotlin and Gradle support.
Template engine, YAML configuration, Gradle improvements... learn more about what we have baked for you in 1.1.
For Quarkus 1.1.0.Final, we had to take the hard decision to go back to GraalVM 19.2 while our CR1 used 19.3. Here is why.
