39 karma · joined June 22, 2018
- Infrastructure as code is not the norm. Most tools are UI-focused. It's the equivalent of setting up your infra via the AWS UI.
- Prod/Staging/Dev environments are not the norm
- Version Control is not a first class concept
- DRY and component re-use is exceedingly difficult (how many times did you walk into a meeting where 3 people had 3 different definitions of the same metric?)
- API Interfaces are rarely explicitly defined, and fickle when they are (the hot name for this nowadays is "data contracts")
- unit/integration/acceptance testing is not as nearly as ubiquitous as it is in software
On the bright side, I think this means DE doesn't need to re-invent the wheel on a lot of these issues. We can borrow a lot from software engineering.
It's so refreshing to see a product try to reinvent something so core to developers everywhere. Really excited to see where this goes!
Let's say the year is 2012 and Redshift is introduced, completely changing how organizations can generate insights from their data. Running your own datacenter? good luck waiting for the ops team to install something similar! It might take you a couple of quarters assuming they are already competent at it. On the Cloud? Press a few buttons and you're off to the races.
velocity is a competitive advantage
Extensive user surveys prior to this change didn't uncover a single user whose workflow would be impacted.
Just some context :)
I work at Airbyte and am genuinely curious about your view.
All connectors and the core functionality of Airbyte will _always_ be open source and free to use. You will always be able to download and operate an instance of Airbyte, containing all connectors and ELT features (whether for personal projects or business operations in your company) for free.
However, there are some things that we might offer as a monetized product in the future, such as:
* enterprise compliance requirements (E.g SOC2)
* SSO
* Hosting Management
Hope this clarifies the direction we’re taking.
More broadly as an ELT tool, Airbyte is focused on supporting the long tail of integrations. The number of data silos is increasing rapidly, and it's intractable for a single engineering team or company to integrate with them all. So as an OSS tool, Airbyte provides a core platform for replicating data (e.g: a UI, scheduling, logging, state management, etc..) and the most popular connectors out of the box, then gets out of the way of its users. If you need a connector you need that Airbyte doesn't already provide, you can implement a Docker image which conforms to the Airbyte protocol, then start using it in your Airbyte instance without ever needing to go through us (Although many users do end up contributing their connectors back to the core codebase).