Skip to content

Kaapi: V1.0: Database optimization for performance issues #808

Closed
0 of 1 issue completed
Closed

Description

@AkhileshNegi

Is your feature request related to a problem?
The database for v1.0 may not be optimized for performance and consistency. This could lead to inefficiencies and complications as we scale.

Describe the solution you'd like

  • Audit indexes: add missing ones and remove unused
  • Standardize on ID vs UUID usage across tables
  • Standardize the timezone followed
  • Log slow queries
  • Adding ENUMS

Activity

  1. self-assigned this
    on May 4, 2026
  2. changed the title [-]Kaapi v1.0: Database Review[/-] [+]Database: Optimize for performance issues[/+] on May 4, 2026
  3. moved this from To Do to In Progress in Kaapi-devon May 5, 2026
  4. changed the title [-]Database: Optimize for performance issues[/-] [+]Kaapi: V1.0: Database optimization for performance issues[/+] on May 7, 2026
  5. AkhileshNegi commented on May 16, 2026

    @AkhileshNegi
    CollaboratorAuthor

    Audit indexes: add missing ones and remove unused
    This is done. We also added partial indexes where they made sense

    Standardize on ID vs UUID usage across tables
    We discussed this and agreed on a simple rule: use UUIDs for anything user-facing, and keep IDs for internal-only use.

  6. moved this from In Progress to Closed in Kaapi-devon May 16, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

  • Status
    Closed

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions