flow

Estuary Technology | Backend Engineer | Developer Evangelist | Rust, Go | REMOTE OR HYBRID | UTC-7 to UTC+2 Regional offices in NYC & Columbus, OH Estuary (https://www.estuary.dev/) is the first real-time Data Operations platform for future-proof pipelines, including both historical and real-time data set up in minutes. Our team is rapidly growing, VC funded and led by two successful, repeat founders. We primarily develop in Rust and Go and are heavily built on top of gazette which is an internally developed streaming engine. Flow: https://github.com/estuary/flow Gazette: https://gazette.readthedocs.io/en/latest/ Backend Engineer: https://www.estuary.dev/about/#backend Developer Evangelist: https://www.estuary.dev/about/#developerevangelist ^This is an exciting opportunity to make direct impact and shape user perception of a new product t

Estuary Technology | Backend Engineer | Rust, Go | REMOTE OR HYBRID | Regional offices in NYC & Columbus, OH Estuary (https://www.estuary.dev/) is the first real-time Data Operations platform for future-proof pipelines, including both historical and real-time data set up in minutes. Our team is rapidly growing, VC funded and led by two successful, repeat founders. We primarily develop in Rust and Go and are heavily built on top of gazette which is an internally developed streaming engine. Flow: https://github.com/estuary/flow Gazette: https://gazette.readthedocs.io/en/latest/ We are looking for a backend engineer who is early in their career (around 1-3 years of industry experience) to join our team. For engineers who have an unquenched curiosity and drive to solve complex distributed systems problems, this is an opportunity to advance yo

Estuary Technology | Junior Backend Engineer | Rust, Go | REMOTE OR HYBRID | Regional offices in NYC & Columbus, OH Estuary (https://www.estuary.dev/) is the first real-time Data Operations platform for future-poof pipelines, including both historical and real-time data set up in minutes. Our team is rapidly growing, VC funded and led by two successful, repeat founders. We primarily develop in rust and go and are heavily built on top of gazette which is an internally developed streaming engine. Flow: https://github.com/estuary/flow Gazette: https://gazette.readthedocs.io/en/latest/ We are looking for a junior backend engineer with 2-3 years of industry experience. For engineers who have an unquenched curiosity and drive to solve complex distributed systems problems, this is an opportunity to advance your career alongside a team of subject

Estuary Technology | Developer Evangelist | Backend Engineer | Rust, Go | REMOTE OR HYBRID | Regional offices in NYC & Columbus, OH Estuary (https://www.estuary.dev/) is an open-source DataOps platform that empowers engineering teams to build real-time, data-intensive applications at scale with minimal friction. We primarily develop in rust and go and are heavily built on top of gazette which is an internally developed streaming engine. Flow: https://github.com/estuary/flow Gazette: https://gazette.readthedocs.io/en/latest/ Our team is rapidly growing, VC funded and led by two successful, repeat founders. Estuary offers full health benefits, competitive salary, unlimited PTO, 401K, equity, and an inclusive, supportive work environment to expand your skills among a passionate team. Open Positions: -Developer Evangelist https://www.estuar

It does seem like a weird bug that this would cause errors https://github.com/estuary/flow/runs/5642694619?check_suite_... seems like it should be some kind of warning instead of an error?

> I'd love to be able to have a "relational database" that is also some "NoSQL" databases (since there's a few major useful paradigms there) that just takes care of this for me. I imagine I'd have to declare my schemas, but I'd love it if that's all I had to do and then the DB handled keeping sync and such. You might be interested in what we're building [0] It synchronizes your data systems so that, for example, you can CDC tables from your Postgres DB, transform them in interesting ways, and then materialize the result in a view within Elastic or DynamoDB that updates continuously and with millisecond latency. It will even propagate your sourced SQL schemas into JSON schemas, and from there to, say, equivalent Elastic Search schema. [0]: https://github.com/estuary/flow