This message was deleted.

Hello. It is hard to say much without knowing what the requests actually constitute in terms of size and processing complexity. 60,000 per day doesn't seem much, and I would assume WireMock can handle if given enough resources. That said, I need to mention that WireMock is a developer tool which is neither designed nor tested for use as a long-term deployment in production environments. When you use it in such a way, you will be likely responsible to monitor its memory usage, extract the data via REST API / storage extension, and then clear the caches and accumulated logs. For that there are admin API endpoints too

Thank you for your response. Regarding the complexity of our service, it is relatively straightforward. Its primary function involves mapping one model to another and interfacing with an external API. We have recently implemented WireMock, which is fully recording the incoming and outgoing traffic to/from our service and to/from the external API. Following this integration, we observed on our development environments an increase in latency from approximately 300ms to around 400ms. (which is not really impactful) We are planning to closely monitor this situation as we move forward. Our strategy involves deploying WireMock in the production environment for a brief period. This will enable us to conduct thorough tests using the data recorded during this phase, which we will continue analyzing in an offline setting. Your insights are invaluable, especially regarding WireMock’s capabilities and limitations. We are aware that it’s primarily a development tool and not ideally suited for long-term production deployment. We will ensure to diligently monitor its memory usage, manage data extraction via REST API or storage extensions, and regularly clear caches and logs using the provided admin API endpoints.