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 Checklist Example
PostedMarch 29, 2025
UpdatedMarch 29, 2025
ByKevin McCaffrey
ID: SUS_SUS3_1_scheduled-jobs-checklist
Code: SUS3_1
Optimizing software and architecture for asynchronous and scheduled jobs is vital for maximizing resource utilization and minimizing waste. By implementing efficient patterns such as queue-driven systems, organizations can ensure their deployed resources are utilized consistently, resulting in lower carbon footprints and improved resource management.
Checklist
- Determine the Scheduling Interval: Align job frequency with actual demand. Avoid overly frequent executions that lead to resource waste, and ensure the schedule does not hamper user experience.
- Choose Asynchronous Patterns: Employ serverless services, event-driven architectures, or containers that can spin up on demand and scale down automatically.
- Utilize Queue-Driven Triggers: Use messaging or queueing services to trigger background tasks. This approach helps distribute workload evenly, minimizing idle time.
- Right-Size Resources: Monitor and adjust compute and memory allocations to prevent over-provisioning. Consider using resource scheduling that coordinates with off-peak times for carbon-efficient usage.
- Implement Observability: Instrument logging and metrics to measure efficiency. Track energy usage, carbon emissions, and resource costs for informed decisions.
- Automate Cleanup and Shutdown: Ensure that resources not in use are released or shut down to reduce energy consumption.
- Review and Iterate: Regularly assess scheduling configurations and adapt based on changes in usage patterns or business requirements.
By following these steps, development teams can maintain an optimized architecture for scheduled jobs, contributing to an overall more sustainable and resource-efficient environment.
Table of Contents