Talk about your next project
Yugabyte case study

The lesson

Build a database case study as stacked blocks where the reader gets the customer's scale number, the failed prior tools, and the results without reading a paragraph.

The move

The hero puts the Plume logo over one sentence with the scale claim, "over 27 billion operations per day," and a Contact Us button. "AT A GLANCE" gives three icon tiles covering who Plume serves, that "MongoDB was unable to scale and Apache Cassandra was hard to operate," and the 60-node outcome. Next come a short company profile naming Comcast, Sky UK and Bell Canada, a "CHALLENGES" bullet list, and two side-by-side quotes from Aman Singla and Muru Guruswamy. The page closes with "YUGABYTE SOLUTION" icons, "TECHNICAL RESULTS" (312K+ transactions per second, 35TB, <30-40ms) and "BUSINESS RESULTS" checkmarks, then "SEE MORE FROM PLUME" links to a talk video and an outage story.

Why it works

  • Our readNaming the two databases that failed, with specifics like latency in the 3-5 second range, lets an engineering buyer match the story to their own situation.
  • Our readSplitting technical results from business results serves both the architect who wants throughput and latency and the executive who wants onboarding and less time managing databases.
  • Our readThe closing links to a conference talk and an AZ outage write-up give a skeptical reader deeper proof without lengthening the card.

What not to copy

Don't copy Plume's smart home framing, the MongoDB and Cassandra comparison, the GDPR point or the AWS outage follow-up. Keep the order of hero stat, at-a-glance trio, profile, challenge bullets, paired quotes, solution icons, two-tier results and links to deeper proof.

More from Yugabyte

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.