---
title: "Comment by Arnold Holm on \"Architecting a Unified China A-Share Real-Time Market Data API Pipeline for Production Trading\" | Hashnode"
description: "The example finishes history() before connecting stream_ticks(). An update between those two steps can be missing even if later duplicates are removed. I would"
url: "https://hashnode.com/posts/architecting-a-unified-china-a-share-real-time-market-data-api-pipeline-for-production-trading/6ab3497156de5d18f14cae26/comment/6abe7e9bcb359656510b79ca"
---

[Discussion](https://hashnode.com/posts/architecting-a-unified-china-a-share-real-time-market-data-api-pipeline-for-production-trading/6ab3497156de5d18f14cae26)

Comment [Architecting a Unified China A-Share Real-Time Market Data API Pipeline for Production Trading](https://hashnode.com/posts/architecting-a-unified-china-a-share-real-time-market-data-api-pipeline-for-production-trading/6ab3497156de5d18f14cae26)

[Arnold Holm](https://hashnode.com/@stratcorealpha)

[Oct 1](https://hashnode.com/posts/architecting-a-unified-china-a-share-real-time-market-data-api-pipeline-for-production-trading/6ab3497156de5d18f14cae26/comment/6abe7e9bcb359656510b79ca)

The example finishes history() before connecting stream\_ticks(). An update between those two steps can be missing even if later duplicates are removed. I would connect and buffer the stream first, backfill through a recorded watermark, then merge the buffered events with an explicit overlap rule. A fixture with a tick arriving during the history request would test that handover directly.
