Skip to content

Timeline and Dependencies

This document maps dependencies between epics and tasks across all Integration Architecture projects. Use this to identify the critical path, parallel work opportunities, and blocking relationships.



Epic-to-Epic Dependencies

Critical Path (must be built in order)

Gateway Foundation

        ├──► Authentication System
        │         │
        │         ├──► Rate Limiting and Quotas
        │         │
        │         └──► Error Handling and Resilience

        ├──► Containerization
        │         │
        │         └──► CI/CD Pipeline

        └──► REST API Design

                  ├──► API Documentation

                  └──► Inbound/Outbound Webhooks

                            └──► Observability Pipeline

                                      └──► Security Hardening

Dependency Matrix

EpicDepends OnBlocked ByEnables
API Gateway Core
Gateway FoundationAuth, Error Handling, Rate Limiting
Authentication SystemGateway FoundationRate Limiting, Connectors
Error Handling and ResilienceGateway FoundationConnectors, Webhooks
Rate Limiting and QuotasAuthentication SystemProduction readiness
API Surface
REST API DesignGateway FoundationSalesforce custom fieldsAPI Documentation
API DocumentationREST API DesignConsumer integration
Webhook Infrastructure
Inbound Webhook ProcessingGateway Foundation, AuthEvent processing
Outbound Webhook DeliveryGateway Foundation, AuthConsumer notifications
Observability and Security
Observability PipelineGateway FoundationAlerting, Health checks
Security HardeningAuth, Rate LimitingProduction readiness
Deployment and Operations
ContainerizationGateway FoundationCI/CD Pipeline
CI/CD PipelineContainerizationProduction deployment
Salesforce Connector Production ReadinessAuth, Error Handling, Rate LimitingSalesforce custom fieldsFull API functionality

Task-Level Dependencies Within Epics

Gateway Foundation

TaskDepends OnNotes
Build stateless request routingStart here
Implement connector abstractionRouting
Build request flow pipeline (9 steps)Connector abstraction
Implement Salesforce connectorConnector abstraction
Add partner/payment connector stubsConnector abstractionCan parallel with Salesforce

Authentication System

TaskDepends OnNotes
Implement inbound consumer auth (API key)Gateway Foundation
Build per-consumer credential managementInbound auth
Implement key rotation with grace windowCredential management
Implement outbound vendor auth (JWT Bearer)Gateway FoundationParallel with inbound
Build token refresh workerOutbound auth
Implement JWT token cache in RedisToken refresh
Store credentials in DopplerCredential management
Add mTLS optionInbound authCan parallel with key rotation

Error Handling and Resilience

TaskDepends OnNotes
Implement error categorizationGateway Foundation
Build bounded retry strategyError categorization
Implement idempotency key requirementRedis setup
Build circuit breakerError categorization
Implement uniform error response shapeError categorizationParallel with circuit breaker

Rate Limiting and Quotas

TaskDepends OnNotes
Implement per-consumer inbound limitsAuthentication
Build per-resource outbound quota trackingConnectors
Implement Salesforce per-user connection poolQuota tracking
Build pre-flight budget checkQuota tracking
Implement backpressure with 429 + Retry-AfterInbound limits

REST API Design and Implementation

TaskDepends OnNotes
Implement versioned REST API (/v1)Gateway Foundation
Build Members endpointREST API, Salesforce connectorBlocked on SF custom fields
Build Quotes CRUDREST API, Salesforce connectorBlocked on SF custom fields
Build Bookings CRUDREST API, Salesforce connectorBlocked on SF custom fields
Implement health endpointREST APICan parallel with others
Implement cursor-based paginationREST API

Inbound Webhook Processing

TaskDepends OnNotes
Implement webhook termination pointGateway Foundation, Auth
Build signature verificationAuth
Implement deduplication via event IDRedis
Build async processing pipelineQueue setup
Return 202 AcceptedPipeline

Outbound Webhook Delivery

TaskDepends OnNotes
Implement event subscription modelGateway Foundation
Build vendor-specific subscription handlingConnectors
Normalize event formatSubscription model
Implement at-least-once deliveryNormalized format
Build idempotency keys on deliveryDelivery

Observability Pipeline

TaskDepends OnNotes
Implement OpenTelemetry tracingGateway Foundation
Build structured JSON loggingTracing
Implement 8 defined metricsTracing, Logging
Build alert rulesMetrics
Implement health endpoint with external checkMetrics

Security Hardening

TaskDepends OnNotes
Implement PII field-level scrubbingLogging
Build audit log of PII accessScrubbing
Enforce TLS 1.2 minimumCan start early
Implement webhook replay protectionWebhooks
Build input validation against JSON SchemaGateway Foundation

Containerization

TaskDepends OnNotes
Build multi-stage DockerfileGateway Foundation
Implement health/readiness checksHealth endpoint
Configure environment-based secretsDoppler

CI/CD Pipeline

TaskDepends OnNotes
Build lint and unit test stagesCan start early
Build integration test stageSF sandbox
Implement container build and pushDockerfile
Build staging deploymentContainer build
Implement manual approval gate for prodStaging deployment

Salesforce Connector Production Readiness

TaskDepends OnNotes
Complete endpoints blocked on SF custom fieldsAuth, REST APIExternal blocker
Move JWT private key to DopplerDoppler
Implement per-environment credentialsCredential management
Build rate limiting and quota trackingRate Limiting epic

Parallel Work Opportunities

Wave 1 (can start immediately)

  • Gateway Foundation (routing, connectors, pipeline)
  • Containerization (Dockerfile)
  • CI/CD Pipeline (lint, unit tests)

Wave 2 (after Gateway Foundation)

  • Authentication System (inbound + outbound)
  • Error Handling and Resilience
  • REST API Design
  • Observability Pipeline

Wave 3 (after Wave 2)

  • Rate Limiting and Quotas (needs Auth)
  • API Documentation (needs REST API)
  • Inbound/Outbound Webhooks (needs Auth)
  • Security Hardening (needs Auth + Logging)

Wave 4 (after Wave 3)

  • Salesforce Connector Production Readiness (needs Auth + Rate Limiting)
  • Integration Testing (needs all above)

Wave 5 (after Wave 4)

  • Production Deployment

Critical Path Summary

The minimum viable path to a production-ready API Gateway:

1. Gateway Foundation (routing, connectors, pipeline)
2. Authentication System (API key + JWT Bearer)
3. Error Handling and Resilience (retry, circuit breaker)
4. Containerization (Dockerfile)
5. CI/CD Pipeline (build, test, deploy)
6. Observability Pipeline (tracing, logging, metrics)
7. Rate Limiting and Quotas (production requirement)
8. Production Deployment

Estimated critical path: ~8-10 weeks if fully staffed and unblocked.


Risk Areas

RiskImpactMitigation
Salesforce custom fields block endpointsHighStart non-SF endpoints first, escalate SF field creation
Redis is critical dependencyHighProvision Redis early, use managed service
Doppler integration delayedHighUse env vars for dev/staging, plan migration
On-disk JWT key in spikeHighMove to Doppler before production
Rate limiting not in spikeMediumBuild rate limiting early in Wave 2
Partner API integration delaysMediumUse connector stubs, integrate incrementally

Marchay Platform Documentation