Campus Integrated Platform

Architecture speedtest

Fixed 100,000-user simulation comparing registration latency against async notification and analytics fan-out. The UI uses shadcn-style cards, button, progress, badge, chart, and table composition.

Run comparison

Default load: 100,000 users, all three architectures, constrained backend profile.

Ready

Registration and fan-out will run together.

100k users

Combined p99 graph

Solid lines are course registration response p99. Dashed lines are fan-out completion p99.

MonolithModularMicroservices
Start the speedtest to draw the combined p99 graph.

Course registration

Latency-sensitive synchronous flow. Modular monolith should usually win because it avoids distributed hops.

response time
ArchitectureAvgp95p99SuccessFailuresCompletedNotes
Run a speedtest.

Normal stage performance

Notification and analytics burst

Async fan-out workload. Microservices should usually win because notification and analytics workers scale independently.

completion time
ArchitectureAvgp95p99SuccessFailuresCompletedNotes
Run a speedtest.

Normal stage performance