-
Notifications
You must be signed in to change notification settings - Fork 9
Open
Description
Title:
Migrate API from standalone Python app into Next.js app
User Story Statement:
As a developer, I want the existing API recreated inside the Next.js app so that we have a unified full-stack solution and can retire the standalone Python app.
Description:
The current API is implemented as a separate Python service. To simplify maintenance, deployment, and scaling, we need to move this API logic into the Next.js application. This will consolidate the stack, reduce overhead, and make the app easier to manage.
Acceptance Criteria (Given/When/Then):
- Given a request to an API route in Next.js, when the corresponding endpoint logic is triggered, then the response should match the existing Python API output.
- Given existing consumers of the API, when they switch to the new endpoints, then no functionality should break.
- Given the old Python service, when the migration is complete, then it can be fully deprecated.
Technical Notes:
- Identify all existing API endpoints in the Python app.
- Recreate endpoints under /api routes in Next.js using Node.js/TypeScript.
- Ensure data models, response structures, and error handling remain consistent.
- Add logging and monitoring in Next.js to replace existing Python logging.
- Update CI/CD pipeline to test and deploy Next.js API.
Dependencies:
- Database connection/configuration already set up in Next.js.
- Access to the Python codebase for reference.
- Coordination with frontend team to update any API calls if endpoints change.
Definition of Done (DoD):
- All existing API endpoints recreated and tested in Next.js.
- Unit and integration tests added for each endpoint.
- API documentation updated to reflect new implementation.
- Python API app retired and removed from deployment pipeline.
- Deployed and validated in staging before production rollout.
Metadata
Metadata
Assignees
Labels
No labels
Type
Projects
Status
In review