Goodbye Shell, Hello Python!
Goodbye Shell, Hello Python!
I have finally made the decision to drop Shell and embrace Python. Why is this? Check out this blog post and discuss with me.
Join the DZone community and get the full member experience.Join For Free
Hortonworks Sandbox for HDP and HDF is your chance to get started on learning, developing, testing and trying out new features. Each download comes preconfigured with interactive tutorials, sample data and developments from the Apache community.
As an Ops/DevOps professional, I have many years of experience writing Shell scripts. You're probably in a similar situation, right? I deeply treasure my achievements with Shell. Yes, I still do, even now. But I have to make a decision to (finally!) drop Shell and embrace Python.
Why is that? Check out this blog post and discuss with me.
It’s really hard to reject the temptation of Shell. Shell is a very old and widely used language, but it’s far from modern programming languages. Poor error handling, weird syntax, no package mechanism to reuse the code — the list goes on and on…
- Unix PIPE philosophy makes Shell the default glue language. It integrates all kinds of (relatively) small tools, solving a bigger problem. So, if you check any popular online tutorials now, you will probably see Shell scripts somewhere.
- With Shell, it’s super easy to get your hands dirty and make progress. Each Shell command you have issued in the terminal is a reward. It makes you feel that you’re making constant progress. Hard to say no, isn’t?
- There's no extra wrapper layer. Let’s say you need to trigger some ElasticSearch actions by programming. You can either call the ElasticSearch management REST API directly by Shell or use the ElasticSearch Python SDK. If you choose Python and the script is not working, then what? It could be some bugs in Python SDK or the way you use Python SDK. No doubt people are in favor of Shell scripting sometimes.
Regardless of all benefits, my DevOps fellows, we have to look ahead and move on.
I will choose Python as the default for all unattended scripts that will run automatically. There is still some room for Shell, for example, to quickly wrap up some commands and execute them manually from the terminal.
First of all, it doesn’t necessarily need to be Python. It could be any modern programming languages you’re comfortable with like Ruby, Golang, etc.
- Reuse code and modules across projects. With years’ accumulation, I come up with a shell common library (GitHub). With this library, I can easily and quickly accomplish lots of DevOps tasks — for example, enforce pre-checks before deployment, run deployment and maintenance via Jenkins, etc. However, distributing the Shell scripts and upgrading them is quite a burden. With Python, I can easily pack up the logic as a pip package.
- It's super hard to make decent and reliable Shell scripts. Think you’re a Shell ninja? Run Shellcheck against your scripts. With the absence of error handling, your scripts can easily give you false positives. Consequently, it may incur serious damage or make troubleshooting difficult.
- Easy requirements may not be easily supported. For example, when you run the scripts, you want to see the output in both terminal and log files. With some research, you may finalize with the solution of the tee command. However, you will have to deal with weird bash issues like this one.
Now, my Python journey starts. What about yours?
Note: I will keep open source my DevOps Python scripts in GitHub.
Published at DZone with permission of Denny Zhang , DZone MVB. See the original article here.
Opinions expressed by DZone contributors are their own.