I recommend append-only & rollups if it's not a crazy scale. I've seen it handle 250k events daily. Plan your indexes, if you miss on add it concurrently.
Does idempotency help in this type of situation?
Do ticks ever outlive the lease? How is that handled?
this poster gets it
be willing to change paradigm to what works well for you specifically. Gather buy-in towards a specific shape, if there are other devs involved. my teams and I use small sub-branch/stacked PRs in a specific order…
Location: Temecula, CA (US Pacific) Remote: Yes Willing to relocate: No Technologies: TypeScript, React, Next.js, Node.js, Python, PostgreSQL, Supabase, Docker, CRDTs, distributed task queues, CI/CD, agentic AI…
I recommend append-only & rollups if it's not a crazy scale. I've seen it handle 250k events daily. Plan your indexes, if you miss on add it concurrently.
Does idempotency help in this type of situation?
Do ticks ever outlive the lease? How is that handled?
this poster gets it
be willing to change paradigm to what works well for you specifically. Gather buy-in towards a specific shape, if there are other devs involved. my teams and I use small sub-branch/stacked PRs in a specific order…
Location: Temecula, CA (US Pacific) Remote: Yes Willing to relocate: No Technologies: TypeScript, React, Next.js, Node.js, Python, PostgreSQL, Supabase, Docker, CRDTs, distributed task queues, CI/CD, agentic AI…
Location: Temecula, CA (US Pacific) Remote: Yes Willing to relocate: No Technologies: TypeScript, React, Next.js, Node.js, Python, PostgreSQL, Supabase, Docker, CRDTs, distributed task queues, CI/CD, agentic AI…