Under the hood of Wiremock: unraveling a performance problem
summary
An investigation of WireMock used as both mock server and proxy revealed serious performance failures: WireMock crashed under about 100 RPS, Kubernetes restarted pods, and a Kubernetes bug even broke a master node. The talk examines the technologies involved (WireMock and Kubernetes), describes the observed failures under load, and analyzes root causes and interactions that led to instability.
AI-written summary · about
chapters (11)
- 0:00Introduction
- 2:13Why we needed mocks
- 4:42Choosing WireMock
- 7:13Reducing test load
- 8:01Memory consumption
- 10:07Proxying performance
- 13:32Linux socket optimizations
- 17:48Kubernetes bug
- 18:51Socket reuse fix
- 21:20Final results
- 22:50Q&A
related talks
32mWiremock: because your microservice needs a buddy when you're testing
38mDoublers in Tests. Wiremock vs Mockito
41mAdvanced HTTP Mocking with
33mMock Me If You Can: Using Mocks in Container Applications for Integration Testing
44mFake It until You Make It! API Integration Testing with Containers & WireMock
31mThe power of mocking APIs
13mSpeed up writing tests with Wiremock Spring Boot
25mResilience testing in modernization projects