Talk about your next project
ReadySet case study

The lesson

Put a before-and-after table under the headline stats so a technical buyer sees each metric's starting point next to its result.

The move

A logo card for Grupo Ótima Digital sits above the headline, a one-line subhead and three stat tiles: "30%" Database Load Reduction, "<1 week" To Results and "0" Application Changes. A "Before and after Readyset" table follows, with Metric, Before Readyset and After Readyset columns for database utilization, cached query coverage, query throughput offloaded, and cache traffic and CPU use. The body runs through "About the Customer", "Customer Challenge" (three bulleted symptoms, then why Redis and the ProxySQL Query Cache were ruled out), and "Customer Solution" with four bullets and a quote from Henrique Müller, Senior Software Engineer. Production monitoring graphs with captions come next, then "About Readyset", a "Want results like these?" demo box and "More customer stories".

Why it works

  • Our readThe table pairs each result with its baseline, such as a 72-vCPU MySQL server at ~80% against a load reduction of over 30%, so an engineer can judge the change rather than take a single number on trust.
  • Our readNaming Redis and ProxySQL and explaining their TTL-based cache expiration answers the alternatives a database buyer would already be weighing.
  • Our readCaptioned production graphs showing ~4k qps on 10GB of memory give a technical reader evidence beyond the quote and the stat tiles.

What not to copy

Don't copy the MySQL caching details, the Redis and ProxySQL comparison or the repeated summary line under the table. Keep the stat tiles, the before-and-after table, the challenge section that rules out named alternatives, the engineer's quote and the captioned production evidence.

More from ReadySet

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.