"Typically, what happens is that we plan for maybe 2x, 3x load, but when you put things into the internet, you don't have any control. Who is coming in, when they're going to come, how is this going to be used, because that's how the internet is. Any event can potentially trigger it. It could be good for your business. It could be bad actors coming and trying to steal stuff."
"In that situation, what happens? How do you really tackle? You have not planned enough, then, how will you really meet this? What can really break when things go wrong? Many things can go wrong. Your network device can go bad. Your load balance circuit going bad. Your application, your database connections, many things can break, and all can break all at once as well."
The architecture team for a major financial website must plan for unpredictable internet traffic that can exceed planned 2x–3x loads. Traffic surges can originate from legitimate customer demand or from malicious actors, and controls must distinguish and mitigate attacks. Scalable infrastructure must handle volatile market-driven demand while preserving transactional availability. Multiple failure points exist, including network devices, load balancers, applications, and database connections, and these can fail concurrently. Planning should include strategies focused on core goals, detailed tactics for scaling and resilience, and considerations learned during large-scale cloud migration of financial systems.
Read at InfoQ
Unable to calculate read time
Collection
[
|
...
]