3 ms·

Seems like strange choices for "CloudQuery vs Others". Why not compare against FiveTran, Airbyte, Meltano or other EL tools? Also, It'd be nice to know what th

• yevpats 4y ago
  Great question! We specifically started with connectors/plugins to cloud infrastructure providers and other infrastructure vendors - This is why most of our users migrated and/or compared us to the tools specified here (https://www.cloudquery.io/docs/cq-vs-others/overview https://www.cloudquery.io/docs/cq-vs-others/overview). There are no connectors for AWS, GCP, Azure in FiveTran, Airbyte, Meltano but as we extend the number of our source plugins I believe this question will come up more and we will add those products as well to our comparison list. The protocol is just standard/plain gRPC (https://www.cloudquery.io/docs/developers/architecture https://www.cloudquery.io/docs/developers/architecture). Protobuf is defined here - https://github.com/cloudquery/plugin-sdk/tree/main/internal/pb https://github.com/cloudquery/plugin-sdk/tree/main/internal/... Basically just the normalized, verified data + metadata, types
  • elchief 4y ago
    understood :) thanks for the reply
  • tomrod 4y ago
    Will you adopt the singer interfaces? That's what Meltano does, and it's chefs kiss.
    • yevpats 4y ago
      Interesting. We will take a look at this even though we usually build our own connectors due the huge concurrency/speed advantages when using CloudQuery SDK.
• sghosh2 4y ago
  Much more of a focus on security and infrastructure than other EL tools. Like these security policies for example - https://www.cloudquery.io/docs/core-concepts/policies https://www.cloudquery.io/docs/core-concepts/policies