affinity
affinity copied to clipboard
Library and a Framework for building fast, scalable, fault-tolerant Data APIs based on Akka, Avro, ZooKeeper and Kafka
Because the http interface is not torn down with the actor
Currently, only internal registration happens against the fqn of the avro recrod but that means it is not accessible to regular consumers
failed pipeline which contains global stores hangs on error shutdown until shutdown timeout occurs
https://github.com/facebook/rocksdb/wiki/Basic-Operations#asynchronous-writes This could lead to a single point of control of at-least-once processing possible, e.g. potentially turning off write-ahead log completely on rocksdb (since kafka writes are primary they serve...
this would make precise validation possible - for example defining `affinity.coordinator.zookeeper.connection` doesn't currently fail because specialization is only defined by `zookeeper` so the path is allowed by the current validation...
Advanced web socket client can subscribe to any number of key-value streams with a single connection. This will complicate the protocol but we need affinity-ws-client module anyway which may contain...