- Why this name?
Because my son loves the ninja turtles.
- What is ?
Turtle is a lightway publish and subscribe broker/library tag based...yes another one !!
- What does ?
With turtle you can publish and subscribe messages using “tags”.
- Can I use it?
The project is not complete yet, don't use it!!.
TurtleEnvironment env = new TurtleEnvironment();
env.init();
String subscriberId = env.subscribe(new MessagesHandler() {
@Override
public void handlerMessage(Map header, byte[] body, String firstMatchTag) {
System.out.println(new String(body));
}
},"#pizza","#pasta","#beer");
env.publish("today spaghetti and wine !!".getBytes(),"#pasta","#wine","#spaghetti");
....
env.unSubscribe(subscriberId);
env.deInit();The library contains three threads kind:
- Publish-Thread
- Subscriber-Thread
- Worker-Thread
The Publish and the Subscribe threads are internal, by default their number is half of the core available for each category.
es: 8 core, 4 for Publish-Thread and 4 for Subscriber-Thread.
The configuration can be modified.
The internals threads are not-blocking, they use LinkedBlockingQueue to share data between the threads but using pool with time-out.
The messages flow is described as follow:
Each thread is isolated and can work without wait lock time between other threads. Internally the threads have an “dummy” cache to improve the performance in high throughput case.
The cache reduce the java synchronization time appending more than one message to the queue-list. In this version the cache is not configurable and it is checked each 200 millisecond.
Finally the worker threads are used by clients, if the pool is full the worker threads are blocked and the messages will be stored to the subscriber thread queue.
The current version does not provide class serializations, the body message is an byte[]. Using byte[] is very flexible, the sender can implement the serialization as prefer. Anyway, I'm planning to implement also a primitive types.
The current version implements JMX interface where it is possible to monitor the threads and the queues status, as following:
Resources count:
Well, my aim is to create an pluggable Publish and Subscribe system tag based. Starting with a library, then an essential asynchronous broker and finally a scalable broker.
I’m making some test with JGroups (http://www.jgroups.org/).