Java | concurrent programming – begins to do those things

The introduction

Hello everyone, I am an Android Developer who has been practicing for one and a half years.

I do not know when I began to pay attention to new things, impetuous, easy to settle down to do some things. Some want to write component analysis, but because feel simple, nothing to write on the hasty, but in fact, they just stay in the [use stage], the source code is just about understanding. Often because of some things that look basic instead, always be asked suddenly, and all spit out, elusive 😑, the answer is always unsatisfactory.

Slowly, IT began to dawn on me that I was avoiding some fundamental questions THAT I didn’t want to face. It seemed to me that I could say a little bit about all aspects of concurrent programming, but I didn’t think I could say enough about it.

This series will be a quick summary of my personal experience with concurrent programming in Java, taking a look at what I think concurrent programming is, from the basics down to the basics.

directory

Java | looking back and concurrent programming – thread has its own small mind those things

Java | look back, CAS in concurrent programming

Java | seriously look, blocking queue in concurrent programming

Java | seriously look, concurrent programming in the thread pool

Java | lay, concurrent programming of AQS

Java | see lying down, the volatile keyword in concurrent programming

Java | wall, synchronized implementation of concurrent programming principle