diff --git a/content/labs/workflow-stepper/Demo.tsx b/content/labs/workflow-stepper/Demo.tsx index 16fbcf8..60af040 100644 --- a/content/labs/workflow-stepper/Demo.tsx +++ b/content/labs/workflow-stepper/Demo.tsx @@ -2,54 +2,133 @@ import { useState } from "react"; -const STEPS = [ - { task: "Validate order", event: "order.received", system: "API" }, - { task: "Reserve resources", event: "inventory.reserved", system: "Inventory" }, - { task: "Provision service", event: "service.provisioned", system: "Network" }, - { task: "Activate & bill", event: "service.activated", system: "Billing" }, +type Actor = "person" | "system" | "engine" | "downstream"; + +type Step = { + task: string; + actor: Actor; + /** What completes the step, as the button reads while it is current. */ + action: string; + events: string[]; +}; + +/** A generic order, end to end: the shape of the flow, none of a client's names. */ +const STEPS: Step[] = [ + { task: "Quote submitted", actor: "person", action: "Submit quote", events: ["quote.submitted"] }, + { + task: "Decomposed into product orders", + actor: "system", + action: "Decompose", + events: ["product-order.created #1", "product-order.created #2"], + }, + { task: "One process per product order", actor: "engine", action: "Start process", events: ["process.started #1"] }, + { task: "Service order created", actor: "engine", action: "Create service order", events: ["service-order.created"] }, + { task: "Reserve network resources", actor: "downstream", action: "Receive callback", events: ["callback resource.reserved"] }, + { task: "Confirm technical details", actor: "person", action: "Complete task", events: ["task.completed"] }, + { task: "Activate and start billing", actor: "downstream", action: "Receive callback", events: ["callback billing.started"] }, + { task: "Product order completed", actor: "engine", action: "Complete", events: ["product-order.completed #1"] }, ]; -/** Placeholder demo: a process with its emitted events. */ +/** From this step on, the order can no longer be cancelled. */ +const MILESTONE = 6; + +const ACTOR_LABEL: Record = { + person: "people", + system: "system", + engine: "engine", + downstream: "callback", +}; + +type LogLine = { event: string; tone?: "reject" | "stop" }; + +/** One product order stepped through its process, with the events it emits + * and a cancellation that only holds before the point of no return. */ export default function WorkflowStepperDemo() { const [step, setStep] = useState(0); + const [log, setLog] = useState([]); + const [cancelled, setCancelled] = useState(false); + const done = step >= STEPS.length; + const stopped = done || cancelled; + const current = STEPS[step]; + + function advance() { + if (stopped) return; + setLog((l) => [...l, ...current.events.map((event) => ({ event }))]); + setStep((s) => s + 1); + } + + function cancel() { + if (stopped) return; + if (step < MILESTONE) { + setCancelled(true); + setLog((l) => [ + ...l, + { event: "cancel.requested" }, + { event: "product-order.cancelled #1", tone: "stop" }, + ]); + } else { + setLog((l) => [...l, { event: "cancel.rejected · past milestone", tone: "reject" }]); + } + } + + function reset() { + setStep(0); + setLog([]); + setCancelled(false); + } return (
-

process · order #4821

-
    +

    product order #1 · its process

    +
      {STEPS.map((s, i) => { - const state = i < step ? "done" : i === step ? "current" : "todo"; + const state = + i < step ? "done" : i === step && !stopped ? "current" : "todo"; return ( -
    1. - {s.task} - {s.system} +
    2. + {i === MILESTONE && ( +

      — milestone: no cancel after this —

      + )} +
      = step ? "line-through" : ""}`} + > + {s.task} + + {ACTOR_LABEL[s.actor]} + +
    3. ); })}
    -
    +
    +
    -

    events on the log

    +

    events, in order

    - {STEPS.slice(0, step).map((s, i) => ( -

    - {s.event} - t+{(i + 1) * 120}ms + {log.map((line, i) => ( +

    + {line.event} + {String(i + 1).padStart(2, "0")}

    ))} - {step === 0 &&

    nothing yet — complete a step

    } + {log.length === 0 &&

    nothing yet — submit the quote

    }
diff --git a/content/labs/workflow-stepper/lab.mdx b/content/labs/workflow-stepper/lab.mdx index af841c5..29db906 100644 --- a/content/labs/workflow-stepper/lab.mdx +++ b/content/labs/workflow-stepper/lab.mdx @@ -1,15 +1,21 @@ --- title: "Workflow stepper" -summary: "Step through an orchestrated service process and watch the events it emits." +summary: "Step one product order through its process, watch the events it emits, and try to cancel it midway." date: "2026-09-17" topic: "orchestration" preview: "process" -tags: ["camunda", "kafka", "orchestration"] +tags: ["camunda", "orchestration", "order management"] --- -A service order in the telco domain touches many systems. Modelling the -process as a first-class artifact — BPMN in an engine, events on a log — -means every step has a name, a state and a trace. The stepper shows what a -single order looks like from the process's point of view. +A submitted quote doesn't become one big transaction. It is decomposed into +product orders, and each product order runs as its own Camunda process. The +process creates the service orders that deliver the product, then waits: +downstream systems answer asynchronously through callbacks, and the steps that +need a person become user tasks. -Placeholder: the real demo will replay an anonymised process definition. +Modelling it this way means every order has a name, a state and a history, +and a question like "can this still be cancelled?" has a precise answer. Before +the milestone, a cancel request stops the process cleanly. After it, the +request is rejected, because work downstream can no longer be taken back. + +The flow is generic: the shape of a real order platform, none of its names. diff --git a/content/work/telco-service-orchestration.mdx b/content/work/telco-service-orchestration.mdx index 2c7e5da..ea4a1b5 100644 --- a/content/work/telco-service-orchestration.mdx +++ b/content/work/telco-service-orchestration.mdx @@ -5,7 +5,7 @@ sector: "Telco" role: "Lead Developer" period: "2024 — now" date: "2026-09-01" -stack: [".NET", "ASP.NET Core", "Camunda", "Kafka", "PostgreSQL", "Vue 3", "OpenShift", "Conceptwave (legacy)"] +stack: [".NET", "ASP.NET Core", ".NET Aspire", "Camunda", "Kafka", "PostgreSQL", "Vue 3", "OpenShift", "Conceptwave (legacy)"] outcomes: - { value: "2", label: "teams led, new platform and legacy", countTo: 2 } - { value: "10+", label: "engineers", countTo: 10 } @@ -32,19 +32,30 @@ integrated with the operator's downstream systems. +## What I built + +**The foundation.** I set up the platform the team builds on: the repository +and the structure of every service, the implementation templates, the shared +building blocks for logging, caching, migrations and API clients, the API +gateway, and the .NET Aspire environment the whole team develops and runs the +system in. + +**The modules on top of it.** I contribute across all of them: order +management (quote, decomposition into product orders, discounts), the order +entry UI and the task framework its screens run on, the product catalog and +the utility services. + ## Decisions **Build on reusable assets.** Catalog, ordering, workflow and integration components are shared, so each new service line builds on the same foundation -instead of starting over. I wrote much of that foundation myself: the API -gateway, the building blocks for logging, caching and API clients, the Camunda -integration and the task framework the order screens run on. +instead of starting over. **Move in phases, side by side.** Each service line is cut over on its own. Both systems run in parallel, and the new platform has to show it behaves like diff --git a/public/cv.pdf b/public/cv.pdf index c44e26e..19c8170 100644 Binary files a/public/cv.pdf and b/public/cv.pdf differ diff --git a/src/config/profile.ts b/src/config/profile.ts index 3bf636d..b1a33d9 100644 --- a/src/config/profile.ts +++ b/src/config/profile.ts @@ -49,7 +49,7 @@ export const profile = { org: "DefineX", context: "Consulting, Technology & Labs", summary: - "Leading a large, multi-year order management transformation for a telecom operator: a legacy Conceptwave-based B2B ordering stack replaced with .NET microservices, one service line at a time. I lead both teams, 10+ engineers in total, own the technical design from the Vue.js interface and API gateway to the ASP.NET Core services, Camunda workflows and Kafka integration, and build much of the foundation myself. Cut-overs ship on schedule without disrupting live order flows.", + "Leading a large, multi-year order management transformation for a telecom operator: a legacy Conceptwave-based B2B ordering stack replaced with .NET microservices, one service line at a time. I lead both teams, 10+ engineers in total, and own the technical design from the Vue.js interface and API gateway to the ASP.NET Core services, Camunda workflows and Kafka messaging. I set up the platform's foundation, from the structure of every service and the implementation templates to the shared building blocks and the .NET Aspire environment the team develops in, and contribute across all of its modules. Cut-overs ship on schedule without disrupting live order flows.", }, { from: "2021", diff --git a/src/i18n/messages/en.json b/src/i18n/messages/en.json index fee88bd..7a32028 100644 --- a/src/i18n/messages/en.json +++ b/src/i18n/messages/en.json @@ -49,7 +49,7 @@ }, { "title": "Workflow orchestration", - "desc": "Camunda, Kafka and phased cut-overs for order processes that carry real load.", + "desc": "A Camunda process per order, asynchronous callbacks from downstream systems, and phased cut-overs for order flows that carry real load.", "href": "/labs/workflow-stepper", "proof": "workflow stepper" },