Software · Commercial · $96K · owned by Yusuf Abdel-Rahman
Steve has not written one for this account. Everything it would read is below.
Every record Steve is allowed to cite
Head of Data Platform
Staff Data Engineer
Software · Commercial · $96K · owned by Yusuf Abdel-Rahman
Steve has not written one for this account. Everything it would read is below.
Every record Steve is allowed to cite
Head of Data Platform
Staff Data Engineer
Site Reliability Engineer
Next step: Streaming ingest scoping session on 2026-07-29
No next step set
Dmitri hit a provider version mismatch applying the workspace module to staging. Pinned the provider to 2.11 and re-ran. Both production and staging workspaces applied cleanly and are now managed from Foundry's existing pipeline.
The initial snapshot on a 400GB orders table held the replication slot open long enough to build 6 hours of WAL on their primary. Enabled chunked snapshotting and set a slot size guard. Steady-state lag settled under 30 seconds.
Post-run webhooks from dbt Cloud are not reaching the refresh endpoint. Signature validation fails because Foundry's egress proxy strips the timestamp header. Ellen is testing a header passthrough rule on their side and will confirm this week.
The first CDC pipeline went to production on July 2, a day ahead of the milestone, and 14 named users are onboarded against a target of 12. Ravi has been benchmarking end-to-end ingest lag against the in-house pipeline his team ran before and said the numbers are holding at roughly a third of what they used to see. He wants to scope streaming ingest for the event data still sitting in S3, and noted that budget for anything beyond the landed contract sits outside his team this year.
Walked the reference architecture against Foundry's stack: raw events land in S3, Postgres is the operational store, dbt handles transforms. Agreed three implementation milestones, staging workspace by June 26, first CDC pipeline in production by July 3, and 12 named users onboarded by July 31. Dmitri asked that all provisioning go through the Terraform provider so nothing is clicked in a console.
Site Reliability Engineer
Next step: Streaming ingest scoping session on 2026-07-29
No next step set
Dmitri hit a provider version mismatch applying the workspace module to staging. Pinned the provider to 2.11 and re-ran. Both production and staging workspaces applied cleanly and are now managed from Foundry's existing pipeline.
The initial snapshot on a 400GB orders table held the replication slot open long enough to build 6 hours of WAL on their primary. Enabled chunked snapshotting and set a slot size guard. Steady-state lag settled under 30 seconds.
Post-run webhooks from dbt Cloud are not reaching the refresh endpoint. Signature validation fails because Foundry's egress proxy strips the timestamp header. Ellen is testing a header passthrough rule on their side and will confirm this week.
The first CDC pipeline went to production on July 2, a day ahead of the milestone, and 14 named users are onboarded against a target of 12. Ravi has been benchmarking end-to-end ingest lag against the in-house pipeline his team ran before and said the numbers are holding at roughly a third of what they used to see. He wants to scope streaming ingest for the event data still sitting in S3, and noted that budget for anything beyond the landed contract sits outside his team this year.
Walked the reference architecture against Foundry's stack: raw events land in S3, Postgres is the operational store, dbt handles transforms. Agreed three implementation milestones, staging workspace by June 26, first CDC pipeline in production by July 3, and 12 named users onboarded by July 31. Dmitri asked that all provisioning go through the Terraform provider so nothing is clicked in a console.