Right now, each batch of events that comes into the /record endpoint makes a query to postgres and a query to clickhouse to determine if the events belong to a new session, an active session, or an ended one. Maybe we could enhance this via the use of a key value store like redis so that we don't need to hit the dbs as often?
Right now, each batch of events that comes into the
/recordendpoint makes a query to postgres and a query to clickhouse to determine if the events belong to a new session, an active session, or an ended one. Maybe we could enhance this via the use of a key value store like redis so that we don't need to hit the dbs as often?