Here is where things go wrong:
dev.to/0xrumple/comment/5e8l
Consider the other scenarios as well: what if you have to look for a particular lesson? You'll end up having to scan all of them!
Looking them how? by title?
That's not our job, that's algolia's job ;)
I really think your use case gains nothing by using a NoSQL store
The most part I feel will get right, is the logical nesting of documents instead of m2m ugly relationships which have no actual benefit.
go huge on caching (set up a Redis cluster, maybe?).
We do caching as explained here:
dev.to/0xrumple/comment/5ebp
so I'm really, really skeptical of throwing away a relational model.
I'm posting this here to make sure we are taking the right decision :)
Are you sure you want to hide this comment? It will become hidden in your post, but will still be visible via the comment's permalink.
Hide child comments as well
Confirm
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Here is where things go wrong:
dev.to/0xrumple/comment/5e8l
Looking them how? by title?
That's not our job, that's algolia's job ;)
The most part I feel will get right, is the logical nesting of documents instead of m2m ugly relationships which have no actual benefit.
We do caching as explained here:
dev.to/0xrumple/comment/5ebp
I'm posting this here to make sure we are taking the right decision :)