Work in progress · Version 1.1, last updated 6 November 2026
Architecture

Containers (C4 level 2)

The deployable units of padi.com and the finder, what technology each uses, and how they talk to each other.

Website containers

Figure 4. Website containers.
Figure 4. Website containers.

Finder and search containers

Figure 5. Finder and search containers.
Figure 5. Finder and search containers.

Container catalogue

Versions and support dates are in Technology.

Container Technology Hosting Repository Responsibility
Zone rulesets Cloudflare rulesets Cloudflare edge.padi.com (Terraform) WAF, rate limits, cache, redirects
Routing Worker TypeScript Worker Cloudflare edge.padi.com Legacy redirects, PADI Travel page proxy
Localisation Worker TypeScript Worker Cloudflare edge.padi.com Country, region and language decision, sanctions gate, signed headers
Next.js frontend Next.js, React, Node.js Acquia Front End Hosting padi.com Page rendering, BFF routes, MyPADI, sign-in
Drupal CMS Drupal, PHP Acquia Cloud Platform drupal.padi.com Content model, editorial workflow, translation jobs, cache purge, search indexing
MySQL and Memcache Acquia-managed Acquia n/a Content store and cache
locator-api Go AWS EC2 autoscaling group locator.padi.com Public finder API: shops, courses, map, suggest, filters
search-api Go AWS EC2 autoscaling group search.padi.com OpenSearch queries for the finder and website search
Pipeline Lambdas Go on AWS Lambda AWS search.padi.com Apply PADI Travel changes, build and publish search documents, member file, translations
OpenSearch Amazon OpenSearch Service Amazon OpenSearch Service search.padi.com Finder indexes and Drupal content index
FinderDB Aurora PostgreSQL + PostGIS Aurora Serverless v2 search.padi.com Copy of Travel data, translations, document store

Component-level (C4 level 3) diagrams are with each system: padi.com and Drupal, Finder and search, Cloudflare.