Skip to content

Integration & messaging replatforming

Why use CCE

Event bus and integration replatforming (Kafka → SQS, dual-write cutovers, HTTP → mesh) needs an inventory of every messaging and HTTP client call site. Architecture diagrams drift; code does not.

CCE surfaces Kafka, SQS, RabbitMQ, and HTTP client usage for bounded-context planning and cutover sequencing.

What CCE extracts

JSON field Meaning for this use case
provider Integration class (MESSAGING, HTTP)
resource Technology (sqs, kafka, axios, …)
operation API invoked (produce, consume, get, post, …)
file / line Module or service boundary hint

CLI wiring

cce -repo acme/event-platform -ref main \
    -language AUTO \
    -mapper-file https://releases.stackgen.com/cce/lenses/integration-replatforming/latest/integration-replatforming_lenses.yaml \
    -filter cloud \
    -format json \
    -output integration-map.json

Local checkout:

cce -folder ./event-platform \
    -language AUTO \
    -mapper-file https://releases.stackgen.com/cce/lenses/integration-replatforming/latest/integration-replatforming_lenses.yaml \
    -filter cloud \
    -format json \
    -output integration-map.json

How to read the JSON output

  • Group entitlements[] by file path prefix to infer service/module ownership.
  • provider == "MESSAGING" — queue/topic clients; prioritize for event bus migration.
  • provider == "HTTP" — synchronous coupling; candidates for async or mesh replacement.
  • Clone + scan in one command when you do not have the repo checked out (-repo / -ref).

CI/CD snippet

- name: Integration inventory
  env:
    GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
  run: |
    cce -repo acme/event-platform -ref main \
        -mapper-file https://releases.stackgen.com/cce/lenses/integration-replatforming/latest/integration-replatforming_lenses.yaml \
        -filter cloud -format json -output integration-map.json

Published lens

Latest mapper YAML is published on every push to main (public, no auth):

curl -fsSL "https://releases.stackgen.com/cce/lenses/integration-replatforming/latest/integration-replatforming_lenses.yaml" -o integration-replatforming_lenses.yaml
cce -folder . -mapper-file https://releases.stackgen.com/cce/lenses/integration-replatforming/latest/integration-replatforming_lenses.yaml -language AUTO -filter all -format json -output report.json

Known limitations

Proof status: Verified — see KNOWN_LIMITATIONS.md (integration-replatforming) and docs/proof.

Limitation Impact
Starter messaging rules Extend Kafka/SQS/Rabbit/Azure rules for your platform.
Configuration Topic/queue names in config files are not extracted.

Platform limits (CGO, languages, static analysis, mapper precedence, filters): KNOWN_LIMITATIONS.md.