Skip to content

feat(workshops/platform-microservice-decomposition): add platform story coverage + delivery variants #113

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
devin-ai-integration wants to merge 1 commit into
base: devin/1780546598-platform-story-coverage
Choose a base branch
from
Open

feat(workshops/platform-microservice-decomposition): add platform story coverage + delivery variants #113

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
15 changes: 15 additions & 0 deletions workshops/platform-microservice-decomposition/README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,5 +1,7 @@
# Workshop: Platform-Conformant Microservice Decomposition

**Other variants:** [Desktop + Cloud](README.platform.md)

## Overview

| | |
Expand All @@ -9,6 +11,12 @@
| **Audience** | DevOps, platform engineering, solution architects |
| **Key Modules** | [Platform-Conformant Microservice Decomposition](../../modules/cloud-infrastructure/platform-conformant-microservice-decomposition.md) |

## Platform Context

This workshop uses **Devin Cloud** via the Devin web app ([app.devin.ai](https://app.devin.ai)). You will create sessions in the browser, paste prompts, and review the PRs Devin opens — all interaction happens through the web interface.

> **Tip:** Prefer a local-first workflow? This same workshop can be run from **Devin Desktop** (IDE + Agent Command Center) where you delegate tasks to Cloud and review PRs without leaving the editor. See the [Desktop + Cloud variant](README.platform.md) for that delivery. You can also use **Devin CLI** in your terminal for the exploration phases.

## Workshop Narrative

Decomposing a monolith is not just about extracting code — the new service must be deployable, observable, and conformant with organizational platform standards. This workshop has Devin read four repositories simultaneously to decompose a bounded context while generating all the IaC artifacts.
Expand All @@ -25,6 +33,7 @@ A few tips to maximize your hands-on time:
- **Use Ask Devin to refine requirements.** The better-defined a task is, the better Devin's output. Ask Devin helps you think through the problem before Devin executes.
- **Build up Devin's knowledge as you go.** When Devin suggests a Knowledge item, accept it — this is how teams build a shared context layer that compounds over time.
- **Leave PR comments to steer Devin.** After Devin opens a PR, you can leave comments and Devin will wake up and address them — this is the core feedback loop.
- **Track parallel sessions from the Agent Command Center.** If you're using Devin Desktop, the Kanban board gives you a single view of sessions across status (working, waiting for review, completed). This is especially useful during Phase 4 if you launch multiple decomposition sessions.

## Table of Contents

Expand Down Expand Up @@ -104,6 +113,8 @@ Build and test both services locally to verify they work together.

**What to expect:** Devin will read all four repos, analyze the domain boundaries, create a task plan, and begin extracting the Inventory module. This typically takes 10–15 minutes to produce initial PRs.

> **Desktop tip:** Use the Agent Command Center in Devin Desktop to monitor this session alongside any other running sessions on a single Kanban board.

### Phase 2 — Explore While Devin Works (25 min)

While Devin is working autonomously, use these features to deepen your understanding:
Expand All @@ -122,6 +133,8 @@ Open each repo's DeepWiki page to understand the architecture:
2. **platform-engineering-shared-services** — Understand the namespace provisioning pattern, network policy defaults, and monitoring setup. This defines what the new service must conform to.
3. **ordermanager-iac** — Understand the Helm chart structure, Dockerfile build stages, ArgoCD application configuration, and CI/CD pipeline. The new service's IaC should mirror these patterns.

> **CLI alternative:** The AskDevin exploration steps above can also be done locally with `devin` in your terminal for faster iteration — ask the same questions and get answers grounded in your local file system.

#### Monitor Devin's Progress

Watch the session as Devin works. Key milestones to look for:
Expand All @@ -135,6 +148,8 @@ Watch the session as Devin works. Key milestones to look for:

Once Devin creates PRs, review them on GitHub:

> **Desktop tip:** The PRs Devin opens in this lab can be reviewed directly in Devin Desktop with one-click checkout — no manual `git fetch` required.

#### Review the Monolith PR

- Does the HTTP client correctly replace all in-process Inventory calls?
Expand Down
Loading