Prototype: Compose live application canvas#1541
Draft
sorenbs wants to merge 1 commit into
Draft
Conversation
A mockup of the Compose framework's application map: every module (standalone unit or bundled into the single Bun app), every external service (Postgres, Redis, S3 object storage, Stripe, email), the dependencies between them, live traffic, and health — on the same ELK-layered ReactFlow canvas language as the Migrations view (floating translucent header, card nodes, persistent canvas instance). All data is simulated: a fixture app (acme-shop, 7 modules + 6 services) plus a pure, seeded traffic simulator that drifts each boundary's rps/p95/error rate per tick, with occasional error spikes on the Stripe boundary. Edge width tracks rps, edge color shifts green → amber → red with error rate, node borders and health dots derive from the traffic crossing their boundaries, and clicking a node opens a 'recent boundary traces' panel of OTel-span-shaped rows — selling the auto-instrumented-boundary story. A Live/Paused toggle freezes the simulation; the header carries module/service counts, inbound rps, weighted error rate, and a 'simulated data' disclaimer. Prototype only: no FEATURES.md entry, no changeset — nothing here is released behavior. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
|
Important Review skippedDraft detected. Please check the settings in the CodeRabbit UI or the ⚙️ Run configurationConfiguration used: Organization UI Review profile: ASSERTIVE Plan: Pro Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
✨ Finishing Touches🧪 Generate unit tests (beta)
✨ Simplify code
Comment |
Contributor
|
Compute preview deployed. Branch: |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Prototype / mockup — not for merging as-is. A live canvas view of a complete Compose application, for design review.
Compose composes an application from modules (independently deployable units or bundled into a single Bun app) and tracks all dependencies — module↔module plus external services (databases, object storage, third-party APIs). Module boundaries are auto-instrumented, so cross-boundary requests are OTel traces.
This mockup renders that as a live map, in the Migrations-canvas visual language (ELK layered layout, floating translucent header, card nodes, persistent canvas):
acme-shop: 7 modules (3 standalone units, 4 bundled into Bun appcore, each badged) + 6 external services with type icons (2× Prisma Postgres, Redis, S3 bucket, Stripe, Resend).HTTP → stripe · 230ms) — the auto-instrumentation story.simulated datadisclaimer; light + dark.All data is simulated (pure, seeded, tested — 13 unit tests); there is no Compose backend. No FEATURES.md entry or changeset, deliberately.
Try it in the preview: open Compose in the left nav.
🤖 Generated with Claude Code