Week 31: automation ubuntu apt updates, mongodb, loadbalancer choice, wal database, brendangregg, curl security process, frameworklaptop isa hardware, netdata

• How we sort of automate updating system packages across our Ubuntu machines: A process to keep o/s patches up to date across many servers. I like that there is a manual component to it. The automation is there to service the operator not replace them.
• MongoDB Tuning Anti-Patterns: How Tuning Memory Can Make Things Much Worse: Interesting point about compressed vs uncompressed data and how mongo balances that. 50% ram usage by mongo is fine nearly always!
• The power of two random choices, visualized: Easy to see 2 random choices load balancing strategy is better than random choice.
• A write-ahead log is not a universal part of durability: Durability, performance and the write ahead log. (WAL) Simple code snippets help get the ideas across effectively.
• Linux Crisis Tools: List of tools that may be used when investigating a performance issue on a linux server. (Ubuntu)

• Curl secure development practices: Nice list of this the curl team members do to try to lower the risk of security concerns in their process.
• What Is an Instruction Set Architecture?: Came up in an interview with the framework laptop ceo. The interface between h/w and s/w in a computer. Defines the operations and data types and operating system can send to the processor.
• Netdata vs Prometheus: Comparison of resource utilization (cpu, ram, disk, network) between netdata and prometheus. Netdata seems solidly performant. I should give it a try!