Java Web Weekly, Issue 171 – Java网络周刊》第171期

最后修改: 2017年 4月 6日

Here we go…


1. Spring and Java


>> The Java in 2017 Survey []

I’m running my yearly Java “State of the Union” survey for 2017. Please take a few seconds to vote.

我正在进行2017年的Java “国情 “年度调查。请花几秒钟时间来投票。

>> Memory Puzzle with Lambdas []

A very interesting Java 8 memory puzzle, with quite surprising results ?

一个非常有趣的Java 8内存难题,结果相当令人惊讶 ?

>> Common code in Spring MVC, where to put it? []

It’s not that easy to find a suitable place for common code in Spring MVC apps. This write-up shows a few possible places where you could do this.

在Spring MVC应用程序中为普通代码找到一个合适的地方并不那么容易。本篇文章展示了几个可能的地方,你可以在那里做这件事。

>> Optional Dependencies in the Java Platform Module System []

Java 9’s Project Jigsaw finally makes it possible to define module dependencies to be present at compile time and not at runtime.

Java 9的Project Jigsaw终于可以定义模块的依赖性,使其在编译时而不是在运行时出现

>> CRUD operations on Spring REST resources with Kotlin []

This is how you can create and consume a simple REST API using Kotlin and Spring.

这就是你如何使用Kotlin和Spring创建和消费一个简单的REST API

>> Use Spring Cloud Config as externalized configuration []

Externalizing your configuration allows you to build artifacts once and easily swap configurations during runtime or for different environments. It turns out that Git works great as a configuration holder for such scenarios.


>> Idiomatic Kotlin Best Practices []

Kotlin is becoming more and more popular and it’s important to revisit our Java coding habits and learn the right way of doing stuff in Kotlin.


Also worth reading:


Webinars and presentations:


Time to upgrade:


2. Technical


>> The ultimate software QA process []

Shocking no one, having a QA in your team is definitely a good idea.


Also worth reading:


3. Musings


>> How to start a peer group []

If you don’t know how to start a peer group, here is a simple list of steps to follow. You don’t need this often, but when you do, it’s super handy.


>> QA in Production []

Production is always a source of unexpected problems that can be a great feedback for improving your systems.


>> The Relationship between Static Analysis and Continuous Testing []

Static Analysis and Continuous Testing are two different techniques applied to different areas. Static Analysis will be useful no matter how good your test coverage is, as it will point out potential problems before even running a single test.


Also worth reading:


4. Comics


And my favorite Dilberts of the week:


>> Ten thousand hours []

>> I don’t know what this is, but I want in []

>> This isn’t what I wanted []

5. Pick of the Week


I’ve been following the work on this book for a few months now. It’s finally out:

>> Hibernate Tips (book)

If you’re doing any kind of Hibernate work, this is definitely one to get.