Skip to content
All work

Copart, Member Mobile

In-app content service

I built a service that separates publishing alerts from releasing the Copart app.

Role
Built the service
Result
The business publishes alerts and banners without an app release.
Built with
  • Payload CMS
  • Redis
  • Node.js
  • Amazon S3
  • PublishPayload CMS publishes to Redis.
  • ServeThe API keeps serving cached alerts during a CMS outage.
  • Back upThe database is continuously backed up to Amazon S3.
  • Release-freeAlerts and banners go out without an app release.
  1. Payload CMSWhere alerts are writtenOffline
  2. RedisKeeps the published alerts
  3. APIServes the app from Redis

When the CMS goes down, the app keeps showing the alert. The business ships alerts and banners without an app release.

Problem

The Copart in-app content service had to keep alerts available during a CMS outage.

What I built

I built the in-app content service on Payload CMS. It publishes to Redis, and the API serves cached alerts. The database is continuously backed up to Amazon S3.

Result

The business can publish alerts and banners to the Copart app without an app release.

I’ve kept this to what my resume says. Ask me for more detail when we talk.

Ask Kai about this