AWS B2B Data Interchange
Managed transformation of X12 EDI documents to and from JSON or XML through S3-based inbound and outbound transformers.
| property | type | values | required | kind default | this component |
|---|---|---|---|---|---|
| accelerator | enum | none | gpu | asic | no | none | ▸ none |
| concurrency | integer | — | no | — | inherited |
| dataFormat | enum | json | xml | no | json | inherited |
| direction | enum | inbound | outbound | no | inbound | inherited |
| ediStandard | enum | x12 | no | x12 | inherited |
| fanoutStrategy | enum | none | push | pull | hybrid | no | none | inherited |
| fanoutThreshold | integer | — | no | — | inherited |
| idempotent | boolean | — | no | false | ▸ false |
| instances | integer | — | no | — | inherited |
| managed | boolean | — | no | false | ▸ true |
| mappingLanguage | enum | none | jsonata | xslt | no | none | inherited |
| rateControl | enum | none | fixed | aimd | no | none | ▸ none |
| schedule | string | — | no | — | inherited |
| trigger | enum | queue | stream | schedule | batch | manual | yes | — | ▸ batch |
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: "b2b-data-interchange", component: "aws-b2b-data-interchange" }# yaml-language-server: $schema=../../schema/component.schema.json # AWS B2B Data Interchange: managed, pay-as-you-go transformation of X12 EDI documents to and from # JSON or XML, reading and writing Amazon S3 buckets. "Transforming and generating EDI" describes # inbound and outbound directions and optional JSONata or XSLT mappings over the service-defined # document structure. schemaVersion: "1" type: "component" id: "aws-b2b-data-interchange" kind: "worker" provider: "aws" docs: "https://docs.aws.amazon.com/b2bi/latest/userguide/what-is-b2bi.html" defaults: managed: true trigger: "batch" idempotent: false rateControl: "none" accelerator: "none" properties: direction: type: "enum" values: ["inbound", "outbound"] default: "inbound" ediStandard: type: "enum" values: ["x12"] default: "x12" dataFormat: type: "enum" values: ["json", "xml"] default: "json" mappingLanguage: type: "enum" values: ["none", "jsonata", "xslt"] default: "none"