In this post, I’m going to make the PowerShell acolytes angry (not hard) by explaining why they are too slow, and ARM/JSON is they best way to deploy things in Azure.
The PowerShell Experience
Let’s imagine that you & your significant other go into a restaurant, and let’s say you order a steak and your other wants to order something else. How does the ordering process go? Is it something like this .. let’s start with your order:
- Customer: Waiter!
- <Wait 1 minute>
- Waiter: What would you like sir?
- Customer: Could you ask the chef to go to the fridge?
- <Wait while the chef is asked to go to the fridge>
- Waiter: Yes?
- Customer: Would you ask the chef to open the fridge?
- <Wait while the chef opens the fridge>
- Waiter: Yes?
- Customer: Would you ask the chef to take a steak out of the fridge?
- <Wait while the chef takes a steak out of fridge>
- Waiter: Yes?
- Customer: Please ask the check to put a pan on the cooker.
- <Wait while the chef puts a pan on the cooker>
- Waiter: Yes?
You see what’s going on here? Meanwhile your significant other is getting no love from the restaurant. Ouch!
With PowerShell you describe the deployment process, one step at a time, connecting each and every dot. The deployment is serialized, with no parallelism unless you use PowerShell features to run parallel jobs. The result isn’t much faster than you doing all the clicking for yourself.
The ARM Experience
I like to describe the ARM as a waiter, and the Azure resource providers as the kitchen cooks. How does the order go?
- Customer: Waiter, I would like a Salmon dish for my wife and steak for myself.
- Waiter: Yes, sir, in the meantime, would you like a drink?
That’s a bit better, right?
ARM or JSON templates describe the result, not the process. Once you submit the deployment, ARM divides up the job and orders the deployment based on your dependencies. That means that the deployment can be parallelized. If I need 100 web servers, all 100 will be deployed at once, not in some 1..100 loop, one at a time (or 5 at a time if you are clever).
Best of Both Worlds
For some of the training that I do at work, I deploy the training lab in Azure as follows:
- A PowerShell script that asks me how many attendees there are, and then it runs a glorified 2 line loop.
- The loop iterates through different subscriptions, adding a resource group and then doing an ARM deployment.
In other words, PowerShell automates my very fast ARM deployments.
PowerShell Still Required
PowerShell is still very useful for some fiddly deployment things that don’t have ARM options, or are once-offs and don’t have a GUI option. To be honest, I do use GUI for most of my once-offs because it is convenient and gets the end result faster than researching/tweaking/fixing PowerShell examples. When it comes to learning about settings and troubleshooting, PowerShell can be pretty awesome.
But PowerShell is much slower than ARM for deployments. Now let’s hear the screams of outraged PowerShellers!
Was This Post Interesting?
If you found this information useful, then imagine what 2 days of training might mean to you. I’m delivering a 2-day course in Amsterdam on April 19-20, teaching newbies and experienced Azure admins about Azure Infrastructure. There’ll be lots of in-depth information, covering the foundations, best practices, troubleshooting, and advanced configurations. You can learn more here.
