We have already seen in the previous chapters that Azure is full of opportunities in terms of services available to be consumed in our solutions. The objective is developing code that is functional to solution objectives, more than non-functional aspects.
We have also told you that using Azure makes developers aware of the non-dev aspect of their work, which is called operations. We have spoken about networking and application lifecycle management, service management, and backup. It is always good that a developer knows about operations. However, there is something that is mandatory for dev about ops: deployment.
In the previous chapters, we used different ops tools, such as the PowerShell environment and APIs, the classic portal and new portal, and management APIs, to instantiate services when deploying our solution.
As we embrace the initial invitation to use Azure services as much as we can, we finally reach a complex solution made of different projects...