Search for the Right Document
-
Planning and Strategy
-
Requirements
-
- Customer Feedback Report
- Capacity Planning Report
- Stakeholder Input Record Example
- List of Customer Journeys
- Reverse Engineering: Legacy Inventory Management System
- Task Analysis: Customer Support Ticketing System
- Requirements Workshop: Employee Onboarding System
- Mind Mapping Session: Mobile Travel Planning App
- SWOT Analysis: New Food Delivery App
- Storyboarding Session: Mobile Health & Fitness App
- User Story Mapping Session: Online Grocery Shopping Platform
- Focus Group: Requirements Gathering for Fitness Tracking App
- Prototyping Session Example: E-Commerce Website
- Document Analysis Example: Hospital Management System Requirements
- Observation Session: Warehouse Operations
- Survey: E-Learning Platform Requirements
- Workshop Session Example: Requirements Gathering for Mobile Banking App
- Interview Session Example: Requirements Gathering for CRM System
- Event Storming Session: Retail Order Management System
- Generate Requirements from Meeting Transcripts
- Requirements Definition Process Example
- ISO/IEC/IEEE 29148 Systems and Software Requirements Specification (SRS) Example Template
- Show all articles ( 7 ) Collapse Articles
-
- Customer Requirement Document (CRD)
- Customer Journey Map
- Internal Stakeholder Requirement Document (ISRD)
- Internal System Use Case Example: CI/CD System
- User Stories & Acceptance Criteria
- Technical Specification Document Example
- BDD Scenarios Example for User Login
- Non-Functional Requirements Example
- Functional Requirements Specification Example
- Use Case Example: User Login
-
-
Communication
-
Design
- Functional Specification for Inventory Management Workload
- Technical Specification for Inventory Management System
-
- Overview of Design Diagrams
- High-Level System Diagram Standards
- User-Flow Diagram Standards
- System Flow Diagram Standards
- Data-Flow Diagram (DFD) Standards
- Sequence Diagram Standards
- State Diagram Standards
- Flowchart Standards
- Component Diagram Standards
- Network Diagram Standards
- Deployment Diagram Standards
- Entity-Relationship Diagram (ERD) Standards
- Block Diagram Standards
-
Operations
-
-
- Creating a Visualization Dashboard Guide
- Business Outcome Metrics Dashboard Guide
- Trace Analysis Dashboard
- Dependency Health Dashboard
- Guidelines for Creating a Telemetry Dashboard
- Guidelines for Creating a User Behavior Dashboard
- Improvement Tracking Dashboard
- Customer Status Page Overview
- Executive Summary Dashboard Overview
- Operations KPI Dashboard Example
- Stakeholder-Specific Dashboard Example
- Business Metrics Dashboard Example
- System Health Dashboard Example
- Guide for Creating a Dependency Map
-
-
-
- Event Management Policy Example
- Incident Management Policy
- Problem Management Policy
- Example Training Materials for Escalation
- Runbook Example: Incident Management with Escalation Paths
- Escalation Path Document Example
- Incident Report Example: Failed Deployment Investigation
- Incident Playbook Example: Investigating Failed Deployments
- Contingency Plan for Service Disruptions
-
-
-
Testing
-
Development
< All Topics
Print
Scheduled Jobs Architecture Diagram Example
PostedMarch 29, 2025
UpdatedMarch 29, 2025
ByKevin McCaffrey
ID: SUS_SUS3_1_scheduled-jobs-architecture-diagram
Code: SUS3_1
This example highlights a scheduled and asynchronous jobs pattern to optimize resource utilization, reduce idle capacity, and support sustainability objectives. By scheduling jobs to run only when needed and decoupling components using an event-driven queue, you can reduce unnecessary resource consumption and lower your carbon footprint.
The architecture includes:
- Scheduled Event Source: A cloud scheduling service (e.g., Amazon EventBridge) triggers jobs at specific intervals.
- Queue or Topic: A message queue (e.g., Amazon SQS) or topic (e.g., Amazon SNS) receives tasks from the scheduled event, preventing resource bottlenecks.
- Worker or Serverless Consumers: Lambda functions or containerized tasks automatically scale based on queue depth, ensuring efficient resource use.
- Data Storage: A lightweight, managed data store (e.g., Amazon DynamoDB) or object storage (e.g., Amazon S3) holds processed results.
- Monitoring and Logging: Cloud-native logging and metrics (e.g., Amazon CloudWatch) provide insight into performance and resource usage.
This design helps maintain a smaller operational footprint by running compute resources only when jobs are in queue, ultimately supporting sustainability goals through efficient use of computing resources.
Table of Contents