Hi @Bishnoi Well, we had thought of this earlier and skipped it and there are multiple reasons for same..
- We now have distributed systems and network, if you hit a response on any of the service - if may be down for you, but not down for everyone. Just today, a very tiny fraction of our users were not able to view watchlist on web, it was available for most.
- Unlike other platforms like say Netflix, Instagram or such ones - they do lot of caching and other techniques that we can’t implement as most systems are real-time.
- Our own architecture - when u send say a large order like Iceberg, your order is sent through multiple instances, via multiple locations and likes. Again, one of the orders may not go, but others would.
- These are potentially real-time systems - we there are bad actors who will query them trying to increase loads or with intention to take them down. We had seen such threats earlier as well.
We had to given this a thought earlier, then dropped it for such reasons.