QBit is a queuing library for microservices. It is similar to many other projects like Akka, Spring Reactor, etc. QBit microservices is just a library not a platform. QBit has libraries to put a service behind a queue. You can use QBit queues directly or you can create a service. QBit services can be exposed by WebSocket, HTTP, HTTP pipeline, and other types of remoting. A service in QBit is a Java class whose methods are executed behind service queues. QBit implements apartment model threading and is similar to the Actor model or a better description would be Active Objects. QBit does not use a disruptor. It uses regular Java Queues. QBit can do north of 100 million ping pong calls per second which is an amazing speed (seen as high as 200M). QBit also supports calling services via REST, and WebSocket. QBit is microservices in the pure Web sense: JSON, HTTP, WebSocket, etc.
QBit is a Java microservice lib supporting REST, JSON and WebSocket. It is written in Java but I might one day write a version in Rust or Go or C# (but that would require a large payday).
POJO (plain old Java object) behind a queue that can receive method calls via proxy calls or events (May have one thread managing events, method calls, and responses or two one for method calls and events and the other for responses so response handlers do not block service. One is faster unless responses block). Services can use Spring MVC style REST annotations to expose themselves to the outside world via REST and WebSocket.
Many POJOs behind one response queue and many receive queues. There may be one thread for all responses or not. They also can be one receive queue.
A thread managing a queue. It supports batching. It has events for empty, reachedLimit, startedBatch, idle. You can listen to these events from services that sit behind a queue. You don't have to use Services. You can use Queue's direct.
ServiceBundle that is exposed to REST and WebSocket communication
EventBus is a way to send a lot of messages to services that may be loosely coupled
Way to invoke service through async interface, service can be inproc (same process) or remoted over WebSocket.
QBit is a non-blocking lib. You use CallBacks via Java 8 Lambdas. You can also send event messages and get replies. Messaging is built into the system so you can easily coordinate complex tasks.
There is a lot of room for improvement with Speed. But already QBit is VERY fast.
200M+ TPS inproc ping pong, 10M-20M+ TPS event bus, 500K TPS RPC calls over WebSocket/JSON, etc.
More work needs to be done to improve speed, but now it is fast enough where I am working more with usability.
Besides if I make it too fast, then no one will publish benchmarks, and then I can't publish follow up benchmarks that kick their ass. Where would be the fun? There is no story if their is no conflict.
Do me a favor. Take a look at QBit. I could use your help, and I think you will like it.
There are a lot of examples in the source code.
Also look at the benchmarks those have good examples too.
Also look at the EventManager as I used QBit to build it. It is a good example on how to build a service in QBit.
Just basic stuff to get your warmed up.
Client for the last one.
Server for the last one. Earlier version of tutorial with less directions.
This one I am proud of. Check out the second example.
This one really shows the power of QBit and starts to lift of QBits skirt a little to show what is going on underneath.
Learn more about QBit.
[Detailed Tutorial] QBit microservice example