What people recommend, in their own words, with the receipt.
Application monitoring and error-tracking company.
7 things
ClickHouseSoftware
We ultimately chose ClickHouse after having engineers on the newly-formed Search and Storage Team individually prototype what Snuba could look like on top of the various systems.
Sentry on choosing ClickHouse to back its new Snuba search infrastructure
blog.sentry.io ↗·2019-05-16Wrong?
RustSoftware
As of yesterday, we have dramatically cut down that processing time (and CPU utilization on our machines) by replacing our source map handling with a Rust module that we interface with from Python.
Sentry on replacing Python source map handling with a Rust module
blog.sentry.io ↗·2016-10-19Wrong?
PostgreSQLSoftware
The application is backed by several PostgreSQL and Redis clusters, Google Cloud Storage, Snuba and Clickhouse clusters, and a bunch of other services like Relay and Symbolicator that are associated with our processing pipeline.
Sentry describing what its monolith is backed by
sentry.engineering ↗·2023-11-15Wrong?
DjangoSoftware
Sentry is a monolithic Python Django application deployed in several form factors (web servers, Kafka consumers, Celery workers, etc).
Sentry on its monolithic Python Django application
sentry.engineering ↗·2023-11-15Wrong?
RedisSoftware
For example, we use Redis to cache individual query results, which coalesces some of our more bursty and frequently repeated queries into a single ClickHouse query and removes unnecessary load from the ClickHouse cluster.
Sentry on caching Snuba query results in Redis
blog.sentry.io ↗·2019-05-16Wrong?
KafkaSoftware
Writing to Snuba starts with reading from a Kafka topic of JSON events that have gone through Sentry’s normalization and processing steps.
Sentry on feeding Snuba from a Kafka topic of events
blog.sentry.io ↗·2019-05-16Wrong?
PythonSoftware
This meant that even ignoring any optimizations, just replacing Python with Rust could relieve our chokepoint.
Sentry on Python becoming a chokepoint for source map processing
blog.sentry.io ↗·2016-10-19Wrong?
Every entry is a verbatim quote and a link to the public post it came from. Nothing is paraphrased. If it is not on record somewhere public, it is not here.
The verdict is what they actually said: loved and liked are explicit; recommended means they told others to get it; uses means they only say they use it; read is a book on their public shelf with no verdict; mixed and disliked are kept too.
A dashed affiliate link, sponsored or their own label means the post disclosed a relationship. It is shown, never hidden.
The small bar beside a date shows how dated a recommendation is for its kind of thing.
The bar shows how dated a recommendation is, for its kind of thing. Full and green is recent. It drains, and turns amber and then grey, as the post gets older.
What counts as old depends on the thing. A laptop praised four years ago has been replaced twice; a book loved twenty years ago is probably still loved. The bar is empty after about:
A striped bar means the post carries no date and the date shown is an estimate. No date at all, no bar.