Performance and Scalability
Contractual SLAs
Section titled “Contractual SLAs”The SLAs below are contractual values, monitored continuously in production. Deviations trigger alerts for Guardline's operations team.
| Operation | Latency (SLA) |
|---|---|
| Transaction evaluation in the engine | P95 of 300ms |
| Restrictive list lookup | < 100ms |
| Automatic case creation | < 500ms |
| Scoring calculation | < 300ms |
Values represent the 95th percentile or the upper bound observed under normal operating conditions. Monitoring is continuous and latency data is available to the operations team.
Horizontal scalability
Section titled “Horizontal scalability”The architecture supports horizontal scalability per component. Each part of the platform can be sized independently according to the institution's demand:
- Decision engine: additional replicas can be provisioned to absorb transaction volume peaks while keeping latency within the defined SLAs.
- Module backends: each module (ONP, FPP, CMP) scales independently. An institution with high onboarding volume and low case volume, for example, can run more ONP replicas without changing the sizing of the other modules.
- Database: supports read replicas, distributing query load without affecting write operations.
- Cache: supports clustering, allowing read load to be distributed and increasing in-memory storage capacity.
Sizing is adjusted to match the institution's operational volume. The platform does not impose fixed limits on transactions, onboardings or cases; capacity follows the allocated infrastructure.
Monitoring
Section titled “Monitoring”Performance metrics are collected continuously and compared against the contractual SLAs. When a metric approaches or exceeds the defined threshold, alerts are generated automatically for the operations team, which acts to resize or investigate the cause.