Hey up!
I think alot of these are going to be depends, as the Pact Broker is highly configurable, and would depend on your use cases
1. There isn’t a physical limit in the code
2. It would be advised you run your own load test, based on your use case, on your infrastructure. The PactFlow created a load test which you can use the same principles and modify the code slightly for your own Pact Broker
https://docs.pactflow.io/docs/on-premises/installation/load-testing/
3. I can’t see anything from a cursory glance, that may be an active choice by the developers not to include, due to the multiple options for deployment, but I would go with those values from PactFlow and you may be able to dial them back a little bit but staying in those ranges is probably good (and well tried and tested from the PactFlow team)
4. 25GB is recommended, going by
https://docs.pactflow.io/docs/on-premises/system-requirements based on the same premise as 3
In production, you would typically run with a proxy such as nginx and load balancer, so its useful to take those into consideration
I’ve in the past at client sites ran the broker via AWS CF templates using ECS with a Postgres RDS instance, very similar to this diagram
https://docs.pactflow.io/docs/on-premises#example-aws-deployment-using-ecs