Architectural advice for support system
❔Advice
Our product is a support system that handles conversations both with AI & by humans in multiple different channels. The possibility of presence with live updates made me try convex. That worked well. Now I'm toying with the idea of moving the core tables to convex instead of postgres. Those would be
conversationsconversations, messagesmessages . Messages are written by a support agent, ai or user, they contain text or larger html content. If we succeed we will have many millions of these rows. There will be lists showing the conversations and who's working on what. There will be some dashboards that show things like how long people have waited, how many conversations have status X etc. I totally get that the answer is "it depends", based on how these are used, how we query them etc. But looking for some guidance and limitations to think about.
