Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

The deck we used to raise our seed funding

airbyte.io

Post reply on HN
Print view View original

91–100 of 127 posts

Re: The deck we used to raise our seed funding

#91

Post by jrhizor »

rahimnathwani wrote: post #89

Looking at your GitHub repo, it seems your data sources are Singer/Pipelinewise taps. Is AirByte an orchestration layer for Singer taps/targets, like Meltano or Pipelinewise?

Some of our sources are written from scratch, some are wrappers directly over Singer, and others are wrappers over forks of Singer taps that we've updated/improved. All of our destinations right now do not depend on Singer.

The high level strategy of orchestrating sources/destinations is similar although configuration, state management, source/destination installation/isolation, normalizing data, etc. are quite different.

Re: The deck we used to raise our seed funding

#96

Post by jeanlaf »

Stratoscope wrote: post #95

In the deck and on the website, I see ETL, ELT, and EL(T) but nothing that says what they mean. Maybe I am behind the times, but I wonder: are these something that a typical technically savvy person would be expected to know, like CPU or GPU?

ETL = Extract - Transform - Load ELT = Extract - Load - Transform (so data normalization happens mostly at the destination).

Here's an article that explains the differences and why it's important: https://airbyte.io/articles/data-engineering-thoughts/why-th...

Re: The deck we used to raise our seed funding

#97

Post by Stratoscope »

jeanlaf wrote: post #96
Stratoscope wrote: post #95

In the deck and on the website, I see ETL, ELT, and EL(T) but nothing that says what they mean. Maybe I am behind the times, but I wonder: are these something that a typical technically savvy person would be expected to know, like CPU or GPU?

ETL = Extract - Transform - Load ELT = Extract - Load - Transform (so data normalization happens mostly at the destination). Here's an article that explains the differences and why it's important: https://airbyte.io/articles/data-engineering-thoughts/why-th...

Thanks! Interestingly, that page doesn't define the terms either, but your cheat sheet helped me understand it.

I might suggest giving short definitions whenever possibly unfamiliar terms like these are used.

Re: The deck we used to raise our seed funding

#98

Post by jeanlaf »

graiz wrote: post #94

If I see a team that is 100% guys, as an investor I'm asking what's up with that?

Yup. Diversity is a big focus for us now. Unfortunately, you tend to look for your first employees in your own network, so people you know. Most of our team is also composed of backend/data engineers, and diversity is not easy there. But this is definitely top of mind for us now.
Post reply on HN