The Baeldung Weekly Review 19
Last updated: July 29, 2020
Mocking is an essential part of unit testing, and the Mockito library makes it easy to write clean and intuitive unit tests for your Java code.
Get started with mocking and improve your application tests using our Mockito guide:
Handling concurrency in an application can be a tricky process with many potential pitfalls. A solid grasp of the fundamentals will go a long way to help minimize these issues.
Get started with understanding multi-threaded applications with our Java Concurrency guide:
Spring 5 added support for reactive programming with the Spring WebFlux module, which has been improved upon ever since. Get started with the Reactor project basics and reactive programming in Spring Boot:
Since its introduction in Java 8, the Stream API has become a staple of Java development. The basic operations like iterating, filtering, mapping sequences of elements are deceptively simple to use.
But these can also be overused and fall into some common pitfalls.
To get a better understanding on how Streams work and how to combine them with other language features, check out our guide to Java Streams:
Explore Spring Boot 3 and Spring 6 in-depth through building a full REST API with the framework:
Yes, Spring Security can be complex, from the more advanced functionality within the Core to the deep OAuth support in the framework.
I built the security material as two full courses - Core and OAuth, to get practical with these more complex scenarios. We explore when and how to use each feature and code through it on the backing project.
You can explore the course here:
Spring Data JPA is a great way to handle the complexity of JPA with the powerful simplicity of Spring Boot.
Get started with Spring Data JPA through the guided reference course:
Refactor Java code safely — and automatically — with OpenRewrite.
Refactoring big codebases by hand is slow, risky, and easy to put off. That’s where OpenRewrite comes in. The open-source framework for large-scale, automated code transformations helps teams modernize safely and consistently.
Each month, the creators and maintainers of OpenRewrite at Moderne run live, hands-on training sessions — one for newcomers and one for experienced users. You’ll see how recipes work, how to apply them across projects, and how to modernize code with confidence.
Join the next session, bring your questions, and learn how to automate the kind of work that usually eats your sprint time.
1. Java and Spring
>> Too Fast, Too Megamorphic: what influences method call performance in Java?
I’m starting this weeks review with a very solid analysis of various types of method invocations in Java, and the performance characteristics of each. This is an in-depth read but very much worthwhile to get a deeper understanding of the Java runtime.
>> Java 8 Friday: Language Design is Subtle
Discussion on some of the Java 8 design decisions such as having default methods versus, for example, Scala traits. A reminder that language design is nuanced and a lot of factors play into it – overall, a great addition to the Java community.
>> Writing Clean Tests – Naming Matters
An in depth discussion about naming in tests – it can serve as a good point of reference for choosing to name your tests artifacts, even if you don’t actually follow all the conventions the article lays out.
>> SpringOne2GX 2013 Replay: spring.io inside and out
This recording is all about Project Sagan and the new (well, new-ish) spring.io website – all very meta and all built in Spring.
>> SpringOne2GX 2013 Replay: Getting Started with Spring Security 3.2
Yes, Spring Security 4 was announced recently, and yes – it looks very interesting. However, if you’re looking to get started with Spring Security, 3.2 is the way to go – this is a quick video that should get the ball rolling.
3. Technical
>> ParallelChange
API design is a beautiful thing – here’s an useful process to keep in mind whenever you’re making a backwards incompatible change in an externally published interface.
>> Goto Fail, Heartbleed, and Unit Testing Culture
This article puts forward an important premise – the latest major security issues of 2014 – the GOTO Fail and Heartbleed – could have been easily avoided if the developers were practicing unit testing. Be warned – the article is very long and in-depth – actually going over the tests themselves and showing exactly how the bugs could have been avoided.
>> Is TDD Dead? (the recording)
The initial “Is TDD Dead” hangout recording and the next one (happening today, on the 16th of May).
The first was OK and spurred a lot of discussion online about the value and practices of TDD, and testing in general, and I’m hoping that the second discussion is going to go a little more in depth.
4. Musings
>> The Low Quality of Scientific Code
If you’ve ever seen scientific code, you know how it looks, you know you don’t want to touch it and you know you couldn’t change it reliably if your life depended on it. If you’re interested in that area, of if you were ever frustrated working with a library such as Mahout – this is why.
