Benzo's Blog

  https://www.hyperiondev.com/portfolio/86840/

  Interfaces in Java An interface is a 'blueprint' for the functions available for an object.  Interfaces are used in large-scale java application developments, and the benefits of using interfaces in the developmental phase of an applications are:  Early establishment of interactions amongst necessary objects without forcing early definition of the supporting objects Enables developers focus on their particular development tasks knowing that integration has already been applied. Provides flexibility to integrate new interfaces without having to overhaul the entire code. Enforcing the contracts between members in the development team to ensure that all objects are interacting as designed to interact. As a software developer, Interfaces allows for us to implement functions and changes to an existing object without actually changing that particular object. Aside from this, It will allow us to make changes without having to rewrite the entire object with the implemented chan...

  Concurrent Collection Classes A collection of Application Programming Interfaces that deal particularly with concurrent operations. These classes are alternative to the Java Collection Framework and provides similar functionality although with additional support towards Concurrency. The ultimate goal of this collection is to allow many threads access to resources in a synchronised manor. Concurrent Collections in Java According to Oracle.com  and as quoted below:  "The  java.util.concurrent  package includes a number of additions to the Java Collections Framework. These are most easily categorized by the collection interfaces provided: BlockingQueue  defines a first-in-first-out data structure that blocks or times out when you attempt to add to a full queue, or retrieve from an empty queue. ConcurrentMap  is a subinterface of  java.util.Map  that defines useful atomic operations. These operations remove or replace a key-value pair only if t...

  Executor Simply put, an Executor just actions threads and instructions provided to it ExecutorService Extends from Executor and includes startup / shutdown threads and is able to wait and determine the status of any instructions a user may have added above the Executor. In the illustration above, we se a simple example that illustrates the main differences between the Executor and ExecutorService.  Both Executor and ExecutorService are interfaces, however ExecutorService extends Executor.  Executor runs execution methods, ExecutorService runs submission methods. Executor returns void type, ExecutorService returns future type.  In summary and according to Oracle.com : "An ExecutorService that provides methods to manage termination and methods to that can produce a Future for tracking progresso one or more asynchronous task" You can read up more about this class by clicking the Oracle link above.