“Lately, I’ve been reading several really good books about building communities and thought I’d share them with you.” Original source: Online Community building books

“Lately, I’ve been reading several really good books about building communities and thought I’d share them with you.” Original source: Online Community building books

Nifty chart. Original source: Technology Spending by the Numbers: From Public Cloud to Security Measures - TheStreet

Nifty chart. Original source: Technology Spending by the Numbers: From Public Cloud to Security Measures - TheStreet

Nifty chart. Original source: Technology Spending by the Numbers: From Public Cloud to Security Measures - TheStreet

The most important thing is to be able to fix The Broken quickly, not make sure it never breaks. “They monitored 400 libraries. In 116 days, they saw 282 breaking changes! Each day, there’s 6.1% chance of breaking chg, for each lib you use!" Original source: “An astonishing paper that may explain why it’s so difficult to patch."

The most important thing is to be able to fix The Broken quickly, not make sure it never breaks. “They monitored 400 libraries. In 116 days, they saw 282 breaking changes! Each day, there’s 6.1% chance of breaking chg, for each lib you use!" Original source: “An astonishing paper that may explain why it’s so difficult to patch."

The most important thing is to be able to fix The Broken quickly, not make sure it never breaks. “They monitored 400 libraries. In 116 days, they saw 282 breaking changes! Each day, there’s 6.1% chance of breaking chg, for each lib you use!" Original source: “An astonishing paper that may explain why it’s so difficult to patch."

[Summary from the post of metrics to use:] Rate — Request rate, in requests/sec Errors — Error rate, in errors/sec Latency — Response time, including queue/wait time, in milliseconds. Saturation — How overloaded something is, which is related to utilization but more directly measured by things like queue depth (or sometimes concurrency). As a queue measurement, this becomes non-zero when you are saturated, often not much before. Usually a counter. Utilization — How busy the resource or system is.

[Summary from the post of metrics to use:] Rate — Request rate, in requests/sec Errors — Error rate, in errors/sec Latency — Response time, including queue/wait time, in milliseconds. Saturation — How overloaded something is, which is related to utilization but more directly measured by things like queue depth (or sometimes concurrency). As a queue measurement, this becomes non-zero when you are saturated, often not much before. Usually a counter. Utilization — How busy the resource or system is.