V
Back to VS /

Microservices Integration Framework Design

Integration Topology Flow

ONEBILL iPaaS CORE PLATFORM BOUNDARYPortal / API TriggerBusiness WorkflowsCPQ AppConfigure & PricePSA AppResource ManagementBilling & InvoicingSubscription SeatsOkta / Keycloak IDPIdentity & Access (OIDC)AWS API GatewayIngress Rate LimiterKAFKA EVENT BROKERProvisioning Service• Sequence Execution• Timeout Guard• Automatic Retry• State Management• Failure CompensationProvisioning TasksLocal Accounts SetupIntegration Service• Tenant & Partner Registry• Dynamic Config Store• Mapping & Conditions• Idempotency Checking• External Ref RegistrySchema RegistryCDM ValidationVault StoreSecret ManagementRedis CacheIdempotency StoreConnector EngineOutbound SDK WrapperTelemetry Engine• OpenTelemetry• Jaeger Traces• Audit Logger• Live ConsoleDLQ Recovery• Error Storage• Re-drive Handler• Payload Re-runs• Poison Msg DLQSalesforce TargetTenant B AccountZoho Sign TargetTenant A AccountSlack / Collab APIIncident Alert ChannelsAWS Lambda HandlerWebhook Event ParserAmazon SQS QueueIngress FIFO Buffer
💡 Hover over any microservice box to inspect its architectural purpose.
Microservice Pod
Active Pipeline Step
Event Flow Path
⚡

Kafka Queue Console

Topic: `provisioning-tasks` Partition Queue

2 pending events
ProvisionTenantSandbox (id: task_001) Status: Enqueued
SyncOktaDirectory (id: task_002) Status: Enqueued

Provisioning Framework Breakdown

CPQ, PSA, and Billing integration via Provisioning Service workflows.

Core Functional Scope

  • Unified Execution: The Provisioning Service controls all execution mechanics including sequence orchestration, timeouts, failure retries, and task state transitions.
  • Integration Intelligence: The Integration Service owns integration configurations, tenant-partner routing resolvers, data transformations, and target endpoint registries.
  • Canonical Data Model: Performs translation from internal transactional records into canonical formats, preventing points of coupling.
  • Thin Connector SDKs: External Connectors (Salesforce, Zoho) focus entirely on HTTP protocol mappings, authentication injection, and error classifications.

Standardized Task Interface & Results

IntegrationTask Interface

public interface IntegrationTask {
    TaskResult execute(
        IntegrationTaskContext context
    );
}

TaskResult Classifications

enum TaskResult {
    SUCCESS,
    RETRYABLE_FAILURE,  // E.g. Rate Limit, HTTP 503
    PERMANENT_FAILURE,  // E.g. Invalid payload schema
    WAIT,               // Waiting for webhook feedback
    SKIP                // Idempotent duplicate check match
}