advantageous/qbit

The Java microservice lib. QBit is a reactive programming lib for building microservices - JSON, HTTP, WebSocket, and REST. QBit uses reactive programming to build elastic REST, and WebSockets based cloud friendly, web services. SOA evolved for mobile and cloud. ServiceDiscovery, Health, reactive StatService, events, Java idiomatic reactive programming for Microservices.

qbit's Issues

ENHANCE: handle websocket open (notify service of open or start of session/connection)

Setup and test HTTP pipelining as an option with Content-Length.

write unit test that starts up server, sends a message from client, ensure server gets message.

Parameters as body arguments

If the body is empty, i.e., 0 args not 1 null arg, then use the request parameters.

Currently we support GET and POST for REST. We should support all.

Add headers to HTTPRequest, HttpResponse, etc.

Add queue / batch back to client API for proxy

Add request to response routing for ServiceImpl

ServiceImpl

needs a regsiter(String returnAdddres, ResponseQueue rqueue)

Bug: A method cannot be mapped to a POST and a GET with the same URI.

handle websocket closed

add binary support based on new encoding

Duplicate code: BoonServiceProxyFactory and BoonJSONServiceFactory seem to do the exact same thing

BoonServiceProxyFactory and BoonJSONServiceFactory seem to do the exact same thing

ENHANCE: ADD SUPPORT FOR JACKSON AND GSON

JsonMapper
Add support for Jackson and GSON.

ENHANCE: BasicQueue, More types of queues, and more SOC seperations of concernt

BasicQueue
This class does too much
It needs knowledge of the type of queue.
There should be several queue implementations.
We need another that does metrics.
The queue also spawns a thread and does its own scheduling.
We really need the scheduling done by a third partys so we can add different types of schedulers.

Finish ServiceBundleImpl, you need to route the call, and find the right service...

Fix broken tests search for //@Test

Create test that throws an exception from service and call from client (do this over the wire)

Finish method protocol call spec over websocket, http

encodeHeaders and Params

Implement simple HTTP server on top of vertex for REST

Timeout throwing an exception for something that has already been handled.

[QueueListener Response Queue /services] DEBUG i.a.q.s.Server - Response not marked handled and it timed out, but could not be written io.advantageous.qbit.http.HttpRequest@87a022a3
java.lang.IllegalStateException: Response has already been written
at org.vertx.java.core.http.impl.DefaultHttpServerResponse.checkWritten(DefaultHttpServerResponse.java:452) ~[vertx-core-2.1.1.jar:na]
at org.vertx.java.core.http.impl.DefaultHttpServerResponse.putHeader(DefaultHttpServerResponse.java:128) ~[vertx-core-2.1.1.jar:na]
at org.vertx.java.core.http.impl.DefaultHttpServerResponse.putHeader(DefaultHttpServerResponse.java:39) ~[vertx-core-2.1.1.jar:na]
at io.advantageous.qbit.vertx.http.HttpServerVertx.lambda$createResponse$13(HttpServerVertx.java:184) ~[qbit-vertx/:na]
at io.advantageous.qbit.vertx.http.HttpServerVertx$$Lambda$15/289205234.response(Unknown Source) ~[na:na]
at io.advantageous.qbit.server.Server.handleMethodTimedOut(Server.java:504) [qbit-boon/:na]
at io.advantageous.qbit.server.Server.checkTimeoutsForRequests(Server.java:475) [qbit-boon/:na]
at io.advantageous.qbit.server.Server.access$200(Server.java:39) [qbit-boon/:na]
at io.advantageous.qbit.server.Server$1.idle(Server.java:268) [qbit-boon/:na]

error response handling

You can put errors messages into response codes for methods that throw exceptions.
We might want another class for this or... perhaps an enum of some sort to denote it is an error message.

There are many missing pieces to the architecture.

This works as a REST framework but not so much as a true websocket framework (yet).
We need to build out some more examples like perhaps a (gasp...) chatroom.
We need eventing (calls to client side without notification).
This will drive the architecture quite a bit.

