DDoS plan: split the cleaning entrance from the database

DEF in Hong Kong, Tokyo, Los Angeles, Seattle, Silicon Valley and Singapore is the entrance. Orders stay on a same-city dedicated server or GIA. A large cleaning figure does not make normal traffic faster. Keep match processes out of aggressive cleaning.

A DDoS server answers whether the entrance is still there when traffic is hostile. It does not answer how fast the database writes. Cleaning capacity, business bandwidth and latency for normal visitors are three different things. The entrance and the database have to be able to stop independently, or one cleaning event stops orders too.

A hard-disk platter

DEF on the entrance, a business box for the ledger

Mainland entrance: Hong Kong DDoS server. Japan: Tokyo DDoS server. North America: Los Angeles DDoS server, Seattle DDoS server or Silicon Valley DDoS server. Southeast Asia can use Singapore DDoS server. The shared prefix is DEF.

Do not put orders and accounts on the DEF box. In Hong Kong the ledger uses Hong Kong dedicated server or, when the return path matters more, Hong Kong CN2 GIA server. When cleaning engages, the entrance can shift into mitigation while the database in the same city keeps writes that already passed the application. If the database is the same machine as the entrance, cleaning stops writes too.

Read both numbers, then look for false positives

A quote that says “100 Gbps protection” is usually cleaning capacity. The business port may still be 50 or 100 Mbps. A large cleaning figure does not make the normal page faster. The two numbers are explained in DDoS server bandwidth. The layout is the DDoS protection plan. Do not put a match process behind aggressive cleaning by default. A false positive looks like the whole room hitching. The login page can sit there. That is the same role split as the game plan.

Test twice. Once with no attack, from a real visitor network, and confirm cleaning is not dropping good traffic and TTFB is close to the box without DDoS. Once after a planned drill or a real event, confirm the entrance still resolves and the database did not stop writing with it. A ping to the DEF address from inside the room has verified neither.