Database and Backend

[DianaLunaXIV]

I threw together a diagram to roughly conceptualize what data we need to store in a database and how it could be organized. Feedback needed!

[lanebpemberton]

Looking good! Some thoughts:

• Since 'ship' could describe more than just the sprite of the ship it could be a good candidate for its own table. (e.g. Table: 'ships' with Fields: 'id', 'name', 'health', 'damage', 'sprite', 'width', 'height', etc). Since we're using mongo I think we can err on the side of modeling more fields or columns per table than we actually need to utilize.
• Going off the previous sentiment I would add Fields: 'time_alive', 'enemies_killed', 'bad_codes_blasted', 'timestamp', 'ship_used_id' (this way when you view your high score you can see which ship was used during that run. it would be linked to the ship id in the ship table)
• Love your thought process on practices!

[markhamtrenton]

Very good layout Brent for the backend!

[DianaLunaXIV]

Here's an updated version of this diagram. This includes more concrete decisions about data to save, taking your suggestions into account.

[DianaLunaXIV]

Our backend is in a state that will cooperate with the game, I think. It will not be difficult to add additional queries and mutations if necessary and small changes.