QuickBite is an enterprise-grade, cloud-native food ordering, restaurant management, and hyper-local delivery backend. Built using a Domain-Driven Vertical Slice Architecture on Java 25 and Spring Boot 4.1.0, the platform leverages PostgreSQL (PostGIS) for spatial queries, Redis (Redisson) for distributed locking and real-time geospatial driver tracking, and Apache Kafka for cross-domain event choreography.
- Architecture Overview
- Key Features & Domain Capabilities
- 1. Security, Identity & Stateful Sessions (
auth) - 2. Multi-Round Dispatch & Geospatial Tracking (
delivery) - 3. Order Engine & Pricing Subsystem (
order,cart) - 4. Payments, Webhooks & Automated Reconciliation (
payment) - 5. Multi-Tier Composite Routing Gateway (
common/routing) - 6. Onboarding Pipelines & Workload-Balanced Allotment (
onboarding,allotment) - 7. Restaurant Catalog, Cuisines & Menu Items (
restaurant,menu) - 8. Reviews & Rating Recalculation (
review) - 9. Joined-Inheritance Notification Center (
notification)
- 1. Security, Identity & Stateful Sessions (
- Technology Stack
- Role-Based Access Control (RBAC) Matrix
- Quickstart
- 🎬 End-to-End Demo Guide: Placing an Order & Delivery Offer Tracking
- Step 1: Start the Interactive Delivery Agent Tracker CLI
- Step 2: Authenticate in Postman (Customer & Restaurant Owner)
- Step 3: Add Menu Item to Cart & Preview Checkout (Customer)
- Step 4: Place Order — Cash on Delivery (COD) or Online Payment (Razorpay)
- Step 5: Restaurant Owner Accepts & Prepares Order (Triggers Dispatch)
- Step 6: Accept Dispatch Offer in Python CLI & Mark Order Ready
- Step 7: Delivery Agent Login, Session Challenge & Order Delivery
- Documentation Directory
- Project Status & Milestone Checklist
flowchart TB
subgraph Clients["Client Applications"]
Customer["Customer App"]
Restaurant["Restaurant Portal"]
Driver["Delivery Agent App"]
Admin["Admin Console"]
end
subgraph Perimeter["Security & Gateway"]
SecurityFilter["Spring Security 6+"]
DualJWT["Dual-JWT Decoder<br/>(SCOPE_API + ROLE_* vs SCOPE_AUTH)"]
Argon2Hasher["Argon2 Password Hasher"]
end
subgraph BoundedContexts["Core Domains (14 Bounded Contexts)"]
direction TB
AuthDomain["auth: Sessions & Family Rotation"]
UserDomain["user: Profiles & PostGIS Addresses"]
OnboardingDomain["onboarding: 3-Way Partner Pipeline"]
AllotmentDomain["allotment: Workload Balancer"]
RestaurantDomain["restaurant: Spatial Catalog & Hours"]
MenuDomain["menu: Cuisines & Menu Items"]
CartDomain["cart: Cart Validation & Fees"]
OrderDomain["order: Pricing & Acceptance Deadline"]
PaymentDomain["payment: Razorpay & Reconciliation"]
DeliveryDomain["delivery: Multi-Round Dispatch & GEO"]
VehicleDomain["vehicle: Fleet Management & VIN"]
ReviewDomain["review: Ratings & Recalculation"]
NotificationDomain["notification: Joined Notification Root"]
CommonDomain["common: S3 Presigned URLs & Routing"]
end
subgraph Datastores["Persistence & Caching"]
PG[("PostgreSQL 18 + PostGIS<br/>Hibernate Envers Auditing")]
Redis[("Redis 8<br/>Cache, Sessions, Redis GEO")]
Redisson[("Redisson Distributed Locks")]
end
subgraph Messaging["Event Broker"]
Kafka["Apache Kafka 4.3<br/>7 Domain Streams + DLT Queues"]
end
subgraph External["External Integrations"]
OSRM["Local OSRM Routing (:5001)"]
S3["AWS S3 Storage"]
Razorpay["Razorpay Payment Gateway"]
end
Clients --> Perimeter
Perimeter --> BoundedContexts
BoundedContexts <--> PG
BoundedContexts <--> Redis
BoundedContexts <--> Redisson
BoundedContexts <--> Kafka
BoundedContexts <--> OSRM
BoundedContexts <--> S3
BoundedContexts <--> Razorpay
- Dual-JWT Token Architecture: Asymmetric RSA256 tokens separating business API access (
aud: quickbite-api,type: access, 15m) from session challenge tasks (aud: quickbite-auth,type: session-limit, 5m). - Client-Aware Hybrid Refresh Token Transport (
X-Client-Type):WEB_BROWSER(web_browser): Refresh tokens are delivered exclusively viaHttpOnly,Secure,SameSite=Strictcookies (qb_refresh_token) and stripped (null) from JSON bodies.MOBILE_APP(mobile_app): Refresh tokens are returned directly in theAuthResponseJSON payload and accepted viaRefreshRequestJSON bodies for native Keychain/Keystore storage.
- Generation-Tracked Token Families & Breach Detection: Refresh tokens belong to a
RefreshTokenFamilywith monotonically increasinggenerationcounters and SHA-256 hashes in PostgreSQL. Replaying an already-used token (used_at != null) outside the 2-second Redis grace window triggers an immediateREQUIRES_NEWbreach revocation. - 3-Step Session Concurrency Challenge: Enforces 3 concurrent active sessions per user. Exceeding the limit returns
409 Conflictwith a 5-minutechallengeTokento list (GET /sessions), evict (DELETE /sessions/{id}), and claim (POST /claim-session) a session slot. - Automated Stale Token Retention Cleanup: Daily cron (
RefreshTokenCleanupScheduler) purges used, expired, or revoked tokens older than 30 days while retaining recent history for breach detection.
- 3-Round Concentric Dispatch: Orders automatically expand across candidate pools:
- Round 1: 3 km radius (2-minute window)
- Round 2: 6 km radius (3-minute window)
- Round 3: 10 km radius (5-minute window)
- Driver Offer Timeout: 45-second timer per candidate driver with automated failover to the next best driver.
- Redis GEO Real-Time Tracking: Drivers transmit live GPS coordinates stored in Redis using
GEOADD. Proximity candidate searches execute in sub-millisecond time viaGEORADIUSBYMEMBER. - Heartbeat & DB Sync: Active drivers maintain a 60-second Redis heartbeat TTL. A background scheduler syncs coordinates into PostgreSQL every 30 seconds.
- Fair Driver Assignment:
FairNearestDeliveryAssignmentStrategyoptimizes for distance while preventing driver starvation.
- 2-Phase Non-Holding Checkout & Cooldown: 5-second Redisson cooldown prevents duplicate submissions; isolated transactions ensure external routing and payment gateway HTTP calls never hold open DB connections.
- Price-Drift Protection (
expectedTotal): Validates checkout totals against real-time pricing and aborts with409 Conflict(PriceChangedException) if item prices or surge fees changed. - Chain-of-Responsibility Fee Calculation: Calculates Base Fee (₹15), Distance Fee (₹8/km), Surge Fee, Platform Fee (₹5), and 5% GST with min (₹20) and max (₹80) bounds and a 5-minute Redis route cache.
- Dual-Layer Distributed Timeouts (Redisson Delayed Queues + Reapers): Event-driven
RDelayedQueue+ atomicBLPOPworkers (OrderTimeoutConsumer) enforce the 2-minute restaurant acceptance deadline (PT2M) and 15-minute payment abandonment window, backed by safety-net cron schedulers.
- Strategy Pattern: Pluggable strategies for online methods (
UPI,CARD,NET_BANKING,WALLETviaOnlinePaymentStrategy),COD(CodPaymentStrategy), andStubOnlinePaymentStrategy. - HMAC-SHA256 Signature Verification: Cryptographic validation for both frontend checkout signatures and backend webhooks.
- Multi-Attempt Reconciliation (
First-Success-Wins): Reconciles all payment attempts on poll or retry, auto-refunding duplicate captures or late captures on abandoned/cancelled orders. - Kafka-Driven Automated Refunds: Event listeners automatically issue Razorpay refunds when orders are cancelled, declined, or refunded post-delivery by an admin.
- Tier 1 (OSRM): Local native high-performance OpenStreetMap routing machine on port
5001. - Tier 2 (Mapbox): Cloud Directions API fallback.
- Tier 3 (Haversine): Mathematical spherical distance fallback with 25 km/h urban velocity to ensure zero downtime.
- 3 Independent Pipelines: Multi-step applications for Restaurants, Delivery Agents, and Vehicles.
- Document & Image Management: AWS S3 presigned PUT URLs for direct, bandwidth-efficient uploads of KYC documents and facade photos.
- Automated Admin Allotment Engine:
WorkloadBalancedAdminSelectionStrategydistributes pending partner applications equally among administrators up to a maximum limit (max-assignees = 4).
- PostGIS Spatial Search: Spatial
/nearbyqueries filtering active restaurants within a radius (ST_DWithin/ST_DistanceSphere). - Menu Management: Dietary classifications (
VEG,NON_VEG,VEGAN), opening hours, image galleries, and instant availability toggles. - Cuisine Moderation: Global cuisine catalog with partner request and admin approval flows.
- Verified Customer Feedback: Reviews restricted to completed orders.
- Kafka Event Recalculation: Submitting or deleting a review publishes a
ReviewChangedEvent, automatically recalculating the restaurant's average rating and total review count.
- Single Root Aggregate: Joined-table inheritance (
Notification) with specialized subclasses:OrderNotification,PaymentNotification,RestaurantApplicationNotification,DeliveryAgentApplicationNotification,VehicleApplicationNotification,CuisineNotification. - Multi-Channel Delivery: In-app notifications, push notifications, and email delivery strategies.
| Layer | Technologies |
|---|---|
| Backend Framework | Spring Boot 4.1.0, Spring Security 6+, Spring Data JPA, Spring Kafka, Spring Validation |
| Language & Runtime | Java 25 (Temurin / GraalVM) |
| Relational Database | PostgreSQL 18.1 with PostGIS 3.4 & Hibernate Spatial |
| Auditing & Lineage | Hibernate Envers (@Audited) on core aggregates (User, Restaurant, Order, Payment, DeliveryAgent) |
| In-Memory & Cache | Redis 8.4-alpine, Redisson 4.7.0 (Distributed Locks & Delayed Queues), Redis GEO |
| Event Streaming | Apache Kafka 4.3.0 (KRaft mode) + Spring Kafka Dead Letter Topics (.DLT) |
| Cloud Storage | AWS SDK for Java v2 (S3 Presigned URLs) |
| Routing Engines | OSRM (Open Source Routing Machine), Mapbox Directions API, Haversine Math Fallback |
| Payment Gateway | Razorpay Java SDK 1.4.10 (UPI, NetBanking, Cards, Webhooks) |
| Security & Tokens | Nimbus JOSE+JWT, Argon2 Password Encoder, BouncyCastle, Yauaa (User-Agent Analyzer) |
| URL Prefix | Primary Role | Required Authority | Description |
|---|---|---|---|
/api/v1/auth/register/**, /login |
Public | None | Authentication & multi-role registration |
/api/v1/cuisines, /restaurants/** |
Public | None | Restaurant catalog, menus, and reviews |
/api/v1/webhooks/** |
Public (Signature) | None | Razorpay webhook notifications |
/actuator/health, /actuator/info |
Public | None | Service liveness and readiness probes |
/api/v1/auth/sessions/**, /claim-session |
Challenged User | SCOPE_AUTH |
Session challenge resolution & eviction |
/api/v1/files/upload-url |
Authenticated | SCOPE_API |
Direct S3 presigned PUT URL generation |
/api/v1/customer/** |
Customer | SCOPE_API + ROLE_CUSTOMER |
Cart, orders, delivery addresses, reviews |
/api/v1/restaurant-owner/** |
Partner | SCOPE_API + ROLE_RESTAURANT_OWNER |
Restaurant info, menus, order kitchen queue |
/api/v1/delivery-agent/** |
Driver | SCOPE_API + ROLE_DELIVERY_AGENT |
Availability, location ping, offers, pickup/delivery |
/api/v1/admin/** |
Administrator | SCOPE_API + ROLE_ADMIN |
Allotments, approvals, refunds, user management |
/actuator/** (all other) |
Administrator | SCOPE_API + ROLE_ADMIN |
Prometheus metrics and internal diagnostics |
git clone https://github.com/eshant52/quickbite-backend.git
cd quickbite-backend
# Setup local Docker Compose environment
cp .env.local.example .env.local
# Setup Spring Boot application environment
cp .env.example .envdocker compose --env-file .env.local --profile full up -dThis spins up PostgreSQL (:5430), Redis (:6377), and Kafka (:9092).
mkdir -p src/main/resources/certs
openssl genrsa -out src/main/resources/certs/private.pem 2048
openssl rsa -in src/main/resources/certs/private.pem -pubout -out src/main/resources/certs/public.pem./mvnw spring-boot:runVerify service readiness:
curl http://localhost:8080/actuator/healthDefault Super Admin Credentials (auto-seeded on startup):
- Email:
super.admin@quickbite.com - Password:
Admin@123
The repository provides ready-to-import Postman collections (Customer Portal, Restaurant Owner Portal, Delivery Agent Portal, Admin Portal) and environment files under postman/exports/.
To import and use the collections in Postman:
-
Create a New Workspace: Open Postman, click Workspaces → Create Workspace, and create a workspace named "Quickbite Internal" as shown below:
-
Click Import: Inside your new workspace, click the Import button in the top-left sidebar:
-
Select
/postman/exportsFolder: In the import dialog, click Folders and select the/postman/exportsfolder from the project directory: -
Confirm & Import: All 4 portal collections and the environment file (
Quickbite Local Dev) will appear in the preview modal. Click Import — you can now immediately use the Postman API collections:
Tip
For more details, comprehensive environment configuration, Docker setup, and routing engine options, look to the Installation and Configuration Guide. For detailed API endpoints, collection variables, and test scripts, see the Postman Developer Guide and REST API Catalog.
This step-by-step walkthrough demonstrates QuickBite's complete reactive order-to-delivery lifecycle:
- Interactive Delivery Agent Offer Tracker CLI (
track_delivery_offers.py): Logs in and tracks up to 10 delivery agents simultaneously, continuously pushes live Redis GEO heartbeats, polls for incoming offers, and renders real-time offer cards with countdown timers. - Postman / cURL API Flow: Customer places an order, Restaurant Owner accepts the order within the 2-minute deadline (triggering 3-round parallel dispatch), and the Delivery Agent accepts the offer with single-key prompt (
1).
In your terminal, launch the Python offer tracker (track_delivery_offers.py):
# Local backend (default: http://localhost:8080)
python3 scripts/track_delivery_offers.py --auto-available
# Or point to a deployed QuickBite backend URL (no direct DB access needed!)
python3 scripts/track_delivery_offers.py --base-url https://api.your-domain.com --auto-availableNote
- 100% REST API-Driven: Polls
GET /api/v1/delivery-agent/offers/activefor each logged-in agent — requires zero direct database connection (psqlis not needed). - Pre-configured with 6 verified delivery agents in
scripts/agents.json(aarav.sharma@example.com,vikram.singh@example.com,pooja.patel@example.com,mohammed.rizwan@example.com,sneha.mukherjee@example.com,rajesh.kumar@example.com, passwordPassword@123). - Automatically refreshes 15-minute JWTs and resolves
409 Conflict(session limits) by evicting only the single oldest session. - Sends
PUT /api/v1/delivery-agent/locationheartbeats every 35s to keep active agents alive in Redis GEO. - Queues multiple incoming offers in FIFO order so you can review each offer without missing others.
Leave this terminal running — it will alert you as soon as an offer is dispatched!
First, log in as the Customer (Customer Portal collection) and Restaurant Owner (Restaurant Owner Portal collection) in Postman via Auth & Session Management → Login & Token Refresh → Login with Email & Password.
Note
- Automatic Token & Session Capture: When you call Login with Email & Password or Refresh Access Token, the Postman post-response script automatically sets
access_token,refresh_token,challenge_token, andsession_idin your collection variables. - 15-Minute Access Token Expiry:
accessTokenexpires in 15 minutes. Whenever it expires, simply call the Refresh Access Token (POST /api/v1/auth/refresh-token) request provided in Postman to rotate and refresh your token automatically. - Login & Session Challenge Screenshots: Customer and Restaurant Owner login screenshots are omitted here for brevity — the complete login and
409 Conflict(session_limit_exceeded) device session challenge resolution flow is shown step-by-step with screenshots in Step 7 when logging in as the Delivery Agent.
- Endpoint:
POST http://localhost:8080/api/v1/auth/login - Body:
{ "email": "eshantsonune52@gmail.com", "password": "Password@123" }
- Endpoint:
POST http://localhost:8080/api/v1/auth/login - Body:
{ "email": "rakesh.agarwal@haldiramsnagpur.com", "password": "Password@123" }
In the Customer Portal collection, open Shopping Cart → Add Item to Cart (POST /api/v1/customer/cart/items) and add items to your cart as a customer:
Call Shopping Cart → Get Checkout Preview (GET /api/v1/customer/cart/checkout-preview?addressId={{address_id}}&tipAmount={{tip_amount}}). The Postman test script automatically saves priceBreakdown.totalAmount into the total_order_amount collection variable so you don't need to copy-paste the final price manually:
Important
Make sure address_id and tip_amount are configured in your Customer Portal collection/environment variables before placing an order.
You can place an order using either Option A (Cash on Delivery) for instant placement, or Option B (Online Payment via Razorpay) to test the full gateway checkout and signature verification lifecycle.
Open Order Placement & Tracking → Place Order from Cart (POST /api/v1/customer/orders) with "paymentMethod": "COD". For COD, the order immediately transitions to PLACED:
-
Place Online Order (
UPIorNET_BANKING): InPlace Order from Cart, changepaymentMethodfromCODtoUPIorNET_BANKINGand send the request. The order is created inAWAITING_PAYMENTstatus and returns a Razorpay gateway order payload: -
Copy Placed Order Response JSON: Copy the entire JSON response returned from placing the online order:
-
Paste JSON into Local Checkout Page: Open
http://localhost:8080/checkout.htmlin your browser, paste the copied JSON response data, and click Next to review the payment details: -
Preview Payment Details & Launch Razorpay: Review the parsed order and payment breakdown on the preview screen, then click Pay Now with Razorpay:
-
Select Netbanking in Razorpay Checkout Popup: In the Razorpay checkout popup, enter the required contact information, select Netbanking, and choose any bank for the demo (note: UPI will not work in the local demo popup):
-
Simulate Payment Success: On the Razorpay mock bank verification page, click the Success button:
-
Razorpay Payment Transition: Wait a moment while Razorpay completes the payment transition callback:
-
Copy Online Payment Result JSON: Once payment succeeds,
checkout.htmldisplays the cryptographic payment result (gatewayOrderId,gatewayPaymentId,gatewaySignature). Copy the JSON data: -
Verify Online Payment in Postman: Open
Online Payment Verification → Verify Online Payment Signature(POST /api/v1/customer/payments/verify) in Postman, paste the payment result JSON into the request body, and send it to verify the payment and transition the order toPLACED:
Once the order is in PLACED status (either via COD or verified online payment), switch to the Restaurant Owner Portal collection (Kitchen Order Fulfillment → Accept Incoming Order, POST /api/v1/restaurant-owner/orders/{{order_id}}/accept?restaurantId={{restaurant_id}}) and accept the incoming order within the 2-minute acceptance deadline. This transitions the order to ACCEPTED and triggers asynchronous radial delivery dispatch:
Next, call Kitchen Order Fulfillment → Mark Order as Preparing (POST /api/v1/restaurant-owner/orders/{{order_id}}/mark-preparing?restaurantId={{restaurant_id}}) to transition the order to PREPARING:
Switch to the terminal running track_delivery_offers.py. The live delivery offer card appears automatically for the nearest logged-in delivery agent with full allotment, restaurant pickup, customer drop-off, distance, and payout details:
Enter 1 in the terminal prompt to accept the incoming delivery offer, and copy the email address of the assigned delivery agent shown in the terminal output:
Back in the Restaurant Owner Portal collection, call Kitchen Order Fulfillment → Mark Order Ready for Pickup (POST /api/v1/restaurant-owner/orders/{{order_id}}/mark-ready?restaurantId={{restaurant_id}}) to advance the order to READY_FOR_PICKUP:
Now switch to the Delivery Agent Portal collection in Postman to log in as the assigned courier, resolve a concurrent device session challenge (409 Conflict) if needed, and complete the pickup and delivery.
Open Auth & Session Management → Login & Token Refresh → Login with Email & Password, paste the assigned delivery agent's email address (the password remains Password@123), and send the request.
- If the agent has reached the maximum concurrent device session limit, the server returns
409 Conflictwith"error": "session_limit_exceeded". - The Postman test script automatically captures
challengeTokeninto thechallenge_tokencollection variable — simply proceed to 7.2 below to evict an old session and claim the login:
Open Auth & Session Management → Device Session Management → List Active Device Sessions (GET /api/v1/auth/sessions, which automatically uses Bearer {{challenge_token}}). Send the request and copy the first sessionId from the response list:
Open Device Session Management → Revoke Device Session (DELETE /api/v1/auth/sessions/{{session_id}}), paste the copied sessionId into the URL/variable as shown, and send the request (204 No Content) to free a session slot:
Open Device Session Management → Claim Challenged Session (POST /api/v1/auth/claim-session) and send the request. Your new device session is now active and the Postman test script automatically saves your fresh access_token and refresh_token into the collection variables:
Open the Delivery Agent Portal collection variables tab and paste the active order_id:
Call Order Dispatch & Last-Mile Delivery → Mark Order Picked Up (Out for Delivery) (POST /api/v1/delivery-agent/orders/{{order_id}}/pickup). This confirms restaurant package handoff and transitions the order to OUT_FOR_DELIVERY:
Finally, call Order Dispatch & Last-Mile Delivery → Mark Order Delivered (POST /api/v1/delivery-agent/orders/{{order_id}}/delivered) to confirm customer handoff. The order is now in its terminal DELIVERED state! 🎉
For in-depth architectural guides and developer specifications, consult the docs/ directory:
- Documentation Hub (
docs/README.md) — Complete documentation index. - System Architecture & Domain Design (
docs/architecture.md) — Event choreography, state machines, and concurrency patterns. - Order & Cart Lifecycle Guide (
docs/order-process.md) — End-to-end cart, pricing chain, price-drift check, Redisson delayed queues, and fulfillment flow. - REST API Reference & Security Matrix (
docs/api-guide.md) — Comprehensive guide to all 35+ REST controllers. - Dispatch Engine & Geospatial Routing (
docs/dispatch-and-routing.md) — Concentric dispatch, Redis GEO, and OSRM routing. - Payments & Automated Reconciliation (
docs/payments-and-reconciliation.md) — Razorpay integration, webhooks, and multi-attempt reconciliation. - Installation & Environment Setup (
docs/installation.md) — Detailed deployment and setup instructions. - Client JWT & Session Integration Guide (
docs/jwt.md) — Guide for frontend and mobile client authentication. - Authentication & Session Architecture (
docs/authentication.md) — Deep dive into dual tokens and family rotation.
- Core Architecture & Framework Setup (Spring Boot 4.1.0 on Java 25, Flyway V1–V35, Envers Auditing)
- Dual-JWT & Stateful Session Engine (Self-issued RSA256, Refresh Token Family Rotation, 409 Session Challenge)
- PostgreSQL & Spatial Foundation (PostGIS 18.1, JTS geometries, GIST indexing, spatial
/nearbysearch with multi-criteria filtering) - Redis & Distributed Concurrency (Redisson locks for orders/payments/dispatch, Redis GEO real-time driver tracking)
- Kafka Event-Driven Messaging (7 aggregate event streams, Jackson inferred polymorphic conversion,
.DLTerror handling) - Multi-Step Onboarding & Allotment (Restaurant, Driver, and Vehicle pipelines with Workload-Balanced Admin Allotment)
- Cart & Order Management (Single-restaurant auto-clearing carts, dynamic fee engine, 2-minute kitchen acceptance deadline, delivered earnings analytics, actor-attributed status audit trail)
- Multi-Round Dispatch Subsystem (3km/6km/10km expanding rounds, 45s driver offer timeout, fair assignment)
- Payment Processing & Webhooks (Razorpay gateway, COD/Online strategies, HMAC-SHA256 verification, auto-reconciliation)
- Multi-Tier Routing Gateway (Local native OSRM on port 5001 + Mapbox fallback + Haversine fallback)
- AWS S3 File Storage (Presigned PUT URLs for direct client uploads with 10-minute expiry)
- Reviews & Automatic Ratings (Kafka-driven restaurant rating and review count recalculation)
- Comprehensive Test Suite (102 test classes / 574 tests across all domains covering unit, controller, and integration flows)
- WebSocket / SSE live order tracking updates for customer frontend
- Push notification gateway integration (Firebase Cloud Messaging / Apple APNs)
- Multi-region MSK Kafka deployment configuration



























