As technical lead or architect, you want to deliver features frequently. You do not worry about quickly deploying a bug fix for fearing a rollback. Unfortunately, getting started with CI/CD and DevOps can be daunting. There are a lot of tools and services to choose from. The landscape changes continuously, and it is easy to spend a lot of time on configuring and maintaining a toolchain. We want to tell you what is great about having Azure DevOps as our only tool for the entire delivery chain but also about the cheats and workarounds that we had to take.
We started a new development team in our midsize financial service organization (100 employees). We had a greenfield opportunity at a small firm living with a Microsoft and Windows legacy. We went all in on Microsoft Visual Studio Team Service, now rebranded Azure DevOps, and we develop serverless applications in Azure. We deploy with a few clicks: we'll show you a demo! Having a single tool saves us from integration hassle, and having it in the cloud removes responsibility but does come with downtime. Yet, overall Azure DevOps is a simple and cheap way for small teams to deliver quickly.
We have not only achieved full automation of builds and deploys for our new serverless apps, but also we have begun replicating our success to delivery of legacy applications. We take one app from dev and build on a single developer box to continuous integration upon git push. This approach enabled releasing changes in smaller batches to reduce risk. Learn from our experience to find your own strategy to gradually speed up your development process.
See the slides.Watch the video.
