Ticker

Introduction

The idea of a ticker plant is being able to subscribe to ticker feeds and be able to aggregate that data into a format that can be useful. Now there are key items that you must consider when building a ticker plant.

1. You can get a million ticks a seconds, that's quotes or trades occuring during a volatile event
2. Every exchange from stocks, crypto, and forex has it's own format hence why we create a ticker plant to format the data.

When approaching high-volume market data ingestion, consider the resources available and realistic constraints. Most deployments must balance sophistication with practical implementation.

Implementation

Each ticker plant you build has the following requirements:

1. It needs to subscribe to exchange / liquidity provider websockets and be able to subscribe to instruments marked to be subscribed through in your mangement layer.
2. Upon subscribing, it should read quotes, trades, or both.
3. Quotes and Trades should be formatted and given a channel name.
4. Stream the data into NATS via that channel name.

Your ticker plant can be that simple of course, there are things you must take into consideration including:

1. What to do if your connection drops
2. How to manage ticker subscriptions when they get enabled/disabled
3. What are exchange requirements to keep connections alive? Pings, heartbeat, etc...