1. Spring and Java
After low level system data, the next family of metrics you want to start tracking and monitoring are JVM level metrics. Here's a good way to go it with the ELK stack.
A quick and practical intro to the various mechanism that are going to power the module system in Java 9.
Interesting way to create a Map.
Years back, we always had to restart the server/redeploy the app for minor changes. Of course that's no longer the case now – which has a significant impact on our speed of rolling work out.
If you're working with Thymeleaf in a Boot app – here are a couple of ways to do exactly that – changes with no restarts.
There are a few different ways to slice implementing audit logic with Hibernate – and Envers is definitely an interesting solution to the problem.
Very interesting writeup showing how to transition a Boot application to run servlerless on AWS. I definitely need to give that a try to get a better understanding of what it can do.
Also worth reading:
Webinars and presentations:
Time to upgrade:
2. Technical
As I started to split my own implementations and very carefully joined the microservices bandwagon (or train) – I very quickly found that I need to relax my definition of time for each service.
That is if I wanted to be able to trace a single request through the system and still make sense of it.
This is a quick writeup all about that.
A long piece worth reading if you're passionate about data science, Clojure – or both.
I've been doing a lot of CQRS, Event Sourcing and microservices in the past couple of years, so naturally this article was quite an interesting read – well worthy if you're doing any of these.
Beyond the “money” thing, there's a lot to glean from this piece about Content Security Policies and the way browsers chose to implement CSPs.
Worth understanding if you're building stuff for the web.
Also worth reading:
3. Musings
Hibernate should have obviously done this a long time ago 🙂
If you're working with and ingesting a large volume of data, back-pressured async stream processing is a godsend.
This is a good intro to how the standard came to be – and a very interesting read.
This writeup is definitely good for some perspective on the way we all work and creating value. Some solid podcasts recommended in here as well 🙂
To be or not to be? That was THE question for a long time, but no longer 🙂
Now, it's to refactor or rewrite – mainly because that decision has the potential to literally put a business under.
I always find that, no matter how much I think I understand a concept, I don't fully grok it until I have to sit down and actually define it. It always turns out to be more difficult than I expect it to be.
Also worth reading:
4. Comics
And my favorite Dilberts of the week:
5. Pick of the Week
res – REST with Spring (eBook) (everywhere)
