Both Thread and Executor is used to run your code in parallel and you can create and start your own thread either by extending java.lang.Thread class or implementing java.lang.Runnable interface. Though both approaches work well in small application, On the other hand, Executor is an interface which also provides parallel execution, but via a thread pool, which is more suitable for large Java application.
The other major differences could be:
1) First and foremost difference between Thread and Executor is that java.lang.Thread is a class in Java while java.util.concurrent.Executor is an interface.
2) The Executor concept is actually an abstraction over parallel computation. It allows concurrent code to be run in managed way. On the other hand, Thread is a concrete way to run the code in parallel.
3) The third difference between an Executor and a Thread class is that former decouples a task (the code which needs to be executed in parallel) from execution, while in the case of a Thread, both task and execution are tightly coupled.
4) The Executor concept allows your task is to be executed by a worker thread from the thread pool, while Thread itself execute your task.
Difference between a Thread and an Executor in Java
5) Executor provides a execute() method which accepts a Runnable task, while Thread accepts the Runnable task on its constructor.
6) One more key difference between a Thread and an Executor is that a Thread can only execute one Runnable task but an Executor can execute any number of Runnable task.
7) In the case of Thread, the task is executed by the Thread which accepts Runnable instance, but in the case of Execution the command (a Runnable implementation) may be executed in a new thread, a pooled thread or in the calling thread itself, depending upon the implementation of Executor interface.
8) In the case of a thread, it's developer's responsibility to create and start the thread, but in the case of Executor, the framework will create and start threads for you. Though you can control the whole process by giving your implementation of Executor interface. Though, with the improvements in ForkJoinPool in Java 7 and 8, you might want to use that instead of Executor. If ForkJoinPool is a new concept to you, I suggest reading Java 8 in Action to learn more about it.
Thread vs Executor in Java
7) Now, let's see an example of execution a Runnable task via Executor and via Thread in Java:
Output
Task is executed by Executer Thread
Task is executed by pool-1-thread-1
The difference is quite clear that first is just a thread while later is a pool of threads.
It's worth noting that factory methods of Executors class e.g. newSingleThreadExecutor() return an ExecutorService, which is sub-interface of Executor and also provides methods to accepts a Callable, terminate or shut down the thread pool.
That's it from my side. If you have some more points add it into the comments, I will add those in the post.
Happy reading and keep commenting :)
click to install Flipkart app
Thread vs Executor in Java
The other major differences could be:
1) First and foremost difference between Thread and Executor is that java.lang.Thread is a class in Java while java.util.concurrent.Executor is an interface.
2) The Executor concept is actually an abstraction over parallel computation. It allows concurrent code to be run in managed way. On the other hand, Thread is a concrete way to run the code in parallel.
3) The third difference between an Executor and a Thread class is that former decouples a task (the code which needs to be executed in parallel) from execution, while in the case of a Thread, both task and execution are tightly coupled.
4) The Executor concept allows your task is to be executed by a worker thread from the thread pool, while Thread itself execute your task.
Difference between a Thread and an Executor in Java
5) Executor provides a execute() method which accepts a Runnable task, while Thread accepts the Runnable task on its constructor.
6) One more key difference between a Thread and an Executor is that a Thread can only execute one Runnable task but an Executor can execute any number of Runnable task.
7) In the case of Thread, the task is executed by the Thread which accepts Runnable instance, but in the case of Execution the command (a Runnable implementation) may be executed in a new thread, a pooled thread or in the calling thread itself, depending upon the implementation of Executor interface.
8) In the case of a thread, it's developer's responsibility to create and start the thread, but in the case of Executor, the framework will create and start threads for you. Though you can control the whole process by giving your implementation of Executor interface. Though, with the improvements in ForkJoinPool in Java 7 and 8, you might want to use that instead of Executor. If ForkJoinPool is a new concept to you, I suggest reading Java 8 in Action to learn more about it.
Thread vs Executor in Java
7) Now, let's see an example of execution a Runnable task via Executor and via Thread in Java:
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 | import java.util.concurrent.Executor; import java.util.concurrent.Executors; public class Main { public static void main(String args[]) { Runnable task = new Runnable() { @Override public void run() { System.out.println("Task is executed by : " + Thread.currentThread().getName()); } }; Thread t = new Thread(task, "Executer Thread"); t.start(); Executor e = Executors.newSingleThreadExecutor(); e.execute(task); } } |
Output
Task is executed by Executer Thread
Task is executed by pool-1-thread-1
The difference is quite clear that first is just a thread while later is a pool of threads.
It's worth noting that factory methods of Executors class e.g. newSingleThreadExecutor() return an ExecutorService, which is sub-interface of Executor and also provides methods to accepts a Callable, terminate or shut down the thread pool.
That's it from my side. If you have some more points add it into the comments, I will add those in the post.
Happy reading and keep commenting :)
click to install Flipkart app
No comments:
Post a Comment