Today I am going to explain how Vert.x can be used for creating distributed Master Worker Paradigm. In large scale systems it’s applicable to wide variety of problems.
First – Just to refresh our memories about what Vert.x is
Vert.x as we know is a lightweight framework for creating distributed microservices. It can sale up and scale out depending on your needs. It also takes away all your pain of dealing with complexity of heavily multithreaded environments, race conditions etc. etc.
Primary unit of work in Vert.x is a verticle. Verticles are thread safe and they can run locally or remotely. One Verticle interacts with other verticle using Events which carry data with them.
Now – let’s take a day to day scenario.
We are getting lot of requests. Each request is independent of each other but we are unable to process all these requests on the commodity hardware that we have. How to serve all these requests coming to our cool high traffic website?
Well one answer is serve each request in a new “thread” and keep increasing the CPU Cores (Scale Up) and hope it will work. This is what your webserver does. Problem is you can only increase no of cores to a limit (How high you can go?).
Once you reach that limit you will add more such machines and leave it to load balancer to divide all these requests equally between all machines. Sounds familiar?
Well, you will have problem relying on load balancer when every service in the system faces same issue. Every time you will have to scale these services and keep re-configuring load balancer. What if this was possible in application layer dynamically. What if we could scale up and out without any pain of load balancer. Good news is it can be achieved using Vert.x except load balancing happens inside your application layer. There can be lot of benefits of this approach which I will discuss some other time but for now let’s just focus on how can this be achieved using Vert.x
So this problem has 2 major challenges : –
a. How to divide the work between different machines so that we can keep up with this load.
b. How to combine the result from all this processing so that we can return this result to client (master) who needs answers from all workers before proceeding further (Can this be achieved by load balancer?).
So Master is like Management whose only job is to distribute all the work to developers (like you and me) and when work is done…combine all the statuses, create a report and notify the boss and hopefully get a fat pay hike (sounds familiar?)
In terms of Vert.x We have a master Verticle which gets lot of work to do. But Master does not want to do any work..Why? Because its a “Master”. So master wants to assign all this work to Workers. Worker are also verticles in Vert.x. But then problem arises that master needs to know if all work is completed so that it can make right decision about what to do next..Right..
So here is high level architecture we are going to fllow
Ok..so in order to simulate this first lets create lot of work
import io.vertx.core.Future;
import io.vertx.core.Vertx;
import io.vertx.core.eventbus.Message;
/**
* Created by marutsingh on 2/20/17.
*/
public class Application {
public static void main(String[] args){
final Vertx vertx = Vertx.vertx();
//vertx.deployVerticle(new HttpVerticle());
vertx.deployVerticle(new MasterWorker());
//DeploymentOptions options = new DeploymentOptions().setInstances(10);
//vertx.deployVerticle("WorkVerticle",options);
for (int i = 0; i < 5; i++){
vertx.deployVerticle("WorkVerticle");
}
vertx.eventBus().send("vrp", "Job1,Job2,Job3,Job4,Job5,Job6,Job7,Job8,Job9,Job10");
System.out.println("Deployment done");
}
}
Great ..We created our own master..lets see how does it look
public class MasterWorker extends AbstractVerticle {
@Override
public void start(Future fut) {
vertx.eventBus().localConsumer("vrp", new Handler() {
@Override
public void handle(Message objectMessage) {
String data = objectMessage.body().toString();
String[] work = data.split(",");
String jobId = UUID.randomUUID().toString();
List futureList = new ArrayList();
for (String w : work){
Future f1 = Future.future();
futureList.add(f1);
vertx.eventBus().send("work",w + ":" + jobId,
f1.completer());
}
}
});
}
}
Great so our master is doing…sending work over event bus and hoping some worker will start working upon it.
Lets see what our worker is doing
public class WorkVerticle extends AbstractVerticle {
@Override
public void start(Future<Void> fut) {
final String verticleId = super.deploymentID();
vertx.eventBus().localConsumer("work",
new Handler() {
@Override
public void handle(Message objectMessage) {
String[] data = objectMessage.body().toString()
.split(":");
String work = data[0];
String jobId = data[1];
String result = work + "Completed***";
objectMessage.reply(result);
}
});
}
}
So worker does the work and sends an event on event bus with result.
Now master needs to combine all these results. This is way cool features introduced in Vert.x 3…Composable futures It makes this so easy
CompositeFuture.all(futureList).setHandler(ar -> {
if (ar.succeeded()) {
ar.result().list().forEach((result) ->
resultSet.append(((MessageImpl) result).body().toString()));
System.out.println(resultSet.toString());
// All succeeded
} else {
// All completed and at least one failed
}
});
Thats all !!. I hope this will be useful in some of your scenario.
Source code is available at
https://github.com/singhmarut/vertx-master-worker-simulator
Happy coding !!
