Academy / Week 2 / Integrations System Overview & DOV / Integrations System Overview — 40+ Repos and All Services

Integrations System Overview — 40+ Repos and All Services

Lesson 11.1 ⏱ ~10 min Week 2

💡 Why This Matters

After two weeks of deep dives into individual services, this session zooms out to show you the full map. Knowing all 40+ repos and how they relate to each other is essential for navigating the codebase and understanding where your work fits in the larger system.

🎯 What You'll Learn

  • The full scope of Integrations-owned repositories (~40-44 active repos)
  • The two main working areas: SyncApp integrations vs core infrastructure services
  • Key UI tools the Integrations team owns and maintains
  • How all services discussed in Weeks 1 and 2 fit into the broader map
  • Repos where cross-file changes are required when updating system-wide configurations

Watch Video

Open in Google Drive 💡 Open in Drive for AI-powered transcript search and summaries

📋 Lesson Summary

The Integrations team manages roughly 40-44 active repositories. At the edges are the SyncApp integrations — per-PMS adapters written inside the SyncApp repo. The core infrastructure includes: SyncApp API (ingress proxy to Data Service), sync-app-support (provisioning automation), sync-app-authentication (data source management), sync-app-writebacks (write-back routing), SyncApp Settings API (configuration store), SyncApp Reporting Service (health monitoring), SyncApp Manager (WebSocket hub), and ICPA (rate limiting proxy). UI tools include WAM and various internal dashboards. Some changes (like adding a new PMS) require updating multiple repos simultaneously.

🏷 Key Concepts

40+ Integrations ReposSyncApp Integrations (Per-PMS Adapters)Core Infrastructure ServicesUI ToolsCross-Repo ChangesIntegrations Ecosystem Map

Key Takeaways

01The Integrations team owns a large surface area — 40+ repos means you'll frequently work across multiple codebases
02SyncApp integrations (per-PMS adapters) are one area; the supporting infrastructure services are another
03Some changes touch many repos simultaneously — always check if your ticket requires cross-repo updates
04This system overview session is worth re-watching after 3 months — things will make more sense once you've worked in the codebase