Reason/Context

• Using microcks to mock partner microservices during perf testing

flowchart LR
    K6[k6 Load Test]
    MS[Microservice Under Test]

    subgraph Microcks [Microcks]
        P1[Partner A - Mock]
        P2[Partner B - Mock]
        P3[Partner C - Mock]
    end

    K6 -->|HTTP Request| MS
    MS -->|Calls| P1
    MS -->|Calls| P2
    MS -->|Calls| P3

Description

Microcks currently makes direct MongoDB queries for each incoming mock request — even when handling repeated or identical requests. This results in increased latency and higher DB load, especially under heavy usage.

Implementation ideas

Introducing a caching layer (e.g. in-memory/Redis) could significantly reduce repetitive DB operations and improve performance.