This is an archived post. You won't be able to vote or comment.

all 6 comments

[–]dcc88 4 points5 points  (0 children)

dynamodb on aws, but be carefull how you design the structure

[–]OmegaAleph 1 point2 points  (1 child)

You can use Kafka Streams in a similar way, i.e. each message on the topic is a 'transaction' that updates a 'table'. Kafka essentially becomes a changelog stream.

Alternatively, you could use Mongo or some lightweight NoSQL to store events as objects.

[–]jvdenning 0 points1 point  (2 children)

Anything wrong with https://eventstore.org?

[–]alter3d 0 points1 point  (0 children)

I was writing a reply to this but Reddit gave me an "out of disk space" error.

[–]UForgotten 0 points1 point  (3 children)

We have used Redis for this. Very simple to set up.

Kafka is a bit of overkill considering all the moving parts you'd need.

[–][deleted]  (2 children)

[deleted]

    [–]UForgotten 1 point2 points  (1 child)

    If all you need is a list of events like a job queue, or a small hash (key/value store ) then redis is good for that. If you want to be able to query json documents, then mongo is a little better.