8000 GitHub - razi-ahmad/solution-design · GitHub
[go: up one dir, main page]

Skip to content

About

No description, website, or topics provided.

Resources

Stars

0 stars

Watchers

0 watching

Forks

Latest commit

 

History

2 Commits

Folders and files

NameName
Last commit message
Last commit date
 
 
 
 
 
 
 
 
 
 

Repository files navigation

Self Service Portal

High Level Components

  1. Frontend: (Staticc Web Assets)

    • Built with React.js
    • Hosted on AWS S3 and served via AWS CloudFront for low latency and high availability.
    • Authentication handled via AWS Cognito.
    • Provides a user-friendly interface for users to interact with the portal.
  2. Backend: (API Layer)

    • Amazon API Gateway -> AWS Lambda functions which is implementing the operations such as register event, view events, subscribe etc.
  3. Database: (Data Storage)

    • Amazon DynamoDB for storing event definitions, schema, versioning etc 4 Subscription Notification:
    • Send notification to the broker's control plane to update routing rules.

Self Service Portal

Event Broker

High Level Components

  1. Ingestion Layer:

    • HTTPS Ingestion: It can put message in SQS Ingestion Queue
    • SQS Ingestion: Producers can send directly to the SQS Ingestion Queue
    • SNS Ingestion: Producers publish to SNS Topic then SNS subscription to the SQS Ingestion Queue
    • Event Bridge Ingestion: Producers can send events to Event Bridge which has a rule to route to the SQS Ingestion Queue
  2. Validation Pipeline:

    • SQS Ingestion Queue will forward messages to the Lambda Validation Function
    • Default Batch Size can be 10 and can be configured based on the use case
    • Fetch Schema from DynamoDb and validate payload against the JSON Schema
    • Enrich the metadata such as timestamp, trace id etc
    • If validation fails, send the message to the DLQ
    • If validation is successful, send the message to the Event Bridge Central Bus
  3. Event Routing:

    • Event Bridge Central Bus will have multiple rules to route the events to different targets based on the event pattern
    • Targets can be SQS Queues, SNS Topics, Lambda Functions, HTTP Endpoints etc
    • Each target can have its own DLQ to handle failures Event Broker
  4. Monitoring and Logging:

    • Use AWS CloudWatch for monitoring the metrics such as number of events ingested, validation failures, routing failures etc
    • Use AWS CloudWatch Logs for logging the validation errors, routing errors etc
  5. Security:

    • Use AWS IAM for fine-grained access control to the resources
    • Use AWS KMS for encrypting the data at rest and in transit
  6. Scalability and High Availability:

    • All components are serverless and can scale automatically based on the load
    • Use multiple Availability Zones for high availability
  7. Cost Optimization:

    • Use AWS Lambda with provisioned concurrency for predictable workloads
    • Use S3 Intelligent-Tiering for storing static web assets
    • Use DynamoDB On-Demand for unpredictable workloads

About

No description, website, or topics provided.

Resources

Stars

0 stars

Watchers

0 watching

Forks

Releases

Packages

Contributors

Languages

0