Synchronization:

Whenever two or more threads required access to a shared resource, they required a few ways to ensure in which the resource will be used through only one thread at a time. The process through that this is achieved is known as synchronization. As you will see, Java precedes unique, language-level support for it.

Key to synchronization is the concept of the monitor (also called a semaphore.) A monitor is an object which is used as a mutually exclusive lock, or mute. Only one thread could own monitor at a given time. Whenever a thread obtains a lock, it is said to have entered the monitor. All other threads attempting to enter the locked monitor will be suspended until the first thread exits the monitor.  These other threads are said to be waiting for the monitor.  A thread that owns a monitor can reenter the similar monitor if it so desires.

If you have worked along with synchronization when using other languages, like a C or C ++, you know which it could be a bit tricky to use. This is since most languages do not, themselves, support synchronization. Alternatively, to synchronize threads, your programs require utilizing OS primitives. Fortunately, since Java implements synchronization through language elements, most of the complexity related along with synchronization has been eliminated.

You could synchronize your code in either of two ways. Both include the use of the synchronized keyword, and both are examined here.