---
title: "Li emily (@emily19980210) | Hashnode"
description: "Li emily (@emily19980210) writes on Hashnode. Read their latest articles and follow their work."
url: "https://hashnode.com/@emily19980210"
---

@emily19980210

# Li emily

@emily19980210 · Joined July 2025

### [Architecting a Unified China A-Share Real-Time Market Data API Pipeline for Production Trading](https://emily19980210.hashnode.dev/architecting-a-unified-china-a-share-real-time-market-data-api-pipeline-for-production-trading?utm_source=hashnode&utm_medium=feed)

Picture this: your quantitative research team has spent weeks perfecting a mean-reversion algorithm targeted at Shanghai and Shenzhen liquid equities. In your backtesting sandbox, built on locally arc

4 min read · [emily19980210.hashnode.dev](https://emily19980210.hashnode.dev/architecting-a-unified-china-a-share-real-time-market-data-api-pipeline-for-production-trading?utm_source=hashnode&utm_medium=feed)

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

### [US Stock Data API Compared: Futu API vs. AllTick WebSocket for Real-Time Market Feeds](https://emily19980210.hashnode.dev/us-stock-data-api-compared-futu-api-vs-alltick-websocket-for-real-time-market-feeds?utm_source=hashnode&utm_medium=feed)

If you’ve ever built a personal market monitor or a lightweight quant tool, you know that the reliability of your “US stock data API” can make or break the whole project. I learned this the hard way w

5 min read · [emily19980210.hashnode.dev](https://emily19980210.hashnode.dev/us-stock-data-api-compared-futu-api-vs-alltick-websocket-for-real-time-market-feeds?utm_source=hashnode&utm_medium=feed)

[1](https://hashnode.com/posts/us-stock-data-api-compared-futu-api-vs-alltick-websocket-for-real-time-market-feeds/6aa0f3d01994c33e623c567a) [Sep 9](https://hashnode.com/posts/us-stock-data-api-compared-futu-api-vs-alltick-websocket-for-real-time-market-feeds/6aa0f3d01994c33e623c567a)

### [Handling Time Boundaries in Real-Time Hong Kong Stock API Data: A Developer’s Field Guide](https://emily19980210.hashnode.dev/handling-time-boundaries-in-real-time-hong-kong-stock-api-data-a-developer-s-field-guide?utm_source=hashnode&utm_medium=feed)

If you have ever built a real-time market data pipeline for Hong Kong stocks, you know the pain: WebSocket connections are straightforward, but time is not. Prices, volumes, and timestamps look simple

8 min read · [emily19980210.hashnode.dev](https://emily19980210.hashnode.dev/handling-time-boundaries-in-real-time-hong-kong-stock-api-data-a-developer-s-field-guide?utm_source=hashnode&utm_medium=feed)

[Sep 2](https://hashnode.com/posts/handling-time-boundaries-in-real-time-hong-kong-stock-api-data-a-developer-s-field-guide/6a97c3c65d952e257213cc38)

### [Building a Reliable Data Validation Layer for Your Hong Kong Stock API Feed: Detecting Silent Gaps and Missing Ticks](https://emily19980210.hashnode.dev/building-a-reliable-data-validation-layer-for-your-hong-kong-stock-api-feed-detecting-silent-gaps-and-missing-ticks?utm_source=hashnode&utm_medium=feed)

When I first started building data-driven content around Hong Kong equities, I assumed that a live WebSocket connection meant a complete data stream. That assumption cost me credibility when a reader

5 min read · [emily19980210.hashnode.dev](https://emily19980210.hashnode.dev/building-a-reliable-data-validation-layer-for-your-hong-kong-stock-api-feed-detecting-silent-gaps-and-missing-ticks?utm_source=hashnode&utm_medium=feed)

[Aug 26](https://hashnode.com/posts/building-a-reliable-data-validation-layer-for-your-hong-kong-stock-api-feed-detecting-silent-gaps-and-missing-ticks/6a8e590e7aae7aa77d8777ee)

### [Building a Caching Layer for Historical K-Lines from a Gold Real-Time API](https://emily19980210.hashnode.dev/building-a-caching-layer-for-historical-k-lines-from-a-gold-real-time-api?utm_source=hashnode&utm_medium=feed)

When I first built my gold market analysis system, I treated the gold real-time API as a simple data source: whenever my code needed historical K-lines, it made a request. That worked until I started

5 min read · [emily19980210.hashnode.dev](https://emily19980210.hashnode.dev/building-a-caching-layer-for-historical-k-lines-from-a-gold-real-time-api?utm_source=hashnode&utm_medium=feed)

[Aug 19](https://hashnode.com/posts/building-a-caching-layer-for-historical-k-lines-from-a-gold-real-time-api/6a854c9a63293e96d2cd62f4)
