Stitch
Hosted ELT service that replicates source tables into a warehouse on a schedule using log-based, key-based or full-table replication.
- Provider
- default
- Kind
- Worker
- Category
- Compute
- Official docs
- https://www.stitchdata.com/docs/
| property | type | values | required | kind default | this component |
|---|---|---|---|---|---|
| accelerator | enum | none | gpu | asic | no | none | inherited |
| concurrency | integer | — | no | — | inherited |
| fanoutStrategy | enum | none | push | pull | hybrid | no | none | inherited |
| fanoutThreshold | integer | — | no | — | inherited |
| idempotent | boolean | — | no | false | inherited |
| instances | integer | — | no | — | inherited |
| managed | boolean | — | no | false | ▸ true |
| rateControl | enum | none | fixed | aimd | no | none | inherited |
| replicationMethod | enum | log-based-incremental | key-based-incremental | full-table | no | — | inherited |
| schedule | string | — | no | — | inherited |
| scheduling | enum | anchor | cron | no | — | inherited |
| trigger | enum | queue | stream | schedule | batch | manual | yes | — | ▸ schedule |
Every rule whose selector covers this component's kind or its category. Whether a rule fires depends on the design: its properties, its edges and its groups.
Pure push fan-out over a social graph is brutal at the tail: one post from an account with millions of followers becomes millions of cache writes. A follower threshold above which readers merge at read time bounds that write amplification.
- — all of these hold:
- — the node's `fanoutStrategy` is "push"
- — the node's `fanoutThreshold` has no value
- — the design contains a node of kind graph-database
One worker pool consuming several queues lets a slow or poisoned queue starve the others. That is precisely what the design's per-queue isolation requirement forbids.
- — all of these hold:
- — the node has more than 1 incoming edge from a queue
- — the design requirement `isolation.perQueue` is true
A stateful compute node pinned to exactly one availability zone disappears with that zone, and its state goes with it. Nodes inside a cell are exempt, because there the cell is deliberately single-zone and redundancy comes from the other cells.
- — all of these hold:
- — the node's `stateless` is false
- — the node sits inside exactly 1 availability-zone group
- — this does not hold:
- — the node sits inside at least one cell group
nodes:
- { id: "stitch", component: "stitch" }# yaml-language-server: $schema=../../schema/component.schema.json # Stitch (Qlik Talend Cloud): hosted ELT service that extracts rows from integrations and loads # them into a destination data lake or warehouse. "Stitch Documentation" documents a per # integration Replication Frequency set with Anchor Scheduling or an Advanced cron expression, so # the job is schedule-triggered, and three replication methods: log-based incremental, key-based # incremental and full table. No default frequency, concurrency or idempotency guarantee is # stated, so none is set. schemaVersion: "1" type: "component" id: "stitch" kind: "worker" provider: "default" docs: "https://www.stitchdata.com/docs/" defaults: managed: true trigger: "schedule" properties: replicationMethod: type: "enum" values: ["log-based-incremental", "key-based-incremental", "full-table"] scheduling: type: "enum" values: ["anchor", "cron"]