71 posts
Last time we looked at the Thread class and the Runnable interface, but that pairing has one problem: no return value. If we want the thread to hand a value back, we need FutureTask and Callable, which is what this post covers.
Last time we talked broadly about why we need multiple threads. Now that we want to study concurrency, let's create threads ourselves and dig into its mysteries.
What's the relationship between high concurrency and multithreading? I never create threads in my code, so why does everyone start talking about multithreading the moment the subject comes up? My opening post digs into why we should learn multithreading, and how high concurrency turns into multithreading.
This post serves as the index for the Java intermediate/advanced programming series. I also wanted to raise my own skill level, so I decided to start learning and sharing some genuinely advanced material.
The first three ZooKeeper tutorials left you able to use it. This post goes a step further and gives you a general idea of how ZooKeeper actually works.
Last time we could already drive ZooKeeper from code and learned about registering watchers. Time to try it out: this post walks through a simple hands-on example that watches a node for changes.
Last post got ZooKeeper installed. The command line works, but most of the time you operate ZooKeeper through API calls, so this post covers the basic beginner-level operations.
The previous tutorial introduced how MapReduce executes and sketched out InputFormat. Now it's time to talk about Shuffle. The data processing that happens after the Map method and before the Reduce method is called Shuffle.
In the previous post we got hands-on with MapReduce by writing some code. The MapReduce workflow looks roughly like this.
Last post covered HDFS broadly. From this section on we'll drive Hadoop by writing code, so first we need a local Hadoop development environment. If you followed the earlier posts and got Hadoop running in a VM, setting it up locally is a walk in the park. If you haven't — or haven't read those posts — read them first.
