Embark on a journey of knowledge! Take the quiz and earn valuable credits.
Take A QuizChallenge yourself and boost your learning! Start the quiz now to earn credits.
Take A QuizUnlock your potential! Begin the quiz, answer questions, and accumulate credits along the way.
Take A Quiz
Dijkstra’s Algorithm is a single-source shortest
path algorithm used to find the shortest path from a starting node to all
other nodes in a graph with non-negative edge weights. It works on both
directed and undirected graphs and is commonly applied in navigation systems,
network routing, and resource optimization.
The core idea of Dijkstra's algorithm is to maintain a priority
queue (min-heap) where the node with the minimum tentative distance
is always picked next. It uses a greedy approach, updating the shortest
known distance to each vertex and relaxing edges until the shortest path to all
nodes is determined.
The algorithm works best when implemented using adjacency
lists and a priority queue, especially for sparse graphs. It does not
work correctly if the graph contains negative edge weights.
2. Dijkstra’s Algorithm Code (2 Examples)
a. Syllabus-Oriented Example (Shortest Path in Weighted
Graph)
import
java.util.*;
public
class DijkstraExample {
static class Node implements
Comparable<Node> {
int vertex, weight;
Node(int v, int w) {
this.vertex = v;
this.weight = w;
}
public int compareTo(Node other) {
return this.weight - other.weight;
}
}
public static void dijkstra(int V,
List<List<Node>> graph, int source) {
int[] dist = new int[V];
Arrays.fill(dist, Integer.MAX_VALUE);
dist[source] = 0;
PriorityQueue<Node> pq = new
PriorityQueue<>();
pq.add(new Node(source, 0));
while (!pq.isEmpty()) {
Node current = pq.poll();
for (Node neighbor :
graph.get(current.vertex)) {
int newDist =
dist[current.vertex] + neighbor.weight;
if (newDist <
dist[neighbor.vertex]) {
dist[neighbor.vertex] =
newDist;
pq.add(new
Node(neighbor.vertex, newDist));
}
}
}
System.out.println("Shortest
distances from node " + source + ": " + Arrays.toString(dist));
}
public static void main(String[] args) {
int V = 5;
List<List<Node>> graph =
new ArrayList<>();
for (int i = 0; i < V; i++)
graph.add(new ArrayList<>());
graph.get(0).add(new Node(1, 10));
graph.get(0).add(new Node(2, 3));
graph.get(1).add(new Node(2, 1));
graph.get(2).add(new Node(1, 4));
graph.get(2).add(new Node(3, 2));
graph.get(3).add(new Node(4, 7));
graph.get(4).add(new Node(3, 9));
dijkstra(V, graph, 0);
}
}
b. Real-World Example (GPS Navigation - Shortest Route)
//
Simplified example for GPS-style routing using Dijkstra
//
Nodes represent cities, and edge weights represent distance in kilometers
Map<String,
List<Node>> buildCityMap() {
Map<String, List<Node>> map =
new HashMap<>();
map.put("A", Arrays.asList(new
Node("B", 5), new Node("C", 10)));
map.put("B", Arrays.asList(new
Node("C", 2), new Node("D", 3)));
map.put("C", Arrays.asList(new
Node("D", 1)));
map.put("D", new
ArrayList<>());
return map;
}
class
Node {
String city;
int distance;
Node(String city, int distance) {
this.city = city;
this.distance = distance;
}
}
// Due to complexity, full real-world Dijkstra for strings
would involve a mapping and adjusted implementation.
(Note: Real-world applications typically involve more
advanced data structures like HashMap<String, List<Node>> for
string-based graph representations.)
3. Pros of Dijkstra’s Algorithm
4. Cons of Dijkstra’s Algorithm
5. How Dijkstra’s Is Better Than Other Algorithms
6. Best-Case Scenarios to Use Dijkstra’s Algorithm
7. Applications of Dijkstra’s Algorithm
8. Worst-Case Scenarios to Use Dijkstra’s Algorithm
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.
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.
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.
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.
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.
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.
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.
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.
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*.
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.
Please log in to access this content. You will be redirected to the login page shortly.
Login
Ready to take your education and career to the next level? Register today and join our growing community of learners and professionals.
Your experience on this site will be improved by allowing cookies. Read Cookie Policy
Your experience on this site will be improved by allowing cookies. Read Cookie Policy
Comments(0)