You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Oct 2, 2020. It is now read-only.
We should consider moving away from MongoDB and using something like Postgres instead.
MongoDB was the correct choice in terms of iterating quickly when Apiary was smaller, since there was no need to manage a rapidly evolving schema. However, MongoDB's schemaless nature can also be a curse.
As Apiary is growing technically, I grow less confident of changing the schema when new features are added because I fear I might break something else that depended on an older part of the schema. It's really quite hard to catch since the database will not do it for you.
I think having a more rigid schema will serve us in the long run, seeing as we have a better sense of where this project is going.
My thoughts on a super simple schema for now would be something like this:
The text was updated successfully, but these errors were encountered:
We should consider moving away from MongoDB and using something like Postgres instead.
MongoDB was the correct choice in terms of iterating quickly when Apiary was smaller, since there was no need to manage a rapidly evolving schema. However, MongoDB's schemaless nature can also be a curse.
As Apiary is growing technically, I grow less confident of changing the schema when new features are added because I fear I might break something else that depended on an older part of the schema. It's really quite hard to catch since the database will not do it for you.
I think having a more rigid schema will serve us in the long run, seeing as we have a better sense of where this project is going.
My thoughts on a super simple schema for now would be something like this:
The text was updated successfully, but these errors were encountered: