Skip to content

Learning Paths

This guide is designed to be read in multiple ways depending on your current needs and role. Choose the path that best fits your objective.

Path Selection

Role Goal Recommended Starting Point
Developer Build and integrate features Developer Path
Operator Manage and monitor at scale Operator Path
Troubleshooter Resolve production issues Troubleshooter Path

Developer Path

The Developer path focuses on implementation details, SDK usage, and core platform concepts like Identity and Access Tokens.

graph TD
    A[Platform Overview] --> B[Identity & Tokens]
    B --> C[Choose SDK Guide]
    C --> D[Implementation Recipes]
    D --> E[Security Best Practices]

Recommended Reading Order:

  1. Platform: Core Concepts
  2. Platform: Authentication
  3. SDK Guides (Choose your preferred language)
  4. Best Practices: Security

Operator Path

The Operator path is designed for SREs and DevOps professionals who manage the ACS resources and ensure service reliability.

graph TD
    A[Platform Deep-Dive] --> B[Resource Management]
    B --> C[Monitoring & Alerting]
    C --> D[Best Practices: Scalability]
    D --> E[Operations: Quotas]

Recommended Reading Order:

  1. Platform: How ACS Works
  2. Operations: Monitoring
  3. Best Practices: Scaling
  4. Reference: Platform Limits

Troubleshooter Path

The Troubleshooter path is for rapid response. It starts with diagnostic entry points and moves toward systematic playbooks.

graph TD
    A[Troubleshooting Methodology] --> B[Diagnostic Decision Tree]
    B --> C[Log Analysis with KQL]
    C --> D[Service Playbooks]
    D --> E[Known Issues & Ref]

Recommended Reading Order:

  1. Troubleshooting: Methodology
  2. Troubleshooting: KQL for ACS
  3. Troubleshooting: Playbooks
  4. Reference: CLI Cheatsheet

See Also

Sources