SonarQube Enterprise Architecture | Deploying SonarQube at Scale
summary
Architecture options for running SonarQube at enterprise scale include self-hosted vs SaaS with concrete tradeoffs: self-hosting requires VMs or containers, a database team, DR and upgrade processes and measurable SLAs, while cloud gives automatic updates and reduces ops work; supports Docker, ECS or Kubernetes (EKS AKS GKE), scanners in CI (GitHub Actions, Azure Pipelines, Jenkins), IDE extensions, MCP server for AI agents, and repo integrations (GitHub Bitbucket GitLab Azure DevOps). Onboarding claims a scan first project in 10 minutes and cloud compliance includes ISO 27001 and SOC 2.
AI-written summary · about
chapters (13)
- 0:00Introduction
- 0:49SonarQube’s Role in Enterprise Software Delivery
- 2:50The First Big Decision: Deployment Model
- 4:47Self-Hosted on VMs, Containers, and Kubernetes
- 6:24Upgrades, SLAs, and Database Considerations
- 8:08Why Teams Choose SonarQube Cloud
- 9:48Total Cost of Ownership and Faster Onboarding
- 10:52Repository Onboarding Options
- 11:32Authentication and SSO Options
- 12:08CI/CD Pipeline Integration
- 13:12Developer Workflow and IDE Support
- 13:57MCP Server and AI-Assisted Development
- 14:20Measuring Success Against Organizational Goals
related talks
47mRollercoaster of Security Automation
28mScale Your DevOps Initiative Beyond Its Awkward Teenage Years
22mBuilding SSDLC in an Enterprise Environment
40mScaling Startup for Success: Building modern Architectures and Developer Acceleration
27mArchitect CI/CD on Enterprise level
31m20k Leagues Under Platform Engineering
31mSaaS release engineering: balancing speed, safety & scale
44mBuilding and scaling cloud-native intelligent applications on Azure