Baeldung Weekly Review 24 – Baeldung每周评论 24

最后修改: 2015年 6月 12日

At the very beginning of 2014 I decided to track my reading habits and share the best stuff here, on Baeldung.

在2014年一开始,我就决定追踪我的阅读习惯,并在这里分享最好的东西,在Baeldung

2014 has been quite the year, covering each week with a review. I’ve been doing a lot more reading to make sure I cover and curate stuff that has value and is actually worth reading.

2014年是相当不错的一年,每星期都有一篇评论。我一直在做更多的阅读,以确保我覆盖和策划的东西有价值,并真正值得阅读。

Let me know in the comments if you’re finding my reviews interesting and useful.

请在评论中告诉我,如果你觉得我的评论有趣和有用。

Here we go…

我们来了……

1. Spring and Java

1.Spring和Java</strong

>> CORS support in Spring Framework

Very nice support for CORS getting here in Spring 4.2 – this is going to help quite a bit.

非常好的对CORS的支持在Spring 4.2中得到了体现 – 这将会有很大的帮助。

>> 12 Tools That I Use for Writing Unit and Integration Tests

This is THE testing toolbox in the Java ecosystem. Lots of good libraries to pick up from here.

这是Java生态系统中的测试工具箱。有很多好的库可以从这里获得。

>> ETags and Spring Data REST

A good, to the point intro to ETags in the upcoming version of Spring Data REST. Cool stuff.

在即将到来的Spring Data REST版本中,对ETags的介绍很好,切中要害。很酷的东西。

Also worth reading:

也值得一读。

Webinars and presentations:

网络研讨会和演讲。

Time to upgrade:

是时候升级了。

2. Technical

2.技术

>> Don’t start with a monolith

If your goal for a new project is a microservice architecture, you have a foundational question to ask yourself as you get going. Should I start on easy monolith route and break it apart into microservices and responsibilities later, or will it be better to enforce these clear responsibilities from the start?

如果你的新项目的目标是微服务架构,那么在你开始的时候,你要问自己一个基础性的问题。我应该从简单的单体路线开始,以后再把它分解成微服务和责任,还是从一开始就执行这些明确的责任会更好?

This piece, along with the one from last week, is a nuanced and well-balanced discussion of this choice.

这篇文章与上周的文章一起,对这一选择进行了细致入微和平衡的讨论。

It has been my experience that both approaches work given the team has very high discipline. If I were to make the choice today, and there would be no question that the goal is the microservice architecture – then I would start with microservices from the very beginning.

根据我的经验,如果团队有很强的纪律性,这两种方法都能发挥作用。如果我今天要做选择,而且目标毫无疑问是微服务架构–那么我将从一开始就采用微服务

>> Why we need Resilient Software Design

A good, short interview on system resiliency at scale.

关于系统规模弹性的一个很好的简短采访。

>> Comparing Application Deployment: 2005 vs. 2015

The Times They Are a-Changin’.

时代在变迁。

Also worth reading:

也值得一读。

3. Musings

3.思索

>> Speaker style bingo: 10 presentation anti-patterns

Great insights into public speaking, specifically about getting better at it.

对公开演讲有很好的见解,特别是关于提高演讲水平。

Also worth reading:

也值得一读。

4. Comics

4.漫画

And my favorite Dilberts of the week:

还有本周我最喜欢的Dilberts。

>> Never been cubicled…

>> Training Customers

>> You’ll have to do some actual work

5. Pick of the Week

5。本周精选</strong

Earlier this year I introduced the “Pick of the Week” section here in my “Weekly Review”. If you’re already on my email list – you got the pick already – hope you enjoyed it.

今年早些时候,我在 “每周回顾 “中推出了 “每周精选 “栏目。如果你已经在我的电子邮件列表中–你已经得到了精选–希望你喜欢它。

If not – you can share the review and unlock it right here:

如果没有–你可以分享评论并在此解锁。

[sociallocker id=”6211″]

[sociallocker id=”6211″]

A very handy reference for Garbage Collection:

一个非常方便的关于垃圾收集的参考资料。

>> Java Garbage Collection handbook

[/sociallocker]

[/sociallocker]