The Slowest One
- May 24, 2012
^this. And to understand why or how do we use Class/Interface names to call static method, you should read how the memory allocation works in Java.
+1 for this. My college professor(during bachelor degree) consulted this book and Head First. Both of them are very good. Great for learning Java. It's a shame I haven't written much Java after my Bachelor's degree(other than for Android).Don't know about others but Herbert Schildt's book is best for Java. I think it's called Java complete reference or something.
Yeah worth it. Also, a whole book dedicated to threads. Wow. @dDesmond David could use it maybe.We’ve teamed up with O’Reilly for our newest bundle. Get books like Java in a Nutshell and Java 8 Lambdas. Plus, pay what you want & support charity!www.humblebundle.com
5 Java based books fro $1.
Not really but depends on your use case. It's most helpful if you are doing something like batch processing.Do we really need to think about threads in web development
These don't run in a container by default. You will have to write a Dockerfile for your build to run in a container.Spring Boot, Play etc runs in a container which is self managed by the containers. Am I right?
Like I said, batch processing or data processing. Like if you have to process a large number of files, then you will have to use threads to process them parallelly to increase throughput. But then again you don't have to know too much for most common use cases, just general idea is usually enough.What use cases do we have in today's Java programming where deep knowledge on Threads might come handy?
Doesn't spring/play comes with its own container which creates a independent thread for each (http)request and those threads are managed until the purpose is served.These don't run in a container by default. You will have to write a Dockerfile for your build to run in a container.
If you are speaking about servlet container, then yes. But this is not something spectacular, a servlet container is basically same as an ordinary web server with the added functionality of running web applications and routing the requests to the appropriate web applications. As such, like any other web server, it creates new threads to handle requests.Doesn't spring/play comes with its own container which creates a independent thread for each (http)request
But not by us, the request thread's lifecycle is handled internally by the servlet container. We can spawn new threads for our own purposes though INSIDE the servlets but not in the servlet container itself.those threads are managed until the purpose is served.