Migrate a 600K-LOC Monolith to a Modular Monolith

FreeVerified credential4 weeksExpert

Overview

What this challenge is about.

Migrate a 600K-LOC Monolith to a Modular Monolith. Expert-level challenge in design. Designing real products under real constraints, earn a blockchain-verifi...

CredentialBlockchain-anchored

ShareableLinkedIn-ready

LanguageEnglish

PaceSelf-paced

The Brief

What you'll do, and what you'll demonstrate.

Design module boundaries from dependency analysis, ship a 2-module Packwerk pilot, and plan a 12-month modular-monolith migration for a 600K-LOC Rails codebase.

This is not a design exercise. It is the work a product designer does between a brief and a shipped interface. That distinction matters to every hiring manager who has seen candidates redesign Spotify's homepage and none who have worked under real product constraints.

When you finish, you will have something most graduates do not: a real-world deliverable, verified by Ewance, that you can show to a hiring manager and say "I did this. Here is the proof."

Earning criteria — what you'll demonstrate

Surface implicit module boundaries from static dependency analysis
Design explicit module APIs in a Packwerk-style modular monolith
Plan a multi-year migration with leading + lagging KPIs
Sequence pilot vs full-migration work to maintain delivery throughput

Program Fit

Where this fits in your program.

Sharpens the same skills your degree expects you to demonstrate.

Advanced Software Engineering

Master · Software Engineering

Strong alignment

This challenge maps to Advanced Software Engineering at the Master level. It sharpens the same practical skills your coursework expects — but in a real industry context with actual constraints and deliverables.

Skills

Skills you'll demonstrate.

Each one shows up on your verified credential.

Careers

Career paths this challenge builds toward

Completing this challenge demonstrates skills that transfer directly to these roles:

Career paths this builds toward

Canonical roles

Systems Architect
Systems architects make the decisions whose consequences are felt for years. The role is about choosing: which cloud provider, which integration pattern, which trade-off between cost and reliability deserves an Architecture Decision Record so the next team understands the reasoning. You'll work in C4 diagrams, ArchiMate models, and the AWS or Azure Well-Architected Framework, but the real artifact is clarity of thought. Strong architects know when to standardize and when to let a team diverge, and they write documents that survive a leadership change. Students drawn here usually loved their distributed systems course and are patient enough to think before they build. Growth happens through scars: owning architectures end-to-end, watching them strain under real load, and learning which abstractions earned their place.
Platform & Infrastructure

One more thing

You can put a credential on your CV by Friday.

Start this challenge