mix amnesia.drop -db QueueDB

rm -rf Mnesia.nonode@nohost mix amnesia.create -db QueueDB --disk

TODO:

fix bug causing fetch to only happen after server restart
switch to promises to invert horrible callback architecture to something more functional
- send completes too
switch to mutable queue allowing elixir objects without silly serialization
fix domain recognition in utils.ex:url_domain/1
custom cool-downs per domain
debug tests
implement retry count
preserving state (not losing sockets/jobs) through restart?
fix decoder
throttler: fix timing, the ticks don't necessarily happen at .000
throttler: how should the blocking work with GenServer's standard 5s timeout?
ditch Phoenix
distribute
ditch handlers for empty domain queues? should work on a failed pop -- no free fetch credit loophole.

api's People

Contributors

With external processing, the traditional HTTP request/response cycle is broken; alternatives:
HTTP:

Shifts the problem: how to pass the websocket around?

options:

have the original sink subscribe to relevant results (Akka HTTP)
passing around a functional copy of the websocket for pushing (not Akka HTTP; not Play WebSocket?; Play Channel?)
^ since websockets are TCP-based I don't think you can really pass them around like this, same issue as for HTTP.

Akka HTTP:

UpgradeToWebsocket.handleMessages (request-response)
UpgradeToWebsocket.handleMessageWithSinkSource (not necessarily connected)
handleWebsocketMessages(flow): use with above
^ make Sink per websocket connection, monitoring results from queues/whatever to sort them into the right result sink?
http://doc.akka.io/api/akka-stream-and-http-experimental/1.0/index.html#akka.http.scaladsl.model.ws.UpgradeToWebsocket
serialization... I don't think copying the Sink would be useful
extra sinks bit unfortunate for scaling
^ use Erlang/Elixir?
^ Node.js can also handle 600k websocket connections, but bit less scalable (esp. more effort for clusters):

Play:

play.api.mvc.WebSocket
https://www.playframework.com/documentation/2.3.0/api/scala/index.html#play.api.mvc.WebSocket
^ serializable, but no push()
play.api.libs.iteratee.Concurrent$$Channel
used in play-akka-angular-websocket
^ pass around and use to push?
^ Trait yet used by itself rather than implemented
^ also something about Enumerator[JsValue]? I don't get it.
https://github.com/playframework/playframework/blob/master/framework/src/iteratees/src/main/scala/* play/api/libs/iteratee/Concurrent.scala
Iteratee interface, implementing cancellation and state (Cont/Error/Done)
https://www.playframework.com/documentation/2.2.x/Iteratees
- bit inelegant since I just tried to shift away from Play
- I don't super understand this...