Skip to content

Commit 0888c77

Browse files
tebanieotebanieo
authored
Adding Modernizr workshop to DynamoDB Immersion Day
Approving Modernizr Workshop. Thanks for the revision @terhunej .
2 parents 4ec9c3a + 118d469 commit 0888c77

File tree

98 files changed

+2257
-0
lines changed

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

98 files changed

+2257
-0
lines changed

‎content/modernizr/00-preparation/index.en.md‎

Lines changed: 101 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,101 @@
1+
---
2+
title: "Environment Setup"
3+
date: 2025-09-01T09:53:04-05:00
4+
weight: 30
5+
chapter: true
6+
---
7+
8+
## Development Environment Setup
9+
10+
Before beginning the modernization process, you need to configure your development environment. You'll be working with Visual Studio Code Web running on a pre-configured EC2 instance that includes all necessary AWS permissions and tooling for this workshop. This cloud-based development environment provides immediate access to AWS services and the specialized MCP servers required for the modernization workflow, eliminating the need for local environment configuration.
11+
12+
## Step 1: Accessing Your Development Environment
13+
14+
Navigate to the workshop studio page and access the "Outputs" tab to retrieve your environment credentials:
15+
16+
![Workshop studio tab](/static/images/modernizr/0/setup-01.png)
17+
18+
Locate these two important values:
19+
- **VSCodeServerPassword** - Authentication credential for your VS Code instance
20+
- **VSCodeServerURLModernizr** - Direct endpoint to your cloud-based IDE
21+
22+
Your values are unique to you and will differ from the above example.
23+
24+
Click the `VSCodeServerURLModernizr` to launch your development environment. Enter the password when prompted and allow approximately 60 seconds for the environment to initialize. Any startup notifications can be safely dismissed.
25+
26+
## Step 2: Configuring the Cline AI Agent
27+
28+
Your workspace includes **Cline**, an autonomous AI coding agent that will assist with the modernization process. Cline provides intelligent code analysis, generation, and refactoring capabilities throughout this workshop.
29+
30+
Access the [Cline](https://cline.bot/) extension through the VS Code interface:
31+
32+
![Cline plugin](/static/images/modernizr/0/setup-02.png)
33+
34+
## Step 3: Establishing Bedrock Integration
35+
36+
Configure Cline to use Amazon Bedrock as its foundation model provider. Select "Use your own API Key" and choose "Amazon Bedrock" from the dropdown:
37+
38+
![Cline plugin API config](/static/images/modernizr/0/setup-03.png)
39+
40+
Apply the following configuration parameters:
41+
- **Authentication**: AWS Profile
42+
- **Profile**: empty (default)
43+
- **Region**: us-west-2
44+
- **Cross region inference**: enabled
45+
46+
Confirm the settings and initialize the connection:
47+
48+
![Cline plugin config](/static/images/modernizr/0/setup-04.png)
49+
50+
51+
::alert[You are working in a lab environment, the foundational models have configured rate limiting, it is highly likely during the workshop you will get throttled and you will have to retry the operations. You have 4 request per minute using Claude 4 and 6 request per minute using Claude 3.7.]{type="info"}
52+
53+
54+
## Step 4: Validating the Integration
55+
56+
Verify the Bedrock connection is functioning correctly by sending the below test prompt to Cline. If you are throttled, press "proceed anyway" to retry the request.
57+
58+
```terminal
59+
Hello and Welcome to this modernization project, can you confirm you can read and list all the files in the workspace?
60+
```
61+
62+
![Cline plugin testing](/static/images/modernizr/0/setup-05.png)
63+
64+
This workshop provides access to two foundation models: `claude-sonnet-4` (latest generation with enhanced reasoning capabilities) and `claude-sonnet-3.7` (previous generation with proven reliability).
65+
66+
![Cline plugin response](/static/images/modernizr/0/setup-06.png) ![Cline plugin result](/static/images/modernizr/0/setup-07.png)
67+
68+
## Step 5: Configuring Auto-Approval Settings
69+
70+
Optimize Cline's efficiency by enabling automatic permissions for routine operations. Access the auto-approve settings via the `^` icon in the bottom-right corner of the Cline interface.
71+
72+
Enable the following capabilities:
73+
- **Read all files** - Full workspace file access
74+
- **Use MCP servers** - Integration with specialized AI tools
75+
- **Edit project files** - Code modification permissions
76+
77+
Increase the **Max requests** parameter from 20 to 40 to accommodate complex multi-step operations without interruption.
78+
79+
![Cline plugin auto-approve settings](/static/images/modernizr/0/setup-08.png)
80+
81+
## Step 6: Verifying MCP Server Status
82+
83+
Access the MCP server management interface (stacked server icon) to confirm all specialized AI tools are operational. You should observe 3 active servers with green status indicators, confirming proper connectivity.
84+
85+
![Cline plugin auto-approve settings](/static/images/modernizr/0/setup-09.png)
86+
87+
## Step 7: MCP Integration Verification
88+
89+
Test the MCP server functionality by querying existing DynamoDB resources:
90+
91+
```shell
92+
Please show me the DynamoDB tables that I have in this region
93+
```
94+
95+
![Task MCP Server](/static/images/modernizr/0/setup-10.png)
96+
97+
## Environment Ready
98+
99+
Your development environment is now fully configured with AI-assisted tooling. The integration of VS Code Web, Cline, Bedrock foundation models, and specialized MCP servers provides a comprehensive platform for the database modernization workflow.
100+
101+
Proceed to the next module to begin the systematic analysis of your legacy application.

‎content/modernizr/01-modernization/index.en.md‎

Lines changed: 116 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,116 @@
1+
---
2+
title: "Database Modernizr Workflow"
3+
date: 2025-09-01T10:41:04-05:00
4+
weight: 30
5+
chapter: true
6+
---
7+
8+
## Application Analysis and Baseline Establishment
9+
10+
Before beginning the modernization process, you must thoroughly understand the existing system architecture. This involves analyzing the current MySQL-based e-commerce application to identify all data access patterns, performance characteristics, and system dependencies.
11+
12+
Begin by reviewing the application documentation in the `README.md` file, which provides an overview of the system architecture and functionality.
13+
14+
::alert[You don't have to follow the `README.md` instructions as your environment is already pre-configured for you. ]{type="info"}
15+
16+
![README](/static/images/modernizr/1/workflow-01.png)
17+
18+
## Starting the Application Services
19+
20+
The e-commerce application follows a standard three-tier architecture:
21+
1. **Backend Service** - Express.js API server handling business logic and database interactions
22+
2. **Frontend Application** - React-based user interface for customer interactions
23+
3. **MySQL Database** - Relational database storing all application data
24+
25+
While your application environment is already preconfigured, you'll still need to start both the backend and frontend services to establish a baseline for analysis.
26+
27+
### Initializing the Backend Service
28+
29+
The backend API server manages all client requests and database transactions. Navigate to the `/backend` directory and open an integrated terminal (right-click > "Open in Integrated Terminal"). Grant any requested permissions when prompted.
30+
31+
![menu](/static/images/modernizr/1/workflow-02.png)
32+
33+
Build and start the backend service using these commands:
34+
35+
```shell
36+
npm run build
37+
npm run start
38+
```
39+
40+
Monitor the startup sequence output. A successful initialization will display output similar to:
41+
42+
```console
43+
👤 DatabaseFactory.createUserRepository called
44+
🔧 DynamoDBClientManager.getClient() called
45+
👤 Creating UserDualWriteWrapper
46+
🔐 AuthService repositories created
47+
🛍️ ShoppingCartService constructor called
48+
🛍️ ShoppingCartService repositories created
49+
🛍️ ShoppingCartService constructor called
50+
🛍️ ShoppingCartService repositories created
51+
Starting server with enhanced error handling...
52+
✅ Environment variables validated successfully
53+
✅ Database abstraction layer initialized with mysql configuration
54+
Registering routes...
55+
All routes registered.
56+
Server setup complete with comprehensive error handling
57+
📝 Using MySQL-only mode (Phase 1)
58+
🚀 Server is running on port 8100
59+
📊 Health check: http://localhost:8100/api/health
60+
🔧 Performance: http://localhost:8100/api/performance
61+
📈 Metrics: http://localhost:8100/api/metrics
62+
```
63+
64+
**Important:** Keep this terminal window open! If you close it, the backend service will stop working, and our application won't function properly.
65+
66+
### Launching the Frontend Application
67+
68+
Initialize the React frontend application by opening a terminal in the `/frontend` directory and executing:
69+
70+
```shell
71+
npm run serve:prod
72+
```
73+
74+
Allow several minutes for the build process to complete. Dismiss any popup notifications that may appear during startup.
75+
76+
## Application Verification and Analysis
77+
78+
With both services running, you can now interact with the complete application stack to understand its current behavior and performance characteristics.
79+
80+
### Backend Health Check
81+
82+
Verify the API server is responding correctly by accessing the health endpoint:
83+
84+
1. Copy your VS Code environment URL
85+
2. Open a new browser tab
86+
3. Navigate to `[your-url]/api/health`
87+
88+
This endpoint should return status information confirming the backend is operational:
89+
90+
![Backend](/static/images/modernizr/1/workflow-03.png)
91+
92+
Monitor your backend terminal for request logging, which demonstrates the API request flow.
93+
94+
### Frontend Application Access
95+
96+
Access the e-commerce frontend by navigating to `[your-url]/store/`:
97+
98+
![Store](/static/images/modernizr/1/workflow-04.png)
99+
100+
## System Interaction Analysis
101+
102+
Explore the application functionality to understand the data access patterns that will need to be modernized:
103+
104+
**User Registration:** Create a new user account to observe authentication workflows
105+
106+
**Admin Access:** Use the administrative account (username: `admin`, password: `0137183966133de0ace3d7e65e025d12`) to access extended functionality
107+
108+
**E-commerce Operations:** Navigate through product browsing, cart management, and checkout processes. We have two simulated payment methods, paypal and credit card, both will auto-approve any order!
109+
110+
Pay close attention to the backend terminal output as you interact with the application. Each user action generates specific database queries that represent the access patterns you'll need to replicate in your DynamoDB implementation.
111+
112+
## Baseline Understanding
113+
114+
This exploration phase establishes your baseline understanding of the current system architecture. Each user interaction demonstrates how the Express.js backend translates HTTP requests into MySQL queries, processes the results, and returns formatted responses to the React frontend.
115+
116+
This request-response cycle represents the core functionality that must be preserved during the database modernization process, ensuring zero functional regression while achieving improved performance and scalability through DynamoDB.

‎content/modernizr/01-modernization/workflow-00.en.md‎

Lines changed: 61 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,61 @@
1+
---
2+
title: "1.1 The workflow"
3+
menuTitle: "The workflow"
4+
date: 2025-09-01T10:42:04-05:00
5+
weight: 31
6+
chapter: false
7+
---
8+
9+
## Your 7-Step Journey to Database Modernization
10+
11+
Think of database modernization like renovating a house while people are still living in it. You can't just tear everything down and start over — you need a careful, step-by-step plan that keeps everything working while you upgrade piece by piece. That's exactly what our modernization workflow does!
12+
13+
Our process consists of seven carefully designed stages, each one building on the previous step. It's like following a recipe — each ingredient needs to be added at the right time and in the right order to get the perfect result.
14+
15+
![Modernization workflow](/static/images/modernizr/1/workflow-base-01.png)
16+
17+
## Stage 1: Understanding What You Have — Database Detective Work
18+
19+
The first stage is like being a detective investigating the current system. We need to understand everything about how the existing MySQL database works before we can improve it. This involves connecting to the database, examining what predicates are used in queries and what data is returned, how fast different operations run, looking at the structure of all the tables, and studying the application code to understand exactly how data flows through the system.
20+
21+
Think of it like doing a walkthrough with a designer before your remodel. They need to understand your taste and how you use your space to fully capture the requirements for the project. We use a specialized AI tool (the MySQL MCP server) to help us gather all this information systematically.
22+
23+
## Stage 2: Designing the New Blueprint — Creating Your DynamoDB Model
24+
25+
This is where the real design work happens! Using all the information we gathered in Stage 1, we create a completely new data model designed specifically for DynamoDB. This stage is highly interactive — you'll work closely with the AI to make important decisions about how to structure your data.
26+
27+
It's like working with an architect to design your dream house renovation. The AI provides technical expertise and suggestions, but you need to guide the process and make the final decisions about what works best for your specific needs. This collaboration ensures the new design fits your application's requirements.
28+
29+
## Stage 3: Building the Bridge — Creating a Database Abstraction Layer
30+
31+
Now we create a special "bridge" layer in your application code that can talk to both the old MySQL database and the new DynamoDB system at the same time. This follows AWS best practices and ensures you can switch between systems safely without breaking anything.
32+
33+
Think of this like rennovating the guest room before you rennovate the primary bedroom — you'll always have somewhere to sleep. Similarly with a database abstraction layer. everything continues to work normally while you prepare for the upgrade.
34+
35+
## Stage 4: Testing the Connection — Validating DynamoDB Integration
36+
37+
In this stage, we set up a local version of DynamoDB and test our bridge layer to make sure everything works correctly. It's like the city inspector making sure your renovated house systems are up to code before you complete the project.
38+
39+
We validate that all the connections work properly and that data flows correctly through both systems. This gives us confidence that everything is ready for the next phase.
40+
41+
## Stage 5: Running Both Systems — Application Refactoring and Dual Writes
42+
43+
This is the most complex stage, where your application learns to write data to both databases simultaneously. We use a method called "test-driven development," which means we write tests first to ensure everything works correctly, then modify the code to pass those tests.
44+
45+
During this stage, we also create a special admin control panel that lets you monitor and control the modernization process. You can watch both the old and new systems running side by side and manage the transition safely.
46+
47+
## Stage 6: Moving to the Cloud — Deploying the cloud Infrastructure
48+
49+
Once everything is tested and working locally, we deploy your new DynamoDB tables to the actual AWS cloud environment. You've finally got your Certificate of Occupancy!
50+
51+
The deployment process ensures your cloud infrastructure is set up correctly and ready to handle real traffic.
52+
53+
## Stage 7: The Great Migration — Moving Your Data
54+
55+
The final stage is where we actually move all your existing data from MySQL to DynamoDB. This is carefully controlled and monitored — you decide when you're ready to start using dual writes, and then we gradually migrate all your historical data.
56+
57+
We use specialized data processing tools (like the AWS Glue MCP Server) to handle this migration safely and efficiently. It's like having professional movers who ensure all your belongings get to the new house safely and end up in exactly the right places.
58+
59+
## Why This Approach Works
60+
61+
This seven-stage approach ensures that at no point during the modernization process is your application broken or unavailable. Users continue shopping, orders continue processing, and everything works smoothly while we upgrade the foundation underneath. It's a proven method that minimizes risk while maximizing the benefits of modern database technology.

‎content/modernizr/01-modernization/workflow-01.en.md‎

Lines changed: 35 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,35 @@
1+
---
2+
title: "1.2 The Anatomy of a prompt"
3+
menuTitle: "Anatomy of a prompt"
4+
date: 2025-09-01T10:43:04-05:00
5+
weight: 32
6+
chapter: false
7+
---
8+
9+
## 📚 Prompt Engineering Architecture
10+
11+
The `/prompts` directory implements a structured approach to AI-driven development through organized subfolders that correspond to each stage of the modernization workflow. Each subfolder contains three components: Requirements, Design, and Tasks documents. This architectural pattern creates a comprehensive framework that systematically guides the entire modernization process from initial analysis through final implementation.
12+
13+
![Prompts](/static/images/modernizr/1/workflow-prompt-01.png)
14+
15+
### Requirements Documentation — Defining Objectives and Success Criteria
16+
17+
The Requirements Document establishes the foundational context by articulating the business objectives and technical constraints that drive the modernization initiative. This document defines explicit acceptance criteria and success metrics, creating what software engineers refer to as the "definition of done." By providing comprehensive context about the problem domain, the requirements document enables the LLM to understand not just what needs to be built, but why it needs to be built and how to validate that the implementation meets the specified goals.
18+
19+
### Design Documentation — Technical Architecture and Implementation Strategy
20+
21+
The Design Document serves as the technical specification that translates high-level requirements into concrete architectural decisions and implementation strategies. This document defines the specific methodologies, data structures, and system workflows that will be employed throughout the modernization process. It includes detailed implementation guidelines, architectural patterns, and design rationale that provide the LLM with a comprehensive technical blueprint for executing the modernization according to established software engineering principles.
22+
23+
### Task Documentation — Executable Implementation Steps
24+
25+
The Tasks Document functions as the bridge between abstract architectural design and concrete implementation by decomposing design specifications into discrete, executable development tasks. This document provides sequenced instructions that reference specific files, tools, and expected deliverables, ensuring the LLM receives actionable directives rather than abstract concepts. The task breakdown transforms architectural decisions into manageable development units that can be systematically executed and validated.
26+
27+
### The Importance of Structured Prompt Engineering
28+
29+
This three-tier documentation approach addresses a fundamental challenge in AI-assisted development: the complexity management problem. When an LLM encounters a sophisticated design document without accompanying task structure, it faces the same challenges that human developers experience when given high-level specifications without clear implementation guidance. The system may attempt to implement multiple components simultaneously, leading to incomplete or inconsistent results, or it may struggle to determine the appropriate sequencing of development activities.
30+
31+
The structured approach provides several advantages. The LLM receives explicit guidance on which specialized tools and MCP servers to utilize for each development phase. Dependencies between implementation tasks become clearly defined, preventing issues that arise from incorrect execution ordering. The system understands exactly what deliverables should be produced at each stage, enabling proper validation and quality assurance throughout the process.
32+
33+
To conceptualize this framework using a navigation analogy: the Requirements document defines the destination and the reasons for traveling there, the Design document provides the comprehensive route map showing all available paths and optimal strategies, and the Tasks document functions as turn-by-turn GPS navigation that guides execution through each specific step of the journey. This structured approach transforms complex modernization challenges into systematic, manageable processes that can be executed reliably through AI-assisted development workflows.
34+
35+
![Tasks](/static/images/modernizr/1/workflow-prompt-02.png)

0 commit comments

Comments
 (0)