TypeSense is not a database per se, but since a lot of what we're using MongoDB for in this project is filtering and searching, it might make sense to completely replace MongoDB with TypeSense. I could imagine seeing huge performance improvements with this, although the migration is not trivial, of course.
See also: #188
Doing this might make the following issues much easier or even unnecessary:
170
151
148
144
130
128
123
50
Some things could also become more difficult, like #88.
It might also make sense to consider graph databases (maybe even in combination with TypeSense), as some things we're doing, and some things that we would like to do in the future, are graph-based.
TypeSense is not a database per se, but since a lot of what we're using MongoDB for in this project is filtering and searching, it might make sense to completely replace MongoDB with TypeSense. I could imagine seeing huge performance improvements with this, although the migration is not trivial, of course.
See also: #188
Doing this might make the following issues much easier or even unnecessary:
170
151
148
144
130
128
123
50
Some things could also become more difficult, like #88.
It might also make sense to consider graph databases (maybe even in combination with TypeSense), as some things we're doing, and some things that we would like to do in the future, are graph-based.