Create a builder for ServiceClient

Methods that are not round should timeout quicker. Or an error response should be sent so the REST client is not hanging.

add request params @ParamName

add request params mapping support.
@ParamName("argName1") or something.

Make HttpResponse take a generic. Have a HttpBinaryResponse and HttpTextResponse? Change the builder to take a setTextResponse and a setBinaryResponse. DONE

Make HttpResponse take a generic. Have a HttpBinaryResponse and HttpTextResponse?
Change the builder to take a setTextResponse and a setBinaryResponse. DONE

ENHANCE: ServiceServerImpl break this out into many tasks

ServiceImpl
There is no way to configure with different method handler.
There is no way to pass AOP interception.
There is no callback for blocked call to be put into another queue or holding area for data faulting.
add this to doHandleMethodCall and beforeMethodProcessing
ServiceImpl can be run async, i.e., it manages its queue or it can run sync, i.e., the service bundle manages its queue. This is probably ok.

ServiceServerImpl
We really need a way to capture pre/post web socket and pre/post request

idle handling

Note that ServiceServerImpl only handles idle callback for checking timeouts. This may not be good enough if under heavily load use case. We may need to do a periodic check as well for timeouts. Not only when we are not busy. I noticed same issue with client. We should do a periodic flush regardless. We may want/need a periodic capability or timer of sorts in all queues.

ENAHNCE: HTTP SERVER INTERCEPTION

HttpServer
This should have the ability for other types of interception pre/post for web socket and HTTP requests.

handle errors from client proxy

java.lang.ClassCastException: org.boon.core.value.CharSequenceValue cannot be cast to java.util.List
at io.advantageous.qbit.vertx.QBitClient$2.accept(QBitClient.java:440)
at io.advantageous.qbit.vertx.QBitClient.handleAsyncCallback(QBitClient.java:225)
at io.advantageous.qbit.vertx.QBitClient.handleWebsocketQueueResponses(QBitClient.java:213)
at io.advantageous.qbit.vertx.QBitClient.lambda$startReturnProcessing$8(QBitClient.java:180)
at io.advantageous.qbit.vertx.QBitClient$$Lambda$3/1338841523.run(Unknown Source)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)

getting occosional unhandled hangup stack traces from Netty.. might need to register a hangup listener

Support void return for REST calls

Works for web socket. Does not work for REST.

create a test for handling request params and move request param handling into build and out of client code

ENHANCE: Add event architecture

create websocket protocol / post protocol parser test

Create a builder for ServiceServer

Support timeout.

ENHANCE: WEBSOCKET FOR BINARY

WebsSocketSender
Only supports strings. If we ever go to a binary protocol. This is limited.
Change send to sendText. Add a binary sentBinary that takes a byte[].
Use a default method to call the sendText from sendBinary so that only sendText needs to be implemented.

ENHANCE: QueueScheduler.. Add this concept and take it out of BasicQueue

QueueScheduler
Add this concept and take it out of BasicQueue

ReceiveQueueManager
This will become QueueScheduler

Put together a benchmark comparing BasicQueue to just using a queue and a thread.

BUG: Websocket Qbit proxy broke

Handle binary

HttpResponse
has one method which is a callback, that takes a string body.
It might be better if this took an HttpResponseBody so that you could hide/abstract the bytes from the server. This would also enable a binary protocol in the future.
This is not a high priority.

Implement simple HTTP Client on top of vertex.

create webscocket / REST call example

Ensure "Content-length" is sent on REST requests to facilitate keep-alive

DOC: Document how to handle callbacks from foreign services in the service queue

handle missing service addresses with 404

Response encoding similar to the method call encoding

ENHANCE: ServiceImpl calls sendAndFlush. It should really call send and there should be a periodic flush. responseSendQueue.sendAndFlush(response); NOT DONE

ServiceImpl calls sendAndFlush. It should really call send and there should be a periodic flush.
responseSendQueue.sendAndFlush(response); NOT DONE

Fix broken tests for service router.