Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Documentation: More details about using an external database #9611

Merged
merged 2 commits into from
Jan 20, 2022

Conversation

alafanechere
Copy link
Contributor

What

Some users are asking in which context they might want to use an external database for Airbyte.

How

I tried to update the doc to suggest it's more reliable to use an external database.

@alafanechere alafanechere added the area/documentation Improvements or additions to documentation label Jan 19, 2022
@alafanechere alafanechere temporarily deployed to more-secrets January 19, 2022 17:02 Inactive
@alafanechere alafanechere changed the title explain why it's better to use an external database Documentation: More details about using an external database Jan 19, 2022
* Through a dedicated custom Postgres instance \(the `airbyte/db` is in this case unused, and can therefore be removed or de-activated from the `docker-compose.yml` file\).
* Through a dedicated custom Postgres instance \(the `airbyte/db` is in this case unused, and can therefore be removed or de-activated from the `docker-compose.yml` file\). It's not a good practice to deploy mission-critical databases on Docker or Kubernetes.
Using a dedicated instance will provide more reliability to your Airbyte deployment.
Moreover, using a Cloud-managed Postgres instance (such as AWS RDS our GCP Cloud SQL), you will benefit from automatic backup and fine-grained sizing. You can pick a pretty small instance for a starter, as the Airbyte database will only host configurations and jobs metadata.
Copy link
Contributor

@tuliren tuliren Jan 19, 2022

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I am not sure we can say that our db instance is pretty small. Because we track job histories in the jobs database, that database can actually grow pretty large. We had OSS users before that had trouble running file-based migration because of the total database size. So it's probably better to remove the second half of the sentence?

Suggested change
Moreover, using a Cloud-managed Postgres instance (such as AWS RDS our GCP Cloud SQL), you will benefit from automatic backup and fine-grained sizing. You can pick a pretty small instance for a starter, as the Airbyte database will only host configurations and jobs metadata.
Moreover, using a Cloud-managed Postgres instance (such as AWS RDS our GCP Cloud SQL), you will benefit from automatic backup.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ok, I'll rephrase this to suggest that they can start small but the job tables might grow according to their usage of Airbyte.

@alafanechere alafanechere requested a review from tuliren January 20, 2022 08:04
@alafanechere alafanechere temporarily deployed to more-secrets January 20, 2022 08:05 Inactive
@alafanechere alafanechere merged commit b8cd772 into master Jan 20, 2022
@alafanechere alafanechere deleted the augustin/doc/update-configuring-airbyte-db branch January 20, 2022 10:18
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/documentation Improvements or additions to documentation
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants