Run a full database modernization assessment with Claude Code¶
Give this tool the schema and queries of a monolithic relational database. It tells you which queries belong on which AWS purpose-built engine and designs the target schemas.
Run this command in Claude Code with the repository open. The chat reports each phase, and by default a local UI opens next to it with the assignment Sankey diagram, the schema designs and the full report as each one is ready.
Get started with Claude Code See a sample report
Demo¶
A full /modernize run on the WordPress sample (47 minutes, time-lapsed), then the local UI: the executive summary, the query flow, the cost per engine and the access pattern explorer.
What it answers¶
- Which queries go where. Every query pattern is scored against each candidate engine. The assignment is deterministic: the scores decide it, not a model.
- What the target schemas look like. DynamoDB tables, DocumentDB collections, OpenSearch mappings and the relational schema that stays, all designed from your workload.
- What it costs and what the risks are. The same run produces TCO projections and a risk analysis. Migration waves show a suggested step-by-step path next to the fully decomposed target.
See Understand the results for how to read every deliverable.
Moving off a monolithic relational database raises hard questions. Which queries belong in DynamoDB? Which need a document store? What stays relational? A wrong answer can force a redesign in the middle of the project.
Database Modernizer Assessment answers these questions using your real workload. Give it the collected schema and queries of a PostgreSQL or MySQL database. It analyzes every query pattern, scores each one against 6 AWS purpose-built engines, checks the resulting architecture, and produces schema designs and TCO projections you can implement.
Supported sources: PostgreSQL, MySQL, MariaDB Target engines: DynamoDB, DocumentDB, Aurora PostgreSQL, Aurora MySQL as query owners, plus ElastiCache as a cache layer and OpenSearch as a search read model
Note: This project originally shipped with a hosted deployment option. Following customer feedback, it became a local tool built around Claude Code, to keep the open-source release simple to adopt.
Who is this for?¶
This tool is for teams that have decided to refactor their application to use purpose-built databases. It helps you figure out which queries go where and what the target schemas should look like.
Who is this NOT for?¶
- Lift-and-shift migrations: If you're moving a database as-is to RDS or Aurora without changing the data model, you don't need this tool.
- Tight deadline migrations: This tool guides application refactoring, which takes time. If you need to migrate by next week, use AWS DMS for a straight move.
- Teams that haven't committed to refactoring: If you're still deciding whether to modernize, start with the AWS Migration Evaluator or a Well-Architected review first.
Sample project
This is a sample project intended for educational and evaluation purposes. It requires proper review, testing, and modification before use in production environments. Use at your own risk.