docs: README 핵심 결과 정리

[ohhalim]

변경 사항

• README 첫 문단을 핵심 기능과 성능 개선 흐름 중심으로 정리
• 설계 판단 섹션 추가

Summary by CodeRabbit

• Documentation
  • Enhanced README with detailed exchange backend capabilities, including limit orders, real-time settlement propagation, and wallet management
  • Added performance metrics and bottleneck analysis comparisons
  • Included design decisions for asynchronous order processing
  • Added current limitations section documenting worker queue metrics

[coderabbitai]

Caution

Review failed

The pull request is closed.

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: fed7d640-a1f1-4427-89c4-a8d0869e845a

📥 Commits

Reviewing files that changed from the base of the PR and between 9c814da and 8e01c7e.

📒 Files selected for processing (1)

• README.md

---

📝 Walkthrough

Walkthrough

README.md documentation is expanded to describe async order acceptance architecture: implementation scope and performance metrics are added to the introduction, design trade-offs are documented in a new table, and current limitations after 202 Accepted transition are clarified with updated terminology.

Changes

Async Order Processing Documentation

Layer / File(s)	Summary
Project overview and performance context README.md	Project introduction expands to include implementation scope (limit orders, matching, settlement, wallet, ledger), bottleneck separation strategy (WebSocket, market lock, worker queue), and Before/After performance metrics (order p95, orderbook broadcast, trade feed p95, throughput) measured via k6/Prometheus/Grafana.
Async order design decision table README.md	New "Design Decisions" section documents five architectural decisions: API response contract, transaction-worker separation, REJECTED failure handling, orderbook broadcast without market lock, and Outbox/Kafka propagation, each with rationale.
Current state, limitations, and terminology updates README.md	Obsolete remaining-limits sentence removed, validation label changed to "scope confirmation," and new "Current Limitations" section documents 202 Accepted scope (HTTP response vs. worker completion separation) alongside remaining queue depth and latency metrics.

Possibly Related PRs

• ohhalim/CoinFlow#81: Introduces the async order acceptance flow documented in this PR's README expansion, covering HTTP 202 split, worker/matching/settlement responsibilities, and state transitions.

Poem

A rabbit hops through docs so fine,
Explaining each design line by line,
Bottlenecks split, performance grows,
Yet honest limits—the story shows! 🐰📊

🎯 1 (Trivial) | ⏱️ ~3 minutes

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch docs/readme-summary-design-decisions

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}