Sentry is atrocious. The thing runs Postgres, Redis, Clickhouse, Kafka, like a dozen huge components on their own as its backend. Their hosted vs self-hosted support is bad so deploying the thing yourself is a nightmare. The opposite of a zero config philosophy.
You're not wrong that it runs too much and it's not something that makes us particularly happy. The reason it ended up this way is that Sentry the SaaS has to support an enormous amount of customers and we haven't done a particular good job at scaling it down to small installations in recent years.
Congratulations Armin and curious to that "what's next" (it's a bit of a cliff hanger in the post)
Sentry is atrocious. The thing runs Postgres, Redis, Clickhouse, Kafka, like a dozen huge components on their own as its backend. Their hosted vs self-hosted support is bad so deploying the thing yourself is a nightmare. The opposite of a zero config philosophy.
You're not wrong that it runs too much and it's not something that makes us particularly happy. The reason it ended up this way is that Sentry the SaaS has to support an enormous amount of customers and we haven't done a particular good job at scaling it down to small installations in recent years.