Update Redis Architecture authored by Nicolas Pope's avatar Nicolas Pope
# Event # Event
Redis streams are used to inform about update events, typically "create", "delete" and "update" for various resource types. The data itself should be stored within regular Redis keys and not included in the event, the event just details which resource has changed. Redis streams are used to inform about update events, typically "create", "delete" and "update" for various resource types. The data itself should be stored within regular Redis keys and not included in the event, the event just details which resource has changed.
The owner of events is the generator of that event, that services defines the structures.
Should each event type have it's own stream? The stream keys can then be specific to that type. The downside is consumers need to watch for many different streams and ordering might become a problem.
# Commands # Commands
Command streams instruct other services to perform a CRUD operation or issue an instruction of another kind. As an example, one service might wish to query a resource but finds that Redis does not contain that data yet (or it expired). To obtain the data it needs to send a query request and then respond to an update event. Command streams instruct other services to perform a CRUD operation or issue an instruction of another kind. As an example, one service might wish to query a resource but finds that Redis does not contain that data yet (or it expired). To obtain the data it needs to send a query request and then respond to an update event.
# Metrics
\ No newline at end of file