Merge pull request #182 from tebanieo/master

feat: including docker compose for DDB local and stages 3 and 4

Author: tebanieo

workshops/modernizr/docker/docker-compose.yml

@@ -0,0 +1,11 @@
+
+services:
+ dynamodb-local:
+   command: "-jar DynamoDBLocal.jar -sharedDb -dbPath ./data"
+   image: "amazon/dynamodb-local:latest"
+   container_name: dynamodb-local
+   ports:
+     - "8000:8000"
+   volumes:
+     - "./docker/dynamodb:/home/dynamodblocal/data"
+   working_dir: /home/dynamodblocal

workshops/modernizr/prompts/00-mysql-dynamodb-migration-orchestrator/design.md

@@ -41,12 +41,12 @@ Each stage is implemented as a complete spec with:
 **Output**: `Stage3_DataModel.md`, `migrationContract.json`
 **Key Methodology**: Two-file system, RPS documentation, denormalization framework
 
-### Stage 3: DAL Abstraction
-**Spec**: `03-dal-abstraction`
-**Purpose**: Create abstraction layer for multiple database implementations
+### Stage 3: Dual-Database Abstraction
+**Spec**: `03-dual-database-abstraction`
+**Purpose**: Create dual-database abstraction layer with feature flag control for simultaneous MySQL and DynamoDB operations
 **Input**: Application codebase
-**Output**: Refactored codebase with DAL abstraction
-**Key Methodology**: 9-step process with factory pattern implementation
+**Output**: Refactored backend codebase with dual-database abstraction and global feature flags
+**Key Methodology**: Discovery-driven approach with dual-database repository pattern and feature flag implementation
 
 ### Stage 4: DynamoDB Implementation
 **Spec**: `04-dynamodb-implementation`
@@ -83,7 +83,7 @@ Each stage is implemented as a complete spec with:
 1. **Stage-01 Modular Artifacts**: Complete database analysis in focused artifacts (`artifacts/stage-01/01_1_API_access_patterns.md`, `01_2_schema_extraction.md`, `01_3_entity_relationships.md`, `01_4_table_structures.md`, `01_5_performance_analysis.md`, `01_6_access_patterns.md`)
 2. **Stage-02 Modular Artifacts**: dynamodb_data_model.md and dynamodb_requirement.md
 3. **migrationContract.json**: MySQL-to-DynamoDB mapping (CRITICAL FORMAT)
-4. **Refactored Codebase**: Application with DAL abstraction
+4. **Refactored Backend**: Backend with dual-database abstraction and feature flags
 5. **Feature Flag System**: Web interface for migration control
 6. **CloudFormation Templates**: Infrastructure deployment
 7. **Migration Reports**: Validation and completion documentation

workshops/modernizr/prompts/00-mysql-dynamodb-migration-orchestrator/tasks.md

@@ -1,54 +1,54 @@
 # MySQL to DynamoDB Migration Orchestrator - Tasks
 
 - [ ] 1. Execute MySQL Analysis Stage
-  - Navigate to `.kiro/specs/01-mysql-analysis/` spec
+  - Navigate to `prompts/01-mysql-analysis/` spec
   - Execute the complete 01-mysql-analysis spec (requirements → design → tasks)
   - Validate output: Modular artifacts exist in `artifacts/stage-01/` and contain complete schema analysis
   - Confirm all MySQL schema, relationships, and access patterns are documented
   - _Requirements: 1.1, 1.2_
 
 - [ ] 2. Execute DynamoDB Data Modeling Stage
-  - Navigate to `.kiro/specs/02-dynamodb-data-modeling/` spec
+  - Navigate to `prompts/02-dynamodb-data-modeling/` spec
   - Provide stage-01 modular artifacts (`artifacts/stage-01/`) as input to the data modeling process
   - Execute the complete 02-dynamodb-data-modeling spec
   - Validate outputs: `dynamodb_data_model.md`, `dynamodb_requirement.md` and `migrationContract.json` exist
   - **CRITICAL**: Verify `migrationContract.json` follows exact format specified in data modeling spec
   - _Requirements: 1.3, 2.1, 2.2_
 
-- [ ] 3. Execute DAL Abstraction Stage
-  - Navigate to `.kiro/specs/03-dal-abstraction/` spec
-  - Provide application codebase path as input
-  - Execute the complete 03-dal-abstraction spec (9-step process)
-  - Validate output: Codebase has abstraction layer with factory pattern
-  - Confirm all existing tests still pass with abstraction layer
+- [ ] 3. Execute Dual-Database Abstraction Stage
+  - Navigate to `prompts/03-dual-database-abstraction/` spec
+  - Provide backend codebase path as input (backend/ folder only)
+  - Execute the complete 03-dual-database-abstraction spec (discovery-driven process)
+  - Validate output: Backend has dual-database abstraction layer with global feature flags
+  - Confirm all existing backend tests still pass with dual-database abstraction layer
   - _Requirements: 1.4, 2.3_
 
 - [ ] 4. Execute DynamoDB Implementation Stage
-  - Navigate to `.kiro/specs/04-dynamodb-implementation/` spec
+  - Navigate to `prompts/04-dynamodb-implementation/` spec
   - Provide `Stage3_DataModel.md` and abstracted codebase as inputs
   - Execute the complete 04-dynamodb-implementation spec
   - Validate output: Complete DynamoDB implementation with passing tests
   - Confirm implementation follows data model specifications exactly
   - _Requirements: 1.5, 2.4_
 
 - [ ] 5. Execute Feature Flags System Stage
-  - Navigate to `.kiro/specs/05-feature-flags-system/` spec
+  - Navigate to `prompts/05-feature-flags-system/` spec
   - Provide completed DAL implementations as input
   - Execute the complete 05-feature-flags-system spec
   - Validate output: Web interface for controlling 5 migration phases
   - Test all migration scenarios: MySQL-only → dual-write → dual-read → DynamoDB-only
   - _Requirements: 2.1, 2.2, 2.3, 2.4, 2.5_
 
 - [ ] 6. Execute Infrastructure Deployment Stage
-  - Navigate to `.kiro/specs/06-infrastructure-deployment/` spec
+  - Navigate to `prompts/06-infrastructure-deployment/` spec
   - Provide `migrationContract.json` as input
   - Execute the complete 06-infrastructure-deployment spec
   - Validate output: DynamoDB tables deployed with proper configuration
   - Confirm all tables, GSIs, and monitoring are properly configured
   - _Requirements: 3.1, 3.2_
 
 - [ ] 7. Execute Data Migration Stage
-  - Navigate to `.kiro/specs/07-data-migration-execution/` spec
+  - Navigate to `prompts/07-data-migration-execution/` spec
   - Provide deployed infrastructure and migration contract as inputs
   - Execute the complete 07-data-migration-execution spec
   - Validate output: Data successfully migrated with validation reports