NoSQL databases were nothing new to me when I started the Writestreak project and decided to go with the Firebase realtime database. The new thing was just the realtime part. I've really enjoyed working with the realtime concept but at the same time I've gotten a reminder why I have mainly stayed away from the NoSQL databases in general. Maybe I've just used the relational ones so much that it's hard for me to live with the features I have learned to take as granted with them.
It's just that I really love the realtime part. If only there were a relational database with similar reactivity. But knowing the details behind the scenes for both technologies I know this might be next to impossible to achieve. At least in full. The result would be somewhat s compromise, not perfect in either area. And I'm not sure that would be good either. Maybe the real solution is to use both side by side, each for features depending on their greatest strengths.
But that would introduce quite a lot of new complexity. At least for small projects like this it would be too much. Better stick to one and just cope with it's weaknesses, trying to find alternative solutions or implementing workarounds instead.