Hi. I have a few questions about the open source v...
# pact-broker
a
Hi. I have a few questions about the open source version of Pact Broker (and Postgres DB), that I hope someone can help with. 1. Are there any limits in the open source Pact Broker, regarding how many pacticipants you can have? 2. In terms of the Pact Broker docker image, once running, how many requests can it deal with, potentially? 3. Do you have any recommended system requirements for the open source Pact Broker and Postgres DB? I have found information relating to PactFlow, but nothing for open source Pact Broker. 4. How big could the Postgres DB potentially grow to? What is a recommended size? I think thats it for now. 😄 Thanks, Alan
y
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
a
Thank you @Yousaf Nabi (pactflow.io) that's really useful information. Thanks for your help.
y
np, it may be worth raising an issue if you don’t mind against perhaps the pact broker or pact broker docker repo, asking the same question, potentially asking the community or any readers what their configuration setup is with a view to updating the documentation somewhere to specify at least some cursory recommendations. The reason I’m not sure of the repo, is that we have the pact broker app, 2 repos which contain a docker image of it, and a kubernetes chart repo here so it probably wants some thought as to where the best place is to show the information to the user and then link to it from any relevant places.
however don’t feel obliged, I can always do that, you may have enough to rock on with for now
m
The perf characteristics of Pactflow are a good guide for the OSS one, so I'd start there. But as Saf said, YMMV
thankyou 1