Java Weekly, Issue 235

Here we go…

1. Spring and Java

An interesting post that highlights the possible semantics of value types in Java, along with some hurdles faced by Oracle’s JVM developers as they evolve this often-requested feature.

>> Tracing a reactive flow – Using Spring Cloud Sleuth with Boot 2 [java-allandsundry.com]

A quick read showing how to capture distributed tracing data for a reactive Spring Boot application and display it in Zipkin UI. Good stuff.

>> WireMock Tutorial: Request Matching, Part Three [petrikainulainen.net]

The latest installment in this series is all about specifying expectations about the contents of a JSON request body.

>> How do find and getReference EntityManager methods work when using JPA and Hibernate [vladmihalcea.com]

A neat writeup about a lesser-known method in JPA — getReference — that can boost performance when creating @OneToOne and @ManyToOne associations. Very cool.

Also worth reading:

Webinars and presentations:

Time to upgrade:

*2. Technical and Musings*

A refreshing review of the different types of non-relational databases at our disposal and what kinds of problems they are best suited for.

>> How did that bug happen? Git bisect to the rescue! [odino.org]

A clever command that can dramatically reduce debugging time by determining exactly which commit introduced a bug to your repository.

>> How to write a Kotlin DSL – e.g. for Apache Kafka [blog.codecentric.de]

A cool writeup demonstrating the utility of Kotlin’s extension functions and lambda arguments to functions when creating a DSL.

>> Politeness or Bluntness in Code Review? Settling the Matter Once and for All [daedtech.com]

A thoughtful piece reminding reviewers to seek the proper balance between subtlety and bluntness, based on your audience — the reviewee — and their cultural norms.

Also worth reading:

3. Comics

And my favorite Dilberts of the week:

>> Ignorance is Bliss [dilbert.com]

4. Pick of the Week

===== >> Say the Hard Thing [randsinrepose.com]

Leave a Reply

Your email address will not be published.