Bridgecrew, the company that sells a commercial version of the free checkov Infrastructure as code security scanner, has published this interesting "be afraid!" report about all the vulnerabilities they have detected in public terraform code. It's worth skimming.
Tuesday, July 28, 2020
Design Docs
Malte Ubl (inventor of accelerated mobile pages -- AMP) at Google published the guidelines he uses at Google for design documents. It's interesting because of the expectations authors have on the readers of the document that are very different from the practices where I work.
Labels:
devops
Thursday, July 23, 2020
Sunday, July 19, 2020
operational incidents: management prevents learning
John Allspaw presents two years of learning from the field, exposing interesting anti-patterns and common practices that prevent learning. It's definitely worth skimming.
Labels:
devops
Monday, July 13, 2020
BTRFS @ scale
The B-Tree File System (BTRFS) on Linux is gaining ground inside of Facebook for many use cases, workloads, and applications at enormous scale. In particular, the file system snapshot feature provides enormous space and CPU savings for workloads involving large numbers of delete operations -- even better than tombstoning. Check out this interview with one of the lead developers, Josef Bacik this month at the Open Source Summit. If you prefer watching videos to reading, check out these videos.
Labels:
devops
Anti-Patterns and Patterns in continuous delivery practices
A bunch of people have recently picked up on Matt Skelton's talk (and his book) to dispel some of the most-common myths and articulate the worst anti-patterns along with their associated better practice patterns in improving code velocity. It's worth skimming the deck.
Labels:
devops
why & how to create isolated environments per pull request
Avner Sorek from env0 gives a mini-tutorial on how & why to create an isolated test environment for your pull requests and integrate the process with git-ops (git actions in your continuous integration pipeline). The power of containerization enables creating temporary environments that are completely isolated in all phases of developing your web application from machine-local through all phases of testing, integration, and deployment. And if you are in a hurry, you can run many of them in parallel. On a public cloud the instant provisioning and tear-down of these environments and all infrastructure needed are simple and straightforward. Some private, on-premise clouds are not yet capable of enabling these features.
Labels:
devops
Subscribe to:
Posts (Atom)










