When the client can be modified
Evaluate the access SDK shield and establish a secure communication path through client and gateway authentication, link detection and scheduling.
Select SDK shield or DDoS-protected IP according to the game protocol and client modification conditions, and use SCDN to protect the official website, account entrance and update resources.
The official website, login service, resource download and real-time matches use different protocols and have different requirements for delay and connection continuity, so access needs to be planned separately.
Evaluate the access SDK shield and establish a secure communication path through client and gateway authentication, link detection and scheduling.
When it is not possible to integrate the SDK, evaluate DDoS Protected IP forwarding based on protocol, port, and bandwidth requirements.
Use SCDN accelerated version resources; when you need WAF protection for web login and active interfaces, choose the Standard or higher.
Provides Windows, Android, or iOS platform information, as well as server-side protocols and ports.
Evaluate SDK integration or IP forwarding based on client compatibility. Configure web resources separately.
Test login, game play, disconnection and reconnection, and resource updates, and then gradually increase the volume.
Focus on observing the connection success rate, delay and reconnection behavior; adopt appropriate protection configurations for the game business and web portal.
No need. The two should be selected based on whether the client can be modified, the usage protocol and deployment conditions, and can also be combined according to business modules.
SCDN is mainly for website and adapted application access. Non-HTTP game connections need to evaluate the SDK or DDoS-protected IP based on the actual protocol.
Have other questions?Contact a technical advisor
From personal projects to corporate operations, find the protection solution that's right for you.