Healthchecks.io now uses self-hosted object storage
blog.healthchecks.io
Healthchecks.io now uses self-hosted object storage
1–10 of 82 posts
Re: Healthchecks.io now uses self-hosted object storage
#2Re: Healthchecks.io now uses self-hosted object storage
#3I'm sure it's a lot better now but everytime I see btrfs I get PTSD.
Re: Healthchecks.io now uses self-hosted object storage
#4Re: Healthchecks.io now uses self-hosted object storage
#5Re: Healthchecks.io now uses self-hosted object storage
#6I don't get it, if it's running on the same (mentioning "local") machine, why does it even need the S3 API? Could just be plain IO on the local drive(s)
Re: Healthchecks.io now uses self-hosted object storage
#7I don't get it, if it's running on the same (mentioning "local") machine, why does it even need the S3 API? Could just be plain IO on the local drive(s)
> The costs have increased: renting an additional dedicated server costs more than storing ~100GB at a managed object storage service. But the improved performance and reliability are worth it.
Re: Healthchecks.io now uses self-hosted object storage
#8Re: Healthchecks.io now uses self-hosted object storage
#9I don't get it, if it's running on the same (mentioning "local") machine, why does it even need the S3 API? Could just be plain IO on the local drive(s)
Part of it is that it follows the object storage model, and part of it is just to lock people into AWS once they start working with it.
Re: Healthchecks.io now uses self-hosted object storage
#10I'm sure it's a lot better now but everytime I see btrfs I get PTSD.