Skip to content

Azure Dev Spaces

kimschles edited this page Jul 31, 2018 · 1 revision

Debugging distributed applications with Azure Dev Spaces and AKS

Gabe Monroy, Microsoft Kubernetes Colorado, July 30, 2018

Imagine you are a new employee trying to fix a bug in a complex microservices application consisting of dozens of components, each with their own configuration and backing services. To get started, you must configure your local development environment so that it can mimic production including setting up your IDE, building tool chain, containerized service dependencies, a local Kubernetes environment, mocks for backing services, and more. With all the time involved setting up your development environment, fixing that first bug could take days. Or you could use Dev Spaces and AKS.

Development Process

  • Outer Loop: After you've commited and push code to a repo (CI/CD process)
    • This is a problem that is much better than 3 years ago
  • Inner Loop: a developer sits down to write code
    • A feature, a bug
    • Unit test locally
    • Once you start running integration tests, it gets harder because your data is remote

Idea: unit test locally, integration test remotely

  • Use a breakpoint with AZDS

Azure Dev Spaces (azds) Docs Blog: Introducing Dev Spaces for AKS

Clone this wiki locally