Architecture
The ME E2E service is a Go HTTP API built with the Fiber framework. It sits at the edge of the push notification sending chain and acts as a recording layer for end-to-end tests: the delivery service calls it after every push dispatch, and test suites query it to verify that correct notifications were sent to the right providers.
Overview
Delivery Service
│
│ POST /providers/:provider?save=true
▼
ME E2E Service ──► PostgreSQL (push_message)
│
│ GET /customers/:customerId/campaigns/:campaignId
│ GET /customers/:customerId/campaigns/:campaignId/clients/:clientId
▼
E2E Test SuitesThe service has three independent binaries:
| Binary | Purpose |
|---|---|
|
HTTP server — receives and serves notifications |
|
Runs database migrations (executed as a pre-deploy hook) |
|
Periodic maintenance tasks (runs as a cron job every 10 minutes) |
Endpoints
Public (no authentication)
| Method | Path | Description |
|---|---|---|
GET |
|
Returns |
GET |
|
Pings the database; returns success or failure |
Escher Authenticated
| Method | Path | Description |
|---|---|---|
POST |
|
Record a notification from a provider ( |
POST |
|
Alternative endpoint for saving a notification from the request body |
GET |
|
List notifications for a campaign (paginated via |
GET |
|
List notifications for a specific client device |
Supported provider names: apple, apns, google, huawei, vapid, fcm.
For the full API specification see REST API.
Database
The service uses PostgreSQL. Migrations are managed with goose and run via the cmd/migrate binary before each deployment.
The main table is push_message, which stores one row per recorded notification with fields including customer_id, campaign_id, hardware_id, provider, app_code, title, body, push_token, run_id, and original_payload.