Rethink Nailgun Database Schema
Nailgun's database schema must be revised, because in current state it slows down engineers performance as well as Nailgun's performance due to the following reasons:
* Some important data (or even entities) are in JSON, so no way to make DB query. Instead, it forces to make joins and filtering on Python side.
* Some entities are duplicated (such as VIPs), and it requires a lot of effort to support them both in consistent state. Also, it's hard to make JOINs on them due to previous point.
* Some things are in different tables, and it forces us to make unneccesary JOINs, or spawn separate SQL queries when we access those things.
Revising our database schema will allow us to simplify contribution to Nailgun, and increase engineering performance.
Blueprint information
- Status:
- Not started
- Approver:
- Ihor Kalnytskyi
- Priority:
- Undefined
- Drafter:
- Fuel Python (Deprecated)
- Direction:
- Needs approval
- Assignee:
- Fuel Python (Deprecated)
- Definition:
- New
- Series goal:
- None
- Implementation:
-
Unknown
- Milestone target:
- None
- Started by
- Completed by