Appfy

See all cases

Ticketing platform

Move the back office without closing the box office.

A ticketing platform needed room to grow without taking down the site where the public buys.

The problem
The site the public sees and the back office, with accounts, payments and emails, ran together and needed to grow. Estimate: 1 hour stalled when a show goes on sale × 2,000 tickets an hour × R$200 (assumptions) ≈ R$400k in stalled sales.
What Appfy did
Appfy moved only the back office to the cloud, left the site where it was and put a door with a doorman between them, which also holds back floods of requests. Payments and emails went into queues that retry and alert the team when something fails.
The gain
For buyers, the site is the same. The records show a separate DLQ, alert and retrigger path. No ticket correctness or successful email delivery is established, and there is no configured retry policy or tested recovery.

  1. Scene 1 of 7The company

    Storefront and back office in one building.

    A platform sells tickets for shows and events. The site the public sees and the back office, with accounts, payments and emails, ran together, like a shop and its stockroom in one building.

  2. Scene 2 of 7The problem

    Growing without going down, and without letting bots in.

    The platform had to handle more people at once, stay online and block floods of requests and bots. With everything in one building, growing one part meant growing it all.

  3. Scene 3 of 7The choice

    Only the back office moves building.

    Appfy moved only the back office to the cloud: accounts, payments, events and emails. The site stayed where it was, and between the two a door with a doorman checks the key of every message.

  4. Scene 4 of 7What Appfy did

    An email that fails does not vanish: it alerts the team.

    Whoever buys a ticket gets an email. Now that message joins a queue, like a ticket number at a counter, and goes out in turn. If it fails, it retries; if it keeps failing, it alerts the team.

  5. Scene 5 of 7What Appfy did

    What the records show for the accounts is an initial sketch. It proposes completing the Google, Okta and Facebook setup, and audit records for login, logout, signup and modify. Its premises include not storing passwords. Those statements are the proposal's semantics, not verified behavior.

  6. Scene 6 of 7What changed

    On screen, nothing changes.

    Buyers stay on the same site. The records show a separate DLQ, alert and retrigger path. No ticket correctness or successful email delivery is established, and there is no configured retry policy or tested recovery.

  7. Scene 7 of 7And in your company?

    Has your platform outgrown itself? Move only what needs to move.

    Changing systems does not have to be all or nothing. Appfy first draws what stays and what moves, and how the two parts talk. Start with a free 30-minute conversation.