Ai Coding And Product Systems easy
Your ChatGPT-style assistant must let users reopen old threads, edit a past message to create a branch, and search their history. How should conversations be stored?
- A Store each message as a row keyed by conversation ID, with a parent ID for branches.
- B Store only the latest prompt string sent to the model, since it holds the full prior conversation.
- C Keep conversations only in the model's context window, since the model remembers past sessions.
- D Store each thread as a single text blob that is rewritten in full every time a new message arrives.
Answer: A. Store each message as a row keyed by conversation ID, with a parent ID for branches.
**Per-message rows** with parent links cost more schema design up front but support branching, search, and rebuilding the prompt under any token budget. Storing only the last prompt (B) looks complete, but that prompt may be summarized or truncated, so the original messages are lost. A single blob is acceptable only for small, append-only threads that never branch or get searched.
One system design question a day, with spaced repetition so the ones you miss come back.
Get the appRelated questions
- Your assistant uses a classifier to route queries to a small or large model, which saves 60% of GPU spend. Analysis shows about 20% of hard queries are misrouted to the small model, which then gives confident wrong answers, and regenerate clicks on those threads have doubled. What should you do?
- Your workspace AI retrieves the top-k chunks from a shared vector index and passes them to the model with ACL metadata and a system prompt saying 'only use documents this user can access.' A user just received an answer quoting a private HR page they cannot open. What is the correct fix?
- Your support bot answers billing questions. One user has asked the same refund question three times, and retrieval confidence for that topic is low. What should the bot do next?
- Your AI review system receives a 4,000-line pull request spanning 60 files. Sending the whole diff in one prompt yields shallow, generic comments, and real bugs in files near the middle of the diff are missed. How should you structure the review?
- In your ChatGPT-style assistant, power users keep single threads running for weeks, reaching about 150K tokens. Cost per turn keeps climbing, latency is rising, and the model increasingly misses facts from early in the thread. What should you do?
- Your workspace AI filters retrieval using ACLs stored in the vector index, which is rebuilt nightly. An admin removes an employee from a confidential project page, but for the rest of the day the employee can still get AI answers drawn from it. What is the right fix?