1. Spring
Quite a lot of webinars and recordings come out this week on Spring:
Add to this a few very exciting Spring releases and project news, and we have a solid week for Spring:
Chris is continuing the series about project Sagan – the code that powers spring.io. Yet another reminder that Java 8 is not only ready for production use, but has also changed the way we'll write code in Java going forward.
And since we're only dealing in series this week – here's the latest installment in the fantastic series about building a light web app that makes sense out of log files. I really enjoy seeing a real-world application being built like this.
2. Java
The Jrebel guys know their classloaders and this article is no exception to that rule.
Java 8 brings some nice performance tweaks to the old trusty HashMap. I'll take it.
A good rundown for running Jmeter tests in Jenkins, against different environment.
3. Technical
Using inheritance is rarely a good idea, and preferring composition is one of these things things that you learn to do (and appreciate) more and more over time. This article covers a few good reasons why this is true for tests as well.
The way of the land when it comes to log tools analyzers – SAAS, Open Source – all in all, a very useful analysis. This goes a long way towards helping you weigh your options and make a good decision when picking one of these for a production system. I know first hand how difficult it is to switch – having done it last year, half way through a project (goodbye Papertrail).
The story and reasoning behind flexi-pool – a new, adaptive connection pool proxy integrating with most relevant connection pooling solutions in the Java ecosystem.
4. Musings
Insightful response from “The Code Whisperer” (aka J. B.) to a recent article on refactoring. While both views are pragmatic, I find the J.B.'s response a more nuanced and closer to my own thinking on this.
This is a good start of what could be a very useful list of generic acceptance criteria for an application. It covers things that are simply common across applications, and – as such, don't belong on the individual acceptance criteria of an issue/story/task.
res – REST with Spring (eBook) (everywhere)
