Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
With some differences in data structuring in SQL vs NoSQL, I embedded the session documents into user documents. This way we only need one operation per update and one operation for fetching both user and the session
Ideally the user and session object wouldn't be separated, as in DB they exist embedded together, but in order to conform to API's down the line that would rely on separate session and user object I splitted them up
And since the userId field in session is not used in application code, but only exists in the DB for joins, I ommited that field for unnecessary redundancy
I used sqlite as a base doc. Should be fine