Workbench/resume/projects/proj_44c7adddc8385d8e72a81720/session/sess_12d5030f0cf94bb5a2d136eb8e0ef992
Event Pipeline Rebuild deep dive
The transcript keeps interviewer prompts, your answers, coach hints, and the retrieval trace visible beside the structured project context.
- session_id
- sess_12d5030f0cf94bb5a2d136eb8e0ef992
- status
- active
- turns
- 3
- latest_trace_hits
- 11
Continue deep dive
Submit the next project answer while keeping the latest interviewer prompt visible above.
Session transcript
Turns are preserved in order so the project narrative can be reviewed, not just improvised once.
interviewer2026-03-24 11:32:25Z
What problem was Event Pipeline Rebuild solving, and what part did you personally own?
user2026-03-24 11:32:25Z
I led the migration from synchronous checkout RPC calls to Kafka events, added idempotency keys and DLQ replay, and cut recovery time by roughly 60%. The main trade-off was eventual consistency, so I added compensating jobs and dashboards.
interviewer2026-03-24 11:32:25Z
Why did you choose Java and Spring Boot for Event Pipeline Rebuild?
Coach hints (1)
Hints stay explicit so the session remains a workbench, not a mystery box.
Explain why Java and Spring Boot fit this project and what it cost you.
Related questions (1)
Related question-bank items are optional supporting context, not the main surface.
Retrieval trace • hybrid • 11 hits
Project deep dive stays anchored on the structured resume_project summary chunk.Slice 5 question-bank retrieval is reused only as supplemental follow-up grounding.resume_project_chunks_synced: 7
source_documentmergedscore 113.0
Question 1: Redis 分布式锁会遇到哪些问题？
Source answer: 要考虑误删、续约、主从切换一致性和超时兜底。
source_documentmergedscore 107.0
Question: Redis 锁怎么回答比较完整？
Answer: 先讲目标，再讲误删、续约、主从切换一致性、超时兜底与监控。
resume_projectmergedscore 100.0
Event Pipeline Rebuild
Rebuilt a synchronous order-processing pipeline into an event-driven architecture for higher throughput. / Built a personal interview prep workbench with grounded QA and structured review flows.
Led the migration from sync RPC to Kafka-driven events across checkout and fulfillment.
Added idempotency keys, DLQ replay, and tracing dashboards to reduce incident recovery time.
Tech stack: Java, Spring Boot, Kafka, Redis, ClickHouse, Next.js, TypeScript, SQLite
source_documentmergedscore 94.0
Question 1: Redis 分布式锁为什么要续约？
Source answer: 因为业务执行时间可能超过锁超时，需要防止锁提前释放。
question_itemmergedscore 62.0
Kafka 重试和死信队列怎么回答？
question_itemmergedscore 62.0
Redis 分布式锁会遇到哪些问题？
question_itemmergedscore 60.0
为什么 ThreadLocal 在线程池里要手动清理？
question_itemmergedscore 59.0
Redis 锁怎么回答比较完整？
source_documentmergedscore 54.0
Question: Kafka 重试和死信队列怎么回答？
Answer: 先讲重试目标，再讲幂等、退避、死信隔离和监控补偿。
question_itemmergedscore 53.0
Redis 分布式锁为什么要续约？
question_itemmergedscore 50.0
ThreadLocal 会导致什么问题？
Project context
Project context stays visible while the conversation evolves.
Rebuilt a synchronous order-processing pipeline into an event-driven architecture for higher throughput. / Built a personal interview prep workbench with grounded QA and structured review flows.
JavaSpring BootKafkaRedisClickHouseNext.jsTypeScriptSQLite
Led the migration from sync RPC to Kafka-driven events across checkout and fulfillment.
Added idempotency keys, DLQ replay, and tracing dashboards to reduce incident recovery time.
Open Interview
Designed parse-review-confirm workflow for interview notes and resume projects.
Implemented Next.js + TypeScript workbench routes with retrieval trace visibility.
Latest prompt
The latest interviewer question stays easy to revisit before answering.
Why did you choose Java and Spring Boot for Event Pipeline Rebuild?