golangbot

Principle of Least Privilege in Software Engineering means granting only the bare minimum permissions necessary for a process/module/user or any other entity to perform the required task. For example in Kubernetes, assigning only the necessary minimum privileges to a pod’s service account to perform it’s functions. If a Pod needs only read access to a specific config map in a namespace, then following the principle of least privilege means creating a role and rolebinding on that namespace with access to only that specific config map and not providing any other permissions.

Although Docker and container orchestrators like Kubernetes have solved the issues such as ensuring that a web service keeps running all the time, they are quite complicated to configure and maintain for small SAAS applications and side projects. For my own side projects such as https://sslnotify.com/, I use a systemd service to deploy my Go binary. This setup is very simple and it serves my critical needs such as ensuring that the web server is always running and also provides indexable logging using journald.