How to process and store a huge number of tracking requests?

Question

Highload

There is a JS script similar to Ya.Metrika and Google Analytics that clients install on their sites. The script sends data about each visitor to my server.
How, from an architectural point of view, to organize the processing and storage of a potential huge data stream, for example, using Azure tools?
Things are of interest, such as the API request handler itself, where the data will directly arrive from the JS tracker, and the storage where the API will add this data.
The data will be retrieved by a dashboard-like web application, so quick data retrieval and sorting is relevant.
Ideas that come to mind:
- Have a load-balancer that will shove processing requests into the application API in the DCs closest to the client (region)
- Have distributed storage (look towards CosmosDB)

Answer 1

see YouTube
"How VK inserts data into ClickHouse from tens of thousands of servers - Yuri Nasretdinov"