Mastering Graph Algorithms: BFS, DFS, Dijkstra, Floyd-Warshall, and Bellman-Ford in Java

4.23K 0 0 0 0

Chapter 2: Depth-First Search (DFS) in Java


Depth-First Search (DFS) is another fundamental algorithm used to traverse or search through graphs and trees. Unlike Breadth-First Search (BFS), which explores level by level, DFS dives deeper into a graph, exploring as far down a branch as possible before backtracking. DFS can be implemented using either a stack (iterative approach) or recursion.

DFS is particularly useful for problems where you need to explore a graph fully, such as in scenarios involving pathfinding, cycle detection, topological sorting, and connected components in a graph. The algorithm starts at the root node (or any arbitrary node in the graph), marks it as visited, and then explores each adjacent node before backtracking.

The DFS algorithm works by:

  1. Starting at a selected node (often the root in trees).
  2. Visiting an unvisited node, marking it as visited.
  3. Recursively or iteratively visiting the adjacent nodes (depth-first).
  4. Backtracking to the most recent node and continuing the process until all nodes have been visited.

One of the main advantages of DFS is that it can be easily implemented using recursion, simplifying the code. It can also be adapted to find solutions like topological sorting in Directed Acyclic Graphs (DAGs), strongly connected components in directed graphs, and detecting cycles in graphs.

DFS Algorithm in Java

DFS can be implemented using recursion or with an explicit stack. Below is an example of DFS implemented using recursion:

import java.util.*;

 

class Graph {

    private Map<Integer, List<Integer>> adjacencyList = new HashMap<>();

 

    // Add edge to the graph

    public void addEdge(int v, int w) {

        adjacencyList.putIfAbsent(v, new ArrayList<>());

        adjacencyList.get(v).add(w);

    }

 

    // DFS Recursive method

    public void DFS(int start) {

        Set<Integer> visited = new HashSet<>();

        DFSUtil(start, visited);

    }

 

    private void DFSUtil(int node, Set<Integer> visited) {

        // Mark the current node as visited and print it

        visited.add(node);

        System.out.print(node + " ");

 

        // Recur for all the vertices adjacent to this node

        if (adjacencyList.containsKey(node)) {

            for (Integer neighbor : adjacencyList.get(node)) {

                if (!visited.contains(neighbor)) {

                    DFSUtil(neighbor, visited);

                }

            }

        }

    }

}

 

public class Main {

    public static void main(String[] args) {

        Graph graph = new Graph();

        graph.addEdge(1, 2);

        graph.addEdge(1, 3);

        graph.addEdge(2, 4);

        graph.addEdge(3, 5);

 

        System.out.println("DFS traversal starting from node 1:");

        graph.DFS(1);  // Output: 1 2 4 3 5

    }

}

Time Complexity of DFS:

  • The time complexity of DFS is O(V + E), where V is the number of vertices (nodes) and E is the number of edges. This is because DFS visits each vertex and edge once.

Space Complexity of DFS:

  • The space complexity of DFS is O(V) due to the stack (or recursion call stack) used to keep track of visited nodes.



Back

FAQs


1. What is the main difference between BFS and DFS in terms of traversal strategy and use cases?

BFS (Breadth-First Search) explores a graph level-by-level using a queue, which makes it ideal for finding the shortest path in unweighted graphs or for level-order traversal. On the other hand, DFS (Depth-First Search) dives deep into each branch before backtracking using recursion or a stack, which is better suited for problems like cycle detection, topological sorting, or solving mazes. BFS is more memory-intensive for wide graphs, while DFS may hit stack limits in deep graphs.

2. Which algorithm is best suited for graphs containing negative edge weights, and why is Dijkstra not suitable in such cases?

Bellman-Ford is the preferred choice for graphs with negative edge weights because it relaxes all edges up to V-1 times and can detect negative weight cycles. Dijkstra's Algorithm assumes that once a node's shortest path is found, it won't change—which fails when a negative edge later offers a better path. Hence, Dijkstra produces incorrect results in graphs with negative weights.

3. Can we use BFS or DFS to find the shortest path in weighted graphs?

No, BFS and DFS do not work correctly for weighted graphs when computing the shortest path unless all edges have the same weight (in which case BFS can be used). In weighted graphs, algorithms like Dijkstra or Bellman-Ford should be used to account for varying edge weights.

4. Is Dijkstra’s Algorithm always faster than Bellman-Ford?

Yes, typically. Dijkstra’s Algorithm (especially with a min-priority queue) has a time complexity of O((V + E) log V) using a binary heap, which is significantly faster than Bellman-Ford’s O(V × E) in dense graphs. 
However, Dijkstra is restricted to graphs with non-negative weights, while Bellman-Ford is more versatile in terms of weight handling but slower in execution.

5. Does Floyd-Warshall detect negative cycles, and how does it differ from Bellman-Ford in that regard?

Floyd-Warshall does not explicitly detect negative cycles but can indirectly do so. If any diagonal element dist[i][i] becomes negative, it indicates a negative weight cycle. In contrast, Bellman-Ford directly checks for cycle presence after the V-1 iterations, making it more transparent and suitable for single-source shortest path detection with cycle checking.

6. How does memory usage differ between adjacency matrix and adjacency list in graph algorithms?

An adjacency matrix uses O(V²) space regardless of edge count, which is inefficient for sparse graphs. Adjacency lists use O(V + E) space, making them more space-efficient and faster for traversals in sparse graphs. Most graph algorithms like BFS, DFS, Dijkstra, and Bellman-Ford perform better with adjacency lists in large, sparse graphs.

7. In what scenarios would Floyd-Warshall be preferred over repeated Dijkstra's executions for all-pairs shortest paths?

Floyd-Warshall is preferred when the graph is dense and edge weights may be negative (but no negative cycles), as it provides a clean O(V³) solution for all-pairs shortest paths. Running Dijkstra’s Algorithm V times yields O(V × (V + E) log V), which may be better in sparse graphs but complex to implement compared to Floyd-Warshall’s simplicity.

8. Are graph algorithms like BFS or DFS guaranteed to work correctly in disconnected graphs?

No, by default, BFS or DFS starting from a single source will only explore the connected component of that source. To process the entire graph, especially for tasks like component counting or cycle detection, you must run BFS or DFS on each unvisited node to ensure all disconnected components are covered.

9. How can graph algorithms be optimized for real-time systems like GPS or social networks?

For real-time systems, efficiency and response time are critical. BFS or optimized Dijkstra (with Fibonacci or binary heaps) is ideal for fast queries in routing. Systems often precompute paths using Floyd-Warshall or store distance matrices. In large-scale applications like social networks, graph traversal is often distributed or approximated using heuristics like A*.

10. Do graph algorithms work equally well for both directed and undirected graphs?

Most graph algorithms work for both, but implementation varies. For DFS and BFS, directionality affects traversal order. For Dijkstra and Bellman-Ford, directed edges must be processed correctly for accurate pathfinding. Special attention must be paid in cycle detection, SCCs (Strongly Connected Components), and topological sorting, which only apply to directed graphs.