Skip to content

[chore]: Autogenerated ORM code from DB schema #218

Closed

Description

@SuvabrataChowdhury

Chore Description

Currently the service defines it's db schema through specific ORMs (e.g., spring-data-jpa for pipeline service). This will get complicated with multiple services as we would need to write it's own specific ORM. Therefore, there won't be any single source of truth!

The solution is to introduce a db migration tool (agnostic of specific ORMs like liquibase or flyway) and generate the ORM code from the unified schema definition.

Benefit hypothesis

All services will be reading from unified schema. This will vastly reduce efforts maintaining db schema and synchronizing it across services.

Chore importance

Medium

Additional comments

No response

Metadata

Metadata

Assignees

No one assigned

    Labels

    choreSome tasks, other than core application development, which helps the application's development.

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions