Skip to content
This repository has been archived by the owner on Oct 2, 2020. It is now read-only.

Migrate to Postgres #118

Open
onbjerg opened this issue Jan 9, 2020 · 1 comment
Open

Migrate to Postgres #118

onbjerg opened this issue Jan 9, 2020 · 1 comment
Assignees
Labels
discussion This issue needs to be fleshed out enhancement New feature or request

Comments

@onbjerg
Copy link
Contributor

onbjerg commented Jan 9, 2020

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:

https://i.imgur.com/GCNZctK.png

@onbjerg onbjerg added enhancement New feature or request discussion This issue needs to be fleshed out labels Jan 9, 2020
@onbjerg onbjerg self-assigned this Jan 9, 2020
@lkngtn
Copy link
Member

lkngtn commented Jan 10, 2020

I don't have much to add from the technical side, but I think the described rationale for the switch makes intuitive sense.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
discussion This issue needs to be fleshed out enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants