Load testing (terhelés-teszt)

DEFINITION

Measuring how a web shop or SaaS system behaves under simulated heavy load. Critical before Black Friday or Christmas for e-commerce, before summer peak for hospitality, before school start for education platforms. Tools: k6 (modern, free), Apache JMeter (legacy but powerful), Artillery, Locust. Measures: max concurrent users, response time under load, when errors start. Typical Hungarian e-commerce load test: HUF 200-600k, 1-2 weeks. Catches many problems before launch.

RELATED TERMS06

Threat model→
A structured exercise that walks the system's actors, attack surface, risks, and controls. Day one of every DField project · before any code.
Penetration test (pentest)→
Manual + tooled attack simulation that reveals what an attacker could achieve. We deliver findings as PRs in your repo, not an 80-page PDF.
DevSecOps→
Security as a continuously-running CI step (SAST, DAST, SCA, IaC scan), not an annual project. Runs against every push; every sprint closes at least one security bug.
MFA (Multi-factor auth)→
Two or more factors (TOTP, WebAuthn, biometric) beyond a password. Table-stakes in SaaS today · enterprise procurement disqualifies you without it.
SOC 2→
A US audit framework for confidentiality, integrity, availability, and privacy controls. For SaaS, the Type II audit (6–12 months of observation) is the standard enterprise baseline.
ISO 27001→
International standard for Information Security Management Systems (ISMS). Often preferred in Europe instead of or alongside SOC 2. 3-year certification cycle.

MENTIONED IN THE BLOG08