eBook – Guide Spring Cloud – NPI EA (cat=Spring Cloud)
announcement - icon

Let's get started with a Microservice Architecture with Spring Cloud:

>> Join Pro and download the eBook

eBook – Mockito – NPI EA (tag = Mockito)
announcement - icon

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:

Download the eBook

eBook – Java Concurrency – NPI EA (cat=Java Concurrency)
announcement - icon

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:

>> Download the eBook

eBook – Reactive – NPI EA (cat=Reactive)
announcement - icon

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:

>> Join Pro and download the eBook

eBook – Java Streams – NPI EA (cat=Java Streams)
announcement - icon

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:

>> Join Pro and download the eBook

eBook – Jackson – NPI EA (cat=Jackson)
announcement - icon

Do JSON right with Jackson

Download the E-book

eBook – HTTP Client – NPI EA (cat=Http Client-Side)
announcement - icon

Get the most out of the Apache HTTP Client

Download the E-book

eBook – Maven – NPI EA (cat = Maven)
announcement - icon

Get Started with Apache Maven:

Download the E-book

eBook – Persistence – NPI EA (cat=Persistence)
announcement - icon

Working on getting your persistence layer right with Spring?

Explore the eBook

eBook – RwS – NPI EA (cat=Spring MVC)
announcement - icon

Building a REST API with Spring?

Download the E-book

Course – LS – NPI EA (cat=Jackson)
announcement - icon

Get started with Spring and Spring Boot, through the Learn Spring course:

>> LEARN SPRING
Course – RWSB – NPI EA (cat=REST)
announcement - icon

Explore Spring Boot 3 and Spring 6 in-depth through building a full REST API with the framework:

>> The New “REST With Spring Boot”

Course – LSS – NPI EA (cat=Spring Security)
announcement - icon

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:

>> Learn Spring Security

Course – LSD – NPI EA (tag=Spring Data JPA)
announcement - icon

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:

>> CHECK OUT THE COURSE

Partner – Moderne – NPI EA (cat=Spring Boot)
announcement - icon

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.

Course – LJB – NPI EA (cat = Core Java)
announcement - icon

Code your way through and build up a solid, practical foundation of Java:

>> Learn Java Basics

Partner – LambdaTest – NPI EA (cat= Testing)
announcement - icon

Distributed systems often come with complex challenges such as service-to-service communication, state management, asynchronous messaging, security, and more.

Dapr (Distributed Application Runtime) provides a set of APIs and building blocks to address these challenges, abstracting away infrastructure so we can focus on business logic.

In this tutorial, we'll focus on Dapr's pub/sub API for message brokering. Using its Spring Boot integration, we'll simplify the creation of a loosely coupled, portable, and easily testable pub/sub messaging system:

>> Flexible Pub/Sub Messaging With Spring Boot and Dapr

1. Introduction

When working with date and time data in Java applications, it’s often crucial to compare dates for various purposes, such as scheduling tasks, reminders, or reporting. One common scenario is the need to identify whether a given date corresponds to yesterday relative to the current date. In this tutorial, we’ll explore various approaches for determining whether a given date object falls on yesterday.

2. Using java.util.Calendar

One common approach is to use the java.util.Calendar classes to manipulate date and time information. To compare yesterday’s date, we instantiate a Calendar object via Calendar.getInstance(). Next, we set its time to the current date using calendar.setTime(new Date()), and then subtract one day using calendar.add(Calendar.DATE, -1). This yields yesterday’s date.

Here’s a code snippet demonstrating these concepts:

Date date = new Date(System.currentTimeMillis() - (1000 * 60 * 60 * 24));
Calendar expectedCalendar = Calendar.getInstance();
expectedCalendar.setTime(date);

Calendar actualCalendar = Calendar.getInstance();
actualCalendar.add(Calendar.DATE, -1);

boolean isEqualToYesterday = expectedCalendar.get(Calendar.YEAR) == actualCalendar.get(Calendar.YEAR) &&
  expectedCalendar.get(Calendar.MONTH) == actualCalendar.get(Calendar.MONTH) &&
  expectedCalendar.get(Calendar.DAY_OF_MONTH) == actualCalendar.get(Calendar.DAY_OF_MONTH);

assertTrue(isEqualToYesterday);

Directly comparing dates using this method may fail due to differences in milliseconds between the two dates. This is because the Date object captures both the date and time, including milliseconds. If the time component is not precisely the same, the comparison may yield incorrect results.

To mitigate this issue, one approach is to truncate the time component of both dates before performing the comparison. We extract the year, month, and day components from both the dates using their respective get(Calendar.YEAR), get(Calendar.MONTH), and get(Calendar.DAY_OF_MONTH) methods to solely determine whether the actualCalendar is equal to yesterday.

Although these classes are considered legacy APIs, they are still widely used, especially in environments where newer Java versions are not available.

3. Using java.util.Date Milliseconds

This approach leverages the fact that Date objects internally store milliseconds since the epoch (January 1, 1970, 00:00:00 UTC). It involves calculating yesterday’s midnight in milliseconds and comparing it with the getTime() value of the Date object.

To begin, we calculate the timestamp in milliseconds representing the start of yesterday (midnight) in the system’s default time zone using the ZonedDateTime. This can be achieved by deducting one day from the current date and time, then truncating it to midnight, ultimately retrieving the timestamp.

Subsequently, we compare this calculated value with the getTime() value of the given expectedDate. By verifying if expectedDate falls within the range from yesterday’s midnight timestamp to the next midnight (yesterdayMidnightMillis + 86_400_000 milliseconds), we ascertain whether yesterdayMidnightMillis corresponds to yesterday’s date.

Let’s demonstrate this approach with a quick example:

