Talk about your next project
Altinity case study

The lesson

Build a technical case study around one precise problem the customer hit, quantify it in their own units, and show the exact fix.

The move

The headline sits beside a SenseOn + Altinity logo card, followed by three short paragraphs on who SenseOn is, why ClickHouse is core to the product, and the 2023 goal to support larger customers. "Adoption of ClickHouse" explains the move off ElasticSearch and the role of sampling keys. "Challenge: Optimizing the Sampling Keys for Scalability" states the cost of a schema change: 50 extra bytes per row (as opposed to 7 bytes per row) and approximately 30% extra storage usage. "Solution: Altinity Support for ClickHouse" lists two recommendations as bullets, then a pull quote from CTO James Mistry, and a "Conclusion" with more Mistry quotes and a list of other support topics.

Why it works

  • Our readAn engineer reading the challenge sees a trade-off they may face themselves, better sampling against worse compression, so the story reads as useful advice and not only praise.
  • Our readThe bullets name real codecs and the system.parts_column table, which proves the vendor's support goes past generic help.
  • Our readThe Conclusion widens from one incident to a list of topics from user management to INSERT performance, so the reader sees the fix as part of an ongoing relationship.

What not to copy

Don't copy the ClickHouse sampling-key details, the ZSTD codec list or the ElasticSearch comparison. Keep the order of background, one precise technical problem with the customer's own numbers, a bulleted fix, a named technical-leader quote, and a closing that broadens to ongoing work.

More from Altinity

More case studies

Steal it for your brand.

Tell us what you want to make. We’ll talk through how to put these ideas to work for your brand.