LevT
Platinum Member | Редактировать | Профиль | Сообщение | Цитировать | Сообщить модератору
Scripting at Scale
We’ve always felt that one of PowerShell’s greatest strengths was that if you could do something with one thing, be it a file, event log, computer or user account, you could do it for 10, 100 or 1000. In most cases, your PowerShell code would be essentially the same. This notion should also be influencing the way you do your work as an IT Pro.
For the longest time we usually approached our work on a singular basis. Say you had to check free disk space on 10 servers. In the last century, you’d go through your list one at a time and get the data you needed. But today, you should be thinking about managing at scale. Don’t think about getting disk space for 1 server at a time, think about how to do it for all 10 at the same time. Don’t check individual event logs on 100 servers, check them all at once. Once you start looking at your work from this perspective, you’ll realize you need to change your tool set or how you are using it. Fortunately, PowerShell makes it relatively easy to take this approach.
However, even with all of that we’re also going to offer up this potentially heresy, “PowerShell isn’t always the answer.” If you need to manage 10,000 servers in near real-time, PowerShell is probably not going to be the best tool. We’re not saying it won’t work, but the scripting effort may be beyond your abilities or performance won’t be what you need. PowerShell is always going have overhead, which is not necessarily a bad thing. That “overhead” makes it easy to find and use well-defined commands and parameters in a meaningful pipelined expression. We want you to realize that at some point you may need to move beyond PowerShell to compiled C# applications or full-blown software management solutions.
|
Всего записей: 17167 | Зарегистр. 14-10-2001 | Отправлено: 10:19 09-09-2017 | Исправлено: LevT, 12:22 09-09-2017 |
|
