Another framework (Meltano) that uses Singer taps ...
# announcementsc
Christian Franklin
11/23/2020, 9:55 PMAnother framework (Meltano) that uses Singer taps advocates / requires separate Python virtual environment for each tap. Does the Airbyte application model resolve this? I vaguely recall reading that each tap is its own container. Sorry for a newbie question but this came up on conversation recently and hoping someone might shed some light.
s
s
11/23/2020, 9:58 PM
Hi Christian! Certainly a great question.
In Airbyte every connector (source or destination) runs in its own docker image. So any dependencies like virtual env or OS binaries must be contained entirely in the docker image. This has the nice benefit that all the env setup is done at “compile time” i.e: a user running airbyte doesn’t have to think about env setup at all
s
11/23/2020, 10:01 PM
some other benefits of isolating connectors to docker images are:
• clear separation between airbyte core (config API, UI, scheduling, etc..) and the connectors it uses
• as long as a connector image conforms to the Airbyte spec, the author has complete freedom on implementation details e.g: use whatever language, framework, implementation details, etc.. You could even write in assembly if you want! 😜
🤣 1
s
11/23/2020, 10:01 PM
does that answer the question @Christian Franklin?
c
Christian Franklin
11/23/2020, 10:02 PMIt does - I actually just found my Fortran compiler that uses DOS 3.1
🤣 5
airbyte rocket 1
s
s
11/23/2020, 10:03 PM
perrrrrfect