Hi folks, I'm looking for some clarity on the scaling page: https://docs.airbyte.com/operator-guides/scaling-airbyte/#:~:text=In%20general%2C%20you%20would%20only,and%2010%20%2D%20100%20connections%20configured. It says:

In general, you would only encounter scaling issues when running over a thousand connections.

Does this mean that it's OK to have 1000+ connections defined, but not 1000+ connections running at the same time?

Yes, your understanding is correct. The [scaling guide](https://docs.airbyte.com/operator-guides/scaling-airbyte) for Airbyte suggests that you would generally only encounter scaling issues when running over a thousand connections concurrently. This means that while you can have more than a thousand connections defined in your Airbyte configuration, you might start to see performance issues if you attempt to run more than a thousand of those connections at the same time. As a reference point, the typical Airbyte user has 5 - 20 connectors and 10 - 100 connections configured. Almost all of these connections are scheduled, either hourly or daily, resulting in at most 100 concurrent jobs. However, it's important to note that the exact number can vary depending on the resources available to your Airbyte instance and the nature of the workloads you're running. If you're planning to scale up your usage of Airbyte significantly, you might want to consider strategies for managing and monitoring your resource usage to ensure optimal performance.

If you have Airbyte deployed in Kubernetes and have autoscale its possible to achieve 1000+ connection in parallel.

Good to know. So in principle it's just down to resources, as opposed to hitting an Airbyte design limit?

Correct

Perfect, thank you