Often among streaming API calls we encounter structures like the one shown below. There may be many message variants, defining scopes across multiple dimensions such as aspect of the system (topic) and purpose of the changes (event):// Snapshot of all markets { "topic": "market", "event": "snapshot", "markets": [ { "ticker": "BTC/USD", "price": 1000000, "volume": 1000 }, { "ticker": "ETH/USD", "price": 10000, "volume": 10000 } ] } // Snapshot of user portfolio { "topic": "portfolio", "event":...

Often among streaming API calls we encounter structures like the one shown below. There may be many message variants, defining scopes across multiple dimensions such as aspect of the system (topic) and purpose of the changes (event):// Snapshot of all markets { "topic": "market", "event": "snapshot", "markets": [ { "ticker": "BTC/USD", "price": 1000000, "volume": 1000 }, { "ticker": "ETH/USD", "price": 10000, "volume": 10000 } ] } // Snapshot of user portfolio { "topic": "portfolio", "event":...