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.

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

Regression testing is an important step in the release process, to ensure that new code doesn't break the existing functionality. As the codebase evolves, we want to run these tests frequently to help catch any issues early on.

The best way to ensure these tests run frequently on an automated basis is, of course, to include them in the CI/CD pipeline. This way, the regression tests will execute automatically whenever we commit code to the repository.

In this tutorial, we'll see how to create regression tests using Selenium, and then include them in our pipeline using GitHub Actions:, to be run on the LambdaTest cloud grid:

>> How to Run Selenium Regression Tests With GitHub Actions

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

1. Overview

In this tutorial, we’ll delve into the problem of finding the closest number to zero within a Java array. For example, given the array, [1, -3, 2, -2, 4], the number closest to zero is 1. We’ll explore various techniques to efficiently find this number and enhance our problem-solving repertoire.

2. Approaches to Find the Closest Number to Zero

We’ll discuss several approaches, each with advantages and trade-offs. First, we’ll look at a brute force method, followed by an optimized approach using sorting and binary search, and finally, an alternative technique utilizing a priority queue.

2.1. The Brute Force Approach

This method involves a straightforward iteration through the array, calculating the absolute difference between each element and zero and keeping track of the minimum difference encountered so far. If two numbers have the same absolute difference from zero, the method prioritizes the positive number to ensure a consistent and predictable result.

Let’s begin with an implementation:

public static int findClosestToZero(int[] nums)
  throws IllegalAccessException {
    if (nums == null || nums.length == 0) {
        throw new IllegalAccessException(
          "int array must not be null or empty");
    }

    int closest = nums[0];

    for (int i = 1; i < nums.length; i++) {
        if (Math.abs(closest) == (nums[i])) {
            closest = nums[i];
        }

        if (Math.abs(nums[i]) < Math.abs(closest)) {
            closest = nums[i];
        }
    }

    return closest;
}

This approach provides a basic yet effective way to find the element closest to zero in an array of integers. Its time complexity is O(n), making it the most efficient for this problem. Let’s illustrate this with a test:

@Test
void whenFindingClosestToZeroWithBruteForce_thenResultShouldBeCorrect()
  throws IllegalAccessException {
    int[] arr = {10,2,4,-2,12,25};
    assertEquals(2, BruteForce.findClosestToZero(arr));
}

This approach begins by sorting the array, simplifying the problem by arranging elements in ascending order of their absolute values. After sorting, a binary search algorithm is applied to efficiently locate the element closest to zero. After sorting, a binary search algorithm is applied to efficiently locate the element closest to zero. It is important to note that while binary search is efficient with a time complexity of O(log n), the sorting step adds O(n log n) complexity, making the overall time complexity O(n log n).

Let’s look at the implementation:

public static int findClosestToZero(int[] arr) {
    if (arr == null || arr.length == 0) {
        throw new IllegalArgumentException("Array must not be null or Empty");
    }

    Arrays.sort(arr);
    int closestNumber = arr[0];
    int left = 0;
    int right = arr.length - 1;

    while (left <= right) {
        int mid = left + (right - left) / 2;

        if (Math.abs(arr[mid]) < Math.abs(closestNumber)) {
            closestNumber = arr[mid];
        }

        if (arr[mid] < 0) {
            left = mid + 1;
        } else if (arr[mid] > 0) {
            right = mid - 1;
        } else {
            return arr[mid];
        }
    }
    return closestNumber;
}

This implementation sorts the input array and then applies a binary search to check the middle of the current search range, narrowing it down to find the number with the smallest absolute value. Let’s validate this with a test:

@Test
void whenFindingClosestToZeroWithBruteForce_thenResultShouldBeCorrect() throws IllegalAccessException {
    int[] arr = {1, 60, -10, 70, -80, 85};
    assertEquals(1, SortingAndBinarySearch.findClosestToZero(arr));
}

For the array arr, the algorithm first sorts it in ascending order, thus [-80, -10, 1, 60, 70, 85]. The method initializes closestNumber to the first element, -80, and iterates using binary search. It updates closestNumber to 1 after finding that 1 is closer to zero than other elements from the first iteration. The first iteration also produces this sub-array from the original array, [-80, -10, 1]. The binary search checks middle elements and adjusts the search range until it exits, confirming 1 as the closest to zero.

2.3. Approach Using Priority Queue

An alternative technique involves utilizing a priority queue to efficiently find the closest number to zero without sorting the entire array. It finds the closest number to zero by adding each number to the queue and keeping only the smallest number based on its absolute value.

Let’s implement this approach in Java:

public static int findClosestToZeroWithPriorityQueue(int[] arr, int k) {
    if (arr == null || arr.length == 0 || k <= 0) {
        throw new IllegalArgumentException("Invalid input");
    }

    PriorityQueue<Integer> pq = new PriorityQueue<>((a, b) -> Math.abs(b) - Math.abs(a));

    for (int num : arr) {
        pq.offer(num);
        if (pq.size() > k) {
            pq.poll();
        }
    }
    return pq.peek();
}

The comparator Math.abs(b) – Math.abs(a) ensures that the priority queue orders elements based on their absolute values, with the farthest from zero having the lowest priority. As we iterate through the array, each element is added to the priority queue. If the size of the queue exceeds k, the element that is farthest from zero is removed, ensuring the queue maintains only the kth closest numbers to zero. Finally, pq.peek() returns the element that is closest to zero.

Let’s test it:

@Test
void whenFindingClosestToZeroWithBruteForce_thenResultShouldBeCorrect()
  throws IllegalAccessException {
    int[] arr = {1, 60, -10, 70, -80, 85};
    assertEquals(1, PriorityQueueToZero.findClosestToZeroWithPriorityQueue(arr, 1));
}

For this test, the priority queue is initialized to hold only one element, representing the closest number to zero. The algorithm iterates through the array [1, 60, -10, 70, -80, 85], processing each element sequentially. Initially, 1 is added to the queue as it’s empty. As 60 is farther from zero compared to 1, it’s not added. When -10 is encountered, it’s not added because 1 is closer to zero in terms of absolute value. Subsequent elements 70, -80, and 85 are all farther from zero compared to -10, so none of them are added to the queue. After processing all elements, the queue retains 1 as the closest element to zero.

3. Comparison of Approaches

While all three approaches aim to find the closest number to zero within a Java array, they exhibit different characteristics:

The brute force approach is the simplest and the optimal solution for this problem.

An optimized approach with sorting and binary search offers better performance for larger arrays but has a time complexity of O(n log n). The Sorting + Binary Search (O(n log n)) approach might make sense if the array is sorted or repeatedly queried.

The priority queue approach strikes a balance between simplicity and performance, making it suitable for scenarios where finding a subset of the closest numbers is sufficient and sorting the array isn’t feasible.

4. Conclusion

In this article, we’ve explored approaches to tackle the problem of finding the closest number to zero in a Java array.

Each method has its strengths and trade-offs, highlighting the importance of selecting the right algorithm based on specific requirements.

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)
5 Comments
Oldest
Newest
Inline Feedbacks
View all comments