Book Image

The Software Developer's Guide to Linux

By : David Cohen, Christian Sturm
5 (2)
Book Image

The Software Developer's Guide to Linux

5 (2)
By: David Cohen, Christian Sturm

Overview of this book

Developers are always looking to raise their game to the next level, yet most are completely lost when it comes to the Linux command line. This book is the bridge that will take you to the next level in your software development career. Most of the skills in the book can be immediately put to work to make you a more efficient developer. It’s written specifically for software engineers, not Linux system administrators, so each chapter will equip you with just enough theory to understand what you’re doing before diving into practical commands that you can use in your day-to-day work as a software developer. As you work through the book, you’ll quickly absorb the basics of how Linux works while you get comfortable moving around the command line. Once you’ve got the core skills, you’ll see how to apply them in different contexts that you’ll come across as a software developer: building and working with Docker images, automating boring build tasks with shell scripts, and troubleshooting issues in production environments. By the end of the book, you’ll be able to use Linux and the command line comfortably and apply your newfound skills in your day-to-day work to save time, troubleshoot issues, and be the command-line wizard that your team turns to.
Table of Contents (20 chapters)
18
Other Books You May Enjoy
19
Index

How do we do Ops with containers?

Although this is not a book for system administrators or site reliability engineers, you should know the basic context in which containers are generally run. The main idea is that containers are largely stateless “functions” that process inputs (web requests or HTTP messages from other services) and produce outputs (web responses, side effects, and logs streamed to STDOUT). In a well-run operations environment, containers can be thought of as an analog to Linux processes, or to functions in programming.

Containers are usually “scheduled” onto hosts by a third-party tooling layer such as Kubernetes, Nomad, and others. If containers are like processes, then these fill the role of the operating system scheduler (the whole thing is a distributed system instead of a single host).

Container output is usually captured by the same tooling and redirected to logging solutions such as Logstash, Graylog, and Datadog. Metrics...