Our legacy backend service is written in Python, but is currently being rewritten in TypeScript to improve maintainability, enable better code reuse, and take advantage of static typing and modern development practices.
To ensure consistent schema migrations across both the new backend and legacy backend projects—and to preserve backward compatibility—we will not use the built-in migration tools provided by individual ORMs. Instead, all schema changes will be defined and applied through a shared migrations project. This centralized approach serves as the single source of truth and guarantees alignment between systems.
