Blog Sections Open
Preparing MODX Evo and Revo Sites for DDoS Pressure
A CMS alone will not absorb multi-gigabit junk traffic, so DDoS resilience starts with hosting, edge protection, and request-layer strategy rather than snippet tweaks.
When teams ask how well Evo or Revo can survive a large DDoS attack, the honest answer is that the CMS is only a small part of the story. A multi-gigabit flood is primarily a network and hosting problem.
What matters most
- upstream protection from the host or CDN
- caching and edge delivery
- request filtering before PHP executes
- clear isolation between dynamic and static surfaces
Recommendation
Do not plan DDoS resilience at the template level. Put rate limiting, edge caching, and upstream mitigation first; then make sure the site can degrade gracefully under stress.
Why eForm Messages Can Disappear on the Home Page
If eForm validates and sends correctly on inner pages but not on the homepage, compare the homepage template and request flow before changing the form logic itself.
Why Database Time Is Not Zero Even When Query Count Is Zero
A zero query count in parser stats does not always mean truly zero database-related overhead; some measured timings can still include framework or connection-layer work.