fawind/actor-db

PoC of an Actor Database System

actor-db's Issues

Return validated result on quorum reads

Runnables for client and datastore

Setup configurable main methods for client and datastore

• Depends on #18
• Client should have the option to spawn a local datastore instance for testing

Read/write repair

• Investigate read repair
• Spike implementation?

Extract parameters to config

Move static config variables to their own config objects.

Multi-Node setup

Finish remoting setup:

• Option to spawn multiple nodes locally
• Option to join existing network
• Docker swarm setup for local testing?

E2e tests

We should add some e2e tests where we actually validate the final states. We can start with some simple workflows, e.g. create table > insert some values > fetch some values

Handle quorum timeouts

Split up client and store modules

• Split up datastore and client into separate modules.
• Add third module containing shared message objects.

Serialize SelectWhere query

ATM SelectWhere uses a Predicate which is not serializable.

Correctly handle lamport timestamps

Check when/where/how we want to return this stamps.

Switch from Java Serialization

Use kryo or something else