Date expectedDate = new Date(System.currentTimeMillis() - (1000 * 60 * 60 * 24));
ZonedDateTime yesterdayMidnight = ZonedDateTime.now().minusDays(1).truncatedTo(ChronoUnit.DAYS);
long yesterdayMidnightMillis = yesterdayMidnight.toInstant().toEpochMilli();

boolean isEqualToYesterday = expectedDate.getTime() >= yesterdayMidnightMillis && expectedDate.getTime() < yesterdayMidnightMillis + 86_400_000;

assertTrue(isEqualToYesterday);

This approach offers a simple and efficient method for comparing dates using milliseconds. It’s suitable for scenarios where direct comparison with legacy Date objects is required.

4. Using java.time.LocalDate 

Another approach to handling date manipulation is to use the LocalDate class along with its minusDays() method. This approach is part of the modern Date and Time API introduced in Java 8.

LocalDate offers a more straightforward and intuitive way to work with dates. It is designed to focus solely on the year, month, and day components, without a time component. This makes it ideal for date-only operations, such as recording historical dates or report date filtering.

To compare yesterday’s date using this method, we start by obtaining the current date using LocalDate.now(). Then, we simply call the minusDays(1) method on the LocalDate object to subtract one day, resulting in yesterday’s date:

Date date = new Date(System.currentTimeMillis() - (1000 * 60 * 60 * 24));
LocalDate expectedLocalDate = LocalDate.of(date.getYear() + 1900, date.getMonth() + 1, date.getDate());

LocalDate actualLocalDate = LocalDate.now().minusDays(1);
boolean isEqualToYesterday = expectedLocalDate.equals(actualLocalDate);
assertTrue(isEqualToYesterday);

In this example, we specify yesterday’s date by extracting the year, month, and day components from a Date object. However, note that the getYear() method returns the year since 1900, and getMonth() returns the month index starting from 0. Therefore, we add 1900 to getYear() and 1 to getMonth() to adjust them to the standard date representation.

Using LocalDate for date manipulation is recommended for Java versions 8 and above.

5. Using Joda-Time

Joda-Time is a popular date and time library for Java. We can use this library to check if a date object represents yesterday’s date. To compare yesterday’s date using Joda-Time, we utilize the DateTime class and its minusDays() method.

First, we obtain the current date and time using DateTime.now(). Then, we subtract one day from the current date by calling the minusDays(1) method, resulting in yesterday’s date:

Date date = new Date(System.currentTimeMillis() - (1000 * 60 * 60 * 24));
DateTime expectedDateTime = new DateTime(date).withTimeAtStartOfDay();

DateTime actualDateTime = DateTime.now().minusDays(1).withTimeAtStartOfDay();

boolean isEqualToYesterday = expectedDateTime.equals(actualDateTime);

assertTrue(isEqualToYesterday);

Similar to the Calendar class, Joda-Time’s DateTime class captures time along with the date, and thus, comparing them directly may lead to inaccuracies due to differences in milliseconds.

To resolve this, instead of breaking down the date value into year, month, and day components, we can leverage the withTimeAtStartOfDay() method provided by Joda-Time. This method sets the time component of a DateTime object to the start of the day, effectively resetting the time to midnight (00:00:00). By applying withTimeAtStartOfDay() to a DateTime object, we ensure that only the date component remains significant for comparison purposes.

6. Conclusion

In this article, we’ve explored a few approaches to determine whether a date object falls on yesterday’s date. For most modern Java applications using Java 8 or later, the LocalDate approach is generally recommended due to its clarity, immutability, and support for various date manipulations.

While Joda-Time is a mature and stable library, its future development and support may become less certain over time as more projects transition to the standard Java Date and Time API.

The code backing this article is available on GitHub. Once you're logged in as a Baeldung Pro Member, start learning and coding on the project.
Baeldung Pro – NPI EA (cat = Baeldung)
announcement - icon

Baeldung Pro comes with both absolutely No-Ads as well as finally with Dark Mode, for a clean learning experience:

>> Explore a clean Baeldung

Once the early-adopter seats are all used, the price will go up and stay at $33/year.

eBook – HTTP Client – NPI EA (cat=HTTP Client-Side)
announcement - icon

The Apache HTTP Client is a very robust library, suitable for both simple and advanced use cases when testing HTTP endpoints. Check out our guide covering basic request and response handling, as well as security, cookies, timeouts, and more:

>> Download the eBook

eBook – Java Concurrency – NPI EA (cat=Java Concurrency)
announcement - icon

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:

>> Download the eBook

eBook – Java Streams – NPI EA (cat=Java Streams)
announcement - icon

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:

>> Join Pro and download the eBook

eBook – Persistence – NPI EA (cat=Persistence)
announcement - icon

Working on getting your persistence layer right with Spring?

Explore the eBook

Course – LS – NPI EA (cat=REST)

announcement - icon

Get started with Spring Boot and with core Spring, through the Learn Spring course:

>> CHECK OUT THE COURSE

Partner – Moderne – NPI EA (tag=Refactoring)
announcement - icon

Modern Java teams move fast — but codebases don’t always keep up. Frameworks change, dependencies drift, and tech debt builds until it starts to drag on delivery. OpenRewrite was built to fix that: an open-source refactoring engine that automates repetitive code changes while keeping developer intent intact.

The monthly training series, led by the creators and maintainers of OpenRewrite at Moderne, walks through real-world migrations and modernization patterns. Whether you’re new to recipes or ready to write your own, you’ll learn practical ways to refactor safely and at scale.

If you’ve ever wished refactoring felt as natural — and as fast — as writing code, this is a good place to start.

eBook Jackson – NPI EA – 3 (cat = Jackson)
2 Comments
Oldest
Newest
Inline Feedbacks
View all comments