New pattern: apigw-lambda-durable-tenant-isolation-callback-terraform#3169
Open
Anandoo7 wants to merge 1 commit into
Open
New pattern: apigw-lambda-durable-tenant-isolation-callback-terraform#3169Anandoo7 wants to merge 1 commit into
Anandoo7 wants to merge 1 commit into
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Issue #, if available:
Description of changes:
New Serverless Pattern
Pattern name: apigw-lambda-durable-tenant-isolation-callback-terraform
Pattern description:
SaaS applications that process tenant requests often need to pause a workflow and wait for an external system to confirm before completing a payment gateway returning a charge result, a compliance system issuing a decision, or a human approver acting on a request. During this wait, the first processing step has already validated the request and cached tenant-specific data (configuration, credentials, intermediate results) in the execution environment's memory.
This pattern uses Lambda durable functions to suspend the workflow at zero compute cost and resume from a checkpoint when the external confirmation arrives. It uses Lambda tenant isolation mode to ensure the suspended execution environment including all cached in-memory state from the first step is never reassigned to another tenant during the wait period. API Gateway provides the HTTP interface for starting workflows and receiving callbacks.
Without durable execution, the function cannot suspend across the wait boundary, forcing you to externalize all state to a database and build a separate resumption mechanism. Without tenant isolation, a suspended environment's cached data could be exposed to a different tenant's invocation during the wait. Both capabilities together enable multi-tenant workflows that pause indefinitely for external input while keeping tenant state private and avoiding re-execution of completed work.
Services: Amazon API Gateway, AWS Lambda (Durable Functions + Tenant Isolation)
Framework: Terraform
Language: Node.js
Testing:
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.