The Weekly Review on Baeldung is a curated list of the best stuff I read each week – a handful of articles that are well worth reading (in no particular order).
With the final weekly review of February – hold on to your hat!
We’ll start strong with a lot of Spring official resources:
- => Accessing JPA Data with REST – a new guide about the ever-improving REST support in Spring.
- => Groovy Bean Configuration in Spring Framework 4 – the Groovy Bean Builder is a real alternative to the now standard @Configuration classes.
- => Webinar Replay: Spring Data Repositories – Best Practices – Over an hour of Spring Data goodness in video form.
- => Spring Data Redis 1.2 GA Released – Hot on the heels of the Spring Data Release train last week – Spring Data Redis 1.2 is out this week (will be part of the next Spring Data train).
Good look into the Spring Security options for managing sessions.
An interesting discussion about monitoring an application – and building a quick and custom tool to proactively monitor logs. Funny to.
A look into how Map can be used as a local cache in Java 8 – using the new computeIfAbsent atomic operation and the lambda support.
Inspired by the previous article – Vlad talks through some great insights about caching. I wish I would have read the first part of this post 8 years ago when I was starting out – it would have saved me a bit of time.
If you’ve been dealing with exceptions in JUnit tests manually – using rules is a good step forward, as it eliminates a long of cruft and unnecessary code.
Example driven discussion about growing and evolving an API – as opposed to trying to get it right from the get go. Read this if you’re building any kind of API (you probably are even if you don’t know it).
A nice short introduction to going beyond JUnit with additional testing libraries (and Maven).
The concept of a transparent redirect – and the interesting idea of potentially extending the HTTP spec with a new redirect status.
Useful to have it your back pocket.
A great answer to a well intentioned but somewhat limited perspective on teams and good software development. This cuts right to the heart of the problem – on a healthy team, everyone should take responsibility.
Keeping with tradition, if you read one single article out of this weeks review – this is the one you should read!
A good in-depth discussion about choosing and administering your passwords – a lot to learn from this article.
Thinking your way correctly through the decisions you’re building and growing an API is a very useful skill to have. TDD will get you half way there – but ultimately the right frame of mind is very useful when deciding the abstractions and the responsibilities of your own API.
I’ve been picking a lot of API articles lately – mainly because it’s so important to get yours right – which is, I think – a good way to end this one.