Hey folks 👋 not sure if it is a feedback or request or just a general enquiry, but I was wondering if anyone else has the same use case. We are aiming to use the platform in terms of

Powered by airbyte

, where our customers would be able to define multiple integrations for different sources. IIUC right now, if two customers want to connect 5 different google analytics views that are synced into 5 different s3 buckets, i would have to create 10 different google analytcis

sources

, a number of different s3

destinations

(I suppose i could be clever and reuse some of destinations by using namespaces and prefix) and 10 different

connections

. Was wondering if anyone has experience using airbyte in such scenario and whether a huge amount of entities can become a problem down the road. If so what is the max capacity of a single deployment

@Igor Sechyn I know some users have +100 connections. Because the UI doesnt handle pagination can be a problem to manage, so they use the API to manage this. If you deploy Airbyte with docker at the moment you're limit to vertical scale but if you plan to use Kubernetes is much easier to scale the nodes and have a lot of parallel connections.

If you have any other question feel free to send here 😃