Skip to content

JSON Schema

Jump to bottom
oliviajerdee edited this page Jan 12, 2023 · 1 revision

JSON Schema

image

Figure 7: General schema design for chat client data storage

Data storage: When any form of data is stored / accessed, it will have to go through a JSON file. This file contains 4 main categories; Per User, Login, Chat Room, and Messages. Each category will have subcategories containing data that is relevant to its parent category. Both storage and access will be executed using the async()function.

Category interactions: In order for storage on the server to be kept low and application speed high, the JSON schema utilizes linking through the use of ID’s. For example, the category Messages contains both the message content as well as the user ID of who sent it. In doing this, it prevents the need to create duplicate data for the categories Per User and Chat Room.

Potential Issues / Concerns: It is very likely that during the development process, problems with the schema may arise. We might run into an issue with data collisions on storage or performance bottlenecks. It is also possible that we may find a way to improve the schema through additional linking and / or streamlining data storage by removing subcategories that we deem unnecessary. Whatever the changes may be, it will be reflected in this technical proposal at a later date.

Clone this wiki locally