Skip to content

Reevaluate table columns #7

@needmorecowbell

Description

@needmorecowbell

Once the first fully functional workflow is able to be made (blocked by #5 ), we can start answering questions about how useful this database structure truly is. We will need to first begin stress testing different parts of the service to account for how people might use and abuse it.

Ie: handling many device registrations at once, unsanitized data, indexing on a large table.

query testing will be a project in itself. If the queries aren't intuitive and quick, the structure of the tables might need reworked. For example, it may be best to hybridize our database solution, whether that means relying more heavily on the jsonb data type, or a table for each new device. This will be very important as scaling increases.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions