Community
Most financial systems are designed to handle outages in one or another way. However, even if redundancy is incorporated into the system’s architecture it is not uncommon to see that insufficient attention is paid to actually verifying that it will work out. In our practice, we have encountered situations when no more than eight hours (a single work shift) was allocated to check all possible failover combinations within rather complex systems.
Taking into account the level of competition in the industry, exchanges might put more effort into operational testing of their platforms and ensure that failover, monitoring and reconciliation tests are in place.
Another point: in contrast to the crossing engines that ought to have a primary processing node and require architecture complexities to handle their failover, market data dissemination, by its very nature, can be implemented with relative ease in the active-active fashion. In this case it is not necessary to identify the exact chip responsible for the problem, it is sufficient to turn off the node.
Anyway it is good to have additional insight for our exchange resilience whitepaper to be released shortly.
This content is provided by an external author without editing by Finextra. It expresses the views and opinions of the author.
Rolands Selakovs Founder at avoided.io
14 February
Laurent Descout CEO at NEO Capital Markets
13 February
Joris Lochy Product Manager at Intix | Co-founder at Capilever
10 February
Alex Kreger Founder & CEO at UXDA
Welcome to Finextra. We use cookies to help us to deliver our services. You may change your preferences at our Cookie Centre.
Please read our Privacy Policy.