1. Java and Spring
Mark Reinhold has just announced what's next for the JDK 9 Java module system. Looks like a more decent plan than the first go-round – taking bite sized chunks and integrating them into the platform one after the other, rather than one big change. Fingers crossed.
Really useful and detailed look at Hibernate UUIDs – although I've been working with these little identifiers for years and years, I still learned a lot from this one. I also like the crowd sourced way to double check info and get advice.
This is how Spring becomes easier – beans that are proxied with CGLIB used to require a default constructor – after Spring 4 they don't any more. So – construction injection is now possible for these beans as well – which makes testing them a lot easier.
Practical illustration of the Caching in Spring – cool use of @Profile to transparently switch between two different cache providers (in this case Hazelcast and Ehcache). Cool beans.
And finally – some official Spring stuff that I took note of this week:
- >> Spring Security / Spring Data integration prototype – A beautiful thing
- >> Spring Data Dijkstra SR1 released – Spring Data bug fixes – pick them up while they're hot
- >> Performance – tuning the Spring Petclinic sample application – webinar replay
- >> Tooling for Spring's next generation – webinar replay
I couldn't agree more, both with this specifically but also with the broader statement: “You Probably Don't Need X“, where X can be any number of things. Complexity is a sneaky thing and you need to be ruthless when architecting your systems. And adding in a MQ is probably – nine times out of ten – a premature optimization and the wrong move.
And so we have our article of the week – go read this one – twice.
An interesting read about microservices from the point of view of the SOLID principles.
Good food for thought – it's a quick read, so you have no excuse 🙂
A good guide for interviewing – a few interesting tidbits in there that I wish I read (and internalized) 8 years ago 🙂
This one struck a chord with me – as I was involved in two “Big Rewrites” until now and both times we should have at least tried to leverage this approach rather than actually re-writing the system. Save yourself the hassle of going down that particular rabbit hole and go read this one.
An off the cuff intro to algorithmic complexity and P vs NP. Nice read – brings back fun memories of school.