snuba

1) Do you have two separate codebases for free and paid? No. Sentry has one codebase between free and paid. We have a Django monolith plus some services where all our features are implemented: https://github.com/getsentry/sentry https://github.com/getsentry/relay https://github.com/getsentry/snuba https://github.com/getsentry/vroom etc. We have a Docker Compose wrapper in a separate repo: https://github.com/getsentry/self-hosted We have a private repo called getsentry/getsentry that is another Django app that imports the public one and uses Django signals (iirc) to meter usage for billing. That is what we deploy to SaaS. All product features are implemented in the public repos. 3) How about employee access? Employee access is managed through UI, I honestly don't know whether it lives in getsentry/sentry (public) or getsentry/getsentry (pr

Sentry.io (http://sentry.io) | Senior Software Engineer, Storage | ONSITE (San Francisco or Seattle, 3:2) | Full-time Sentry.io builds a suite of application monitoring tools that developers love. The Search and Storage team builds out high-volume ingestion (hundreds of thousands of records per second) for our near-real-time event and metric storage built on top of the columnar data store ClickHouse. We’re looking for a seasoned engineer who has dealt with high-volume, production-traffic serving systems who’s searching for a new challenge. The vast majority of our work is source-available; come take a look at what our team is working on at https://github.com/getsentry/snuba. Note that this position does have an on-call component. E-mail me, the hiring manager, at oliver.newland@sentry.io to learn more. Official job req: https://sentry.io