flow
github-actions
flow | github-actions | |
---|---|---|
10 | 7 | |
506 | 1,668 | |
5.3% | 0.8% | |
9.7 | 6.6 | |
4 days ago | 13 days ago | |
C++ | TypeScript | |
GNU General Public License v3.0 or later | Apache License 2.0 |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
flow
-
Unexpected downsides of UUID keys in PostgreSQL
We use a macaddr8 that embeds a wall-clock timestamp (so they're ascending order, achieving data locality) with some additional randomness. It's worked really well for us:
https://github.com/estuary/flow/blob/master/supabase/migrati...
we use macaddr8 instead of bigint, because it has a postgres serialization / JSON encoding which lossless-ly round-trips with browsers and it works well with PostgREST. The same CANNOT be said for bigint, which is a huge footgun.
-
Need Advice on Real-Time Data Synchronization from PostgreSQL to BigQuery: Airbyte vs. CloudQuery?
I can't claim to know much about CloudQuery, but we are an open-source platform with CDC connectors from PostgreSQL and materializations to BQ and elsewhere. We also have fully-managed connectors if you don't want to deal with hosting.
-
DAG orchestration for streaming data?
This is essentially how we model things in Flow (disclosure: I work there). We call them Derivations, which are data products that are built (derived) from other data products. Each data product (we call them Collections) is backed by a set of append-only logs, so they can be read by many different consumers at different times. IDK if our product can work for you since we don't (yet) support stuff like MQTT, but there's a pretty generous free tier if you'd be able to push the data over HTTP. Either way, I just think it's cool that others have independently arrived at similar ideas about how to model streaming tasks!
- quickly replace a small airbyte instance in my stack
-
Advise on incremental process of Kafka data on Snowflake
We Estuary Git Docs have an open-source connector for Kafka -> Snowflake that could perform the tasks of a) flattening the data and b) removing duplicates via exactly once end to end delivery
-
Ask HN: Who is hiring? (September 2022)
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 that brings a fresh experience to working with real-time data.
As this is a unique role, we are open to a variety of personas (data engineers, backend developers, Solutions Engineers and of course DevRel professionals).
Estuary offers full health benefits, competitive salary, unlimited PTO, 401K, equity, and a culture that values trust, transparency, and a flexible work environment to optimize your work/life balance.
To apply, send your resume and any questions to [email protected]
-
Who's Hiring? - August 2022
Flow Gazette We are looking for a backend engineer who is early in their career (around 1-3 years of industry experience) to join our team.
-
Ask HN: Who is hiring? (July 2022)
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 matter experts.
We are focused on expanding our catalog of open-source data connectors and building out our managed service platform.
ESTIMATED COMPENSATION: $110,000 - $150,000.
Estuary offers full health benefits, competitive salary, unlimited PTO, 401K, equity, and a culture that values trust, transparency, and a flexible work environment to optimize your work/life balance.
Email your resume to [email protected] to apply!
-
On 2022-04-05, the default branch will be renamed from “master” to “main”
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?
-
Ask HN: Is there a way to subscribe to an SQL query for changes?
where you'd subscribe for live updates.
[1]: https://github.com/estuary/flow
github-actions
- On April 4, 2022 GitHub Action will force you to use "main" instead of "master" branch
-
On 2022-04-05, the default branch will be renamed from “master” to “main”
Aha: it's because the project team merged this change that intentionally fails the build when people have pinned their workflows to use the deprecated branch name: https://github.com/google-github-actions/setup-gcloud/pull/5...
(that makes sense; there has been a warning in place for a long time, and pinning to a name can be risky when the content within that reference may change over time)
-
Learning Journal 2: Brainstorm a deployment process from GitHub to Google App Engine and Cloud SQL (Part 1)
In the process of finding the answer, I discovered that the small actions are pretty much open-source. I can also go directly to their respective code repositories and learn about them. To run gsutil, I will need a setup-gcloud action.
-
Build an Uptime Monitoring System in Ruby with GCE, Cloud Storage, and PubSub
Like many aspects of the cloud, there are many ways to achieve the same result, but modern software engineering encourages CI/CD processes for several good reasons. As such, we will focus on deploying our service from Github Actions using setup-gcloud
- How to deploy Cloud Functions with GitHub Actions
-
GitOps on Kubernetes - The easy way
GKE_SA_KEY: The service account used for the project with the Base64 encoded JSON service account key. More info available here
What are some alternatives?
realtime - Broadcast, Presence, and Postgres Changes via WebSockets
wait-for-jobs - Wait for the specified jobs in the same run to be complete successfully before proceeding, helpful to prestart the job
timely-dataflow - A modular implementation of timely dataflow in Rust
devops-toolkit
rethinkdb_rebirth - The open-source database for the realtime web.
deploy-appengine - A GitHub Action that deploys source code to Google App Engine.
pldb - PLDB: a Programming Language Database. A computable encyclopedia about programming languages.
rubygems - Library packaging and distribution for Ruby.
Hasura - Blazing fast, instant realtime GraphQL APIs on your DB with fine grained access control, also trigger webhooks on database events.
blackbox_exporter - Blackbox prober exporter
PipelineDB - High-performance time-series aggregation for PostgreSQL
actions-cloud-functions