Live data from Hacker News

Show HN: I built an open-source data pipeline tool in Go

github.com

31–40 of 49 posts

Re: Show HN: I built an open-source data pipeline tool in Go

#34

Hi Burak, thanks for posting! We're looking for a tool in this space and i'll take a look. Does Bruin support specifying and visualizing DAGs? I didn't see that in the documentation via a quick look, but I thought to ask because you may use different terminology that can be a substitute.

By using the vscode extension, you can see the lineage of the pipeline (visualization of dag with other words)

Re: Show HN: I built an open-source data pipeline tool in Go

#35

Hi Burak, thanks for posting! We're looking for a tool in this space and i'll take a look. Does Bruin support specifying and visualizing DAGs? I didn't see that in the documentation via a quick look, but I thought to ask because you may use different terminology that can be a substitute.

hey, absolutely. take a look at here: https://bruin-data.github.io/bruin/vscode-extension/overview...

Re: Show HN: I built an open-source data pipeline tool in Go

#36
Hi, Burak, it looks interesting. I was wondering, do you know about connect? Maybe you can take advantage of some of its ready-made components. In addition, it is also developed using Go

- https://docs.redpanda.com/redpanda-connect/home/

- https://github.com/redpanda-data/connect

Re: Show HN: I built an open-source data pipeline tool in Go

#37
post #36

Hi, Burak, it looks interesting. I was wondering, do you know about connect? Maybe you can take advantage of some of its ready-made components. In addition, it is also developed using Go - https://docs.redpanda.com/redpanda-connect/home/ - https://github.com/redpanda-data/connect

hey, I didn't know that, definitely gonna take a look. thanks!

Re: Show HN: I built an open-source data pipeline tool in Go

#38
post #25

Congrats Burak, I can tell a lot of work has gone into this. If I may recommend, a comparison of this project with similar other/state-of-the-art projects would be really good to have in your documentation set for others to understand how your approach differs from them.

that's definitely coming, thanks!
Post reply on HN