[Contoso Redesign] Migrate COBOL AS400 holiday and logging apps to a Java microservices architecture. #5
Description
Description
Complete gap - the requirement assumes existence of COBOL AS400 legacy systems (holiday management app, logging apps) that do not exist in this repository. This is a modern corporate website project, not a legacy mainframe migration project. To fulfill this requirement would require: (1) Access to the actual COBOL AS400 source code from an external legacy system, (2) Creating entirely new Java microservices from scratch, (3) Complete greenfield development rather than migration.
Current State
This repository (corporate-website) is a modern web application showcase with NO COBOL or AS400 code. The tech stack is: Frontend (Vanilla HTML/CSS/JavaScript with Vite), Backend (Python with FastAPI in server/contact_handler.py and backend/api/users.py), TypeScript API layer (src/api/contact.ts). No .cbl, .cobol, .java files exist. The 'logging' in this repo refers to modern audit logging for GDPR compliance (Python logging module, console.error in TypeScript) - NOT legacy AS400 logging apps. No 'holiday' application exists in any form.
Acceptance Criteria
- The gap described above is fully addressed
Technical Details
This requirement cannot be implemented against this repository because: 1) No COBOL source files exist (.cbl, .cobol patterns return no matches), 2) No AS400-related code or configuration exists, 3) No 'holiday' application exists, 4) No Java infrastructure exists (no .java files, no pom.xml, no build.gradle), 5) The 'logging' in this repo is modern Python/TypeScript audit logging, not legacy AS400 logging apps. If the intent is to build Java microservices for holiday management and logging from scratch (not migration), that would require: Spring Boot/Quarkus setup, holiday service (CRUD, calendar integration), logging service (centralized logging, ELK stack), API gateway, service discovery, containerization (Docker/K8s), and complete departure from current tech stack.
Estimated Effort
6-12 months (if legacy code exists elsewhere); N/A if no legacy systems exist | Complexity: Critical
Part of #4