1. Spring and Java

>> HTTP headers forwarding in microservices [frankel.ch]

>> Tracing Spring Integration Flow with Spring Cloud Sleuth [java-allandsundry.com]

Doing a proper microservice implementation is tough – no two ways about it. There are certainly new challenges but also a new class of tools meant to help with these challenges.

Here are two interesting writeups about one of these tools – Spring Cloud Sleuth – and about tracing an HTTP request across multiple services.

>> JUnit 5 State Of The Union [sitepoint.com]

A good high level look at JUnit 5 right now, a year and a couple of months into development.

>> 6 Hibernate features that I’m missing in JPA [thoughts-on-java.org]

Hibernate has been on a roll lately, and JPA is lagging behind even more so than usual. Here’s a list of solid features that should hopefully make it into the next version of JPA.

>> The best way to implement equals, hashCode, and toString with JPA and Hibernate [vladmihalcea.com]

An interesting discussing focused on the fundamental.

Also worth reading:

Webinars and presentations:

Time to upgrade:

2. Technical

>> Message Processing Styles [tbray.org]

A quick look at processing JSON data in real-world systems, where things aren’t as neat and tidy as we’d like them to be, and pretty much anything could come over the wire.

>> A service framework for operation-based CRDTs [krasserm.github.io]

If you’re way into Event Sourcing and CQRS, than this will make a good read, for both practical takeaways but also for cross-pollination of architectural ideas.

Also worth reading:

3. Musings

>> Short DNS Record TTL And Centralization Are Serious Risks For The Internet [techblog.bozho.net]

No doubt you heard and probably experienced the massive DDOS attack a few days ago.

There are several reports and analysis worth reading online of course, here’s one that actually goes beyond just “what happened”.

>> 4 Ways Custom Code Metrics Make a Difference [daedtech.com]

If you’re using static analysis, semi-custom, tunable rules simply need to be used and evolved. Without these, the defaults likely won’t fit the specifics of your codebase and your needs – which generally leads to either lots of false positives, or turning off useful rules entirely.

As a quick take-away, definitely tweak and keep tweaking your static analysis rules, so that they actually make sense for your codebase.

Also worth reading:

4. Comics

And my favorite Dilberts of the week:

>> Stop being engineers! [dilbert.com]

>> Try eating cake [dilbert.com]

>> Taking more responsibility [dilbert.com]

5. Pick of the Week

>> Just shut up and let your devs concentrate [geekwire.com]