back_bone · the sukoon platform backend

Everything Sukoon did ran through two Lambdas.

Users, experts, calls, payments, WhatsApp, events, games and content for Sukoon Unlimited, an agetech startup for elderly people: one Flask API serves the app and the admin desk, and a scheduler wakes every five minutes to book calls, send reminders and keep experts online.

83api endpoints
2lambda functions
5 minscheduler heartbeat
10kactive users served
01 — the api, by domain

83 endpoints, one square each

gamesProcessor is a Flask-RESTful app behind API Gateway, adapted to Lambda with aws-wsgi. Each square below is one /actions/… route, grouped into domains by hand.

02 — the scheduler

Every five minutes, the jobs run side by side

A rate(5 minutes) rule fires the scheduler Lambda. A thread pool runs its jobs in parallel, and due calls and messages go back through the API’s own /actions/call and /actions/send_whatsapp, so there is one path for everything.

03 — one call, across the platform

Booked here, placed here, scored by mark8

  1. A senior books a slot

    In the app, or through ARK-I on WhatsApp.

  2. The schedule is stored

    Recurring bookings expand into one-off schedules.

  3. A scheduler tick finds it due

    Nudges both people on WhatsApp and pings Slack.

  4. The call is placed

    Through /actions/call; the call platform reports back over webhooks.

  5. mark8 reads and scores it

    Topics, personas and a conversation score land on the call.

  6. Problems escalate

    Escalations reach the team before anyone has to ask.

the sukoon platform
python · flask-restfulaws lambda · amplify · api gatewayaws-wsgimongodbs3cashfreefirebase fcmopenaiwhatsappslack