1. Spring and Java
JWT is becoming the de facto standard in web security yesterday. And JJWT is certainly a good way to go for an implementation.
The ElasticSearch support coming to Hibernate looks intelligently designed. Plus it's a fluid API, which gives it some extra points.
Who said Hibernate is a blunt instrument? You can get surgical with it, Training-Day style.
Keeping track of create/update times is usually the first step towards building out audit logic – here's a good, simple way of doing that in Hibernate.
Also worth reading:
Webinars and presentations:
Time to upgrade:
2. Technical
This one's first for a reason. It's a step back and a real look at architecting a distributed system.
It talks about boundaries between systems, the essential question of inter-communication, all in the scope of achieving a good cadence of actually pushing out real work.
Better code design? Why not.
API contract testing is definitely an underused practice.
This is a very quick and to the point writeup introducing the concept and giving you some basic tools to get it going.
Also worth reading:
3. Musings
The results of an interesting (albeit not super scientific) test about the results of doing TDD.
Of course measuring only a few of the concerns may not be very representative – TDD touches so many aspects of development that it's tough to really quantify the impact it has.
Some common sense advice about good communication, which is unfortunately glossed over by so many organizations out there.
I chuckled my way through this one. You should do the same.
Unit testing is markedly difficult when you're starting out.
Before even considering the correctness of the system, the first significant advantage of weaving tests into a system has is design. Good design doesn't necessarily come from unit tests, but it's a whole lot easier with these as a positive constraint on the system.
Also worth reading:
4. Comics
And my favorite Dilberts of the week:
5. Pick of the Week
res – REST with Spring (eBook) (everywhere)