NewSeveral services per siteRead
Demo dataDemo page: the numbers and events shown are made up, until we have real measurements.

Customers

Case study (example): an online shop that holds up on sale day

By the Syli Labs team · Published · 6 min read

[X]%faster pages
[N]releases per week
[0]outages on sale day

Numbers to be provided and approved by the customer before publication.

In short

This is a layout example: the customer, the numbers and the quote are made up. The real case study will be published with the customer’s written approval.

The starting point

[Situation before: host, problems encountered, impact on sales. Two or three paragraphs, in the customer’s own words.]

What we set up

The shop is split into three services, each in its own container, talking to each other over a private network:

  • shop (Next.js): the only public service, with the site’s address;
  • api (Phoenix): private, called by the shop;
  • database (PostgreSQL) and cache (Valkey): private, used by the API.
  • Development: every push to GitHub updates a private address;
  • Staging: the team tests on an anonymized copy of the database;
  • Production: the same image, released in one click, with a backup just before.

“[Real customer quote, approved in writing.]”

[First Last name], [job title]

The results

[Measured results, with the measurement period and their source.]