It’s been a bit since I wrote the previous article in this series. Quarkus, which has been a topic in this series, has gone from version 1.2 to 1.6! As I started writing this article, I thought, why not, I’ll go ahead an upgrade. For the most part, it was very straightforward. The biggest change for the code used in this series is the updated gRPC support. Once I got the hang of the gRPC update, I have to say that it’s a nice addition to this relatively new framework. Another gotcha for me was what looks to be a tightening of the control over the reactive event loop. Before Quarkus, I’ve used the reactive pattern in other projects. While wanting to be a good citizen and keep the heavy lifting off the event loop, sometimes it’s difficult to know when code that probably shouldn’t be executing in the context of the event loop is. As I upgraded and executed this series’ sample code to Quarkus 1.6, I was caught off guard by the runtime environment alerting me to entity manager operations running on the event loop. While it did catch me off guard, I did appreciate the help in identifying possible trouble spots. There’s been a lot going on with Quarkus. Check it out at quarkus.io.

While wanting to be a good citizen and keep the heavy lifting off the event loop, sometimes it’s difficult to know when code that probably shouldn’t be executing in the context of the event loop is.

#java #microservice architecture #kubernates #quarkus tutorial