Java Weekly, Issue 212

Refactor Java code safely — and automatically — with OpenRewrite.

Refactoring big codebases by hand is slow, risky, and easy to put off. That’s where OpenRewrite comes in. The open-source framework for large-scale, automated code transformations helps teams modernize safely and consistently.

Each month, the creators and maintainers of OpenRewrite at Moderne run live, hands-on training sessions — one for newcomers and one for experienced users. You’ll see how recipes work, how to apply them across projects, and how to modernize code with confidence.

Join the next session, bring your questions, and learn how to automate the kind of work that usually eats your sprint time.

Distributed systems often come with complex challenges such as service-to-service communication, state management, asynchronous messaging, security, and more.

Dapr (Distributed Application Runtime) provides a set of APIs and building blocks to address these challenges, abstracting away infrastructure so we can focus on business logic.

In this tutorial, we'll focus on Dapr's pub/sub API for message brokering. Using its Spring Boot integration, we'll simplify the creation of a loosely coupled, portable, and easily testable pub/sub messaging system:

>> Flexible Pub/Sub Messaging With Spring Boot and Dapr

Here we go…

1. Spring and Java

>> Creating a Kotlin DSL for validation [blog.sourced-bvba.be]

DSLs can be powerful in Kotlin – especially when they leverage reified generics.

>> Spring, Reactor and ElasticSearch: bechmarking with fake test data [nurkiewicz.com]

>> Monitoring and measuring reactive application with Dropwizard Metrics [nurkiewicz.com]

A couple of interesting examples of monitoring a reactive application using Dropwizard.

>> Building richer hypermedia with Spring HATEOAS [spring.io]

Affordance is another interesting concept that allows squeezing more from Hypermedia by including domain-specific metadata in responses generated by a REST API.

>> No JCP for Java EE [infoq.com]

Looks like Java EE will not utilize the standard Java Community Process.

>> Java EE vs Spring Testing [antoniogoncalves.org]

Integration tests are important in a managed environment; even when they’re slightly more difficult to maintain, they should be as easy to write as possible. That’s not always the case in Java EE where integration tests can sometimes be difficult to set up and quite heavy.