mirror of
https://github.com/healthchecks/healthchecks.git
synced 2026-04-25 23:15:49 +03:00
[GH-ISSUE #1137] Support for CockroachDB as a DB Engine #787
Labels
No labels
bug
bug
bug
feature
good-first-issue
new integration
pull-request
question
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/healthchecks#787
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @adyavanapalli on GitHub (Mar 26, 2025).
Original GitHub issue: https://github.com/healthchecks/healthchecks/issues/1137
Hi, I had opened this ticket earlier because the way I wrote the description was considered AI slop. I just wanted to apologize for using an LLM to help write the description, so I'll try again with just my own words:
I've been experimenting with CockroachDB and thought it could be a valuable addition as a database option for our app. It's compatible with PostgreSQL, so integrating it should be straightforward.
CockroachDB's distributed architecture ensures high availability, meaning our app wouldn't rely on a single database that could fail and cause downtime. I've already made the necessary adjustments to get CockroachDB working with our application, and it's been performing well in my tests.
I believe this could enhance the resilience of our deployments. If you're interested, I can submit a pull request with the changes.
@adyavanapalli commented on GitHub (Apr 1, 2025):
Any comments on this, cuu508?
@cuu508 commented on GitHub (Apr 1, 2025):
I remember following CockroachDB development, and testing Healthchecks against it back when it had Apache license. A Django adapter (
django-cockroachdb? don't remember if this one or another) was being actively developed and becoming more and more feature complete. CockroachDB later switched to BSL license and fell off my radar. Looking at its current license, looks like it's gone full proprietary now?This makes it a non-starter for me, and I'm not interested in spending effort supporting it.
If you are interested in running Healthchecks test suite against CockroachDB on new commits, I think a simple solution would be to do that in a fork.
@adyavanapalli commented on GitHub (Apr 1, 2025):
No problem, thanks for your response :)