SRE | Page 2 of 2 | John Nessime

Optimizing API Calls to Reduce SaaS Costs: Six Levers That Actually Move the Bill

Post category:Cloud Computing DevOps Technical Guides

Third-party API spend is the one production signal with no error rate attached to it, which is why it creeps up quietly. This is a working engineer's guide to reducing SaaS API costs by changing the shape of your calls: reading the billing unit before you optimise anything, killing pointless polling with conditional requests and webhooks, collapsing N+1 patterns, caching with stampede protection and per-tenant keys, stopping your own retry amplification, and attributing spend so you can prove the work paid off.

Kubernetes Zero-Downtime Rollouts: Why Your Readiness Probe Isn’t Saving You

Post category:DevOps Kubernetes Technical Guides

Readiness probes are necessary for Kubernetes zero-downtime rollouts, but they only close one of four gaps. Here is what actually drops requests during a deploy: the race between SIGTERM and endpoint propagation, probes that lie, surge settings that quietly delete capacity, and load balancers that never watched EndpointSlices in the first place.

It Works Isn’t Ready: A Production Checklist for Salesforce AWS Integrations

Post category:Cloud Computing DevOps Technical Guides

"It works" and "it's ready" are different claims. Integrations rarely fail on launch day; they fail in week six, when the token expires and someone adds a field. A readiness checklist for Salesforce AWS integrations, with a pass test on every item.

It’s Only a Claim: Kubernetes Persistent Volumes and Stateful Workloads

Post category:DevOps Kubernetes Technical Guides

A PersistentVolumeClaim sounds like paperwork. Delete one on a cluster with the default reclaim policy and the underlying disk goes with it. A short guide to the parts of Kubernetes storage that bite: reclaim policies, access modes, zone affinity and StatefulSets.

The Cluster Becomes the Product: When Kubernetes Is Overkill

Post category:Cloud Computing DevOps Kubernetes

Three hours into an ingress controller upgrade for an application that is one Go binary and a Postgres database. Nothing is broken. The cluster has just become the thing you operate. An honest look at what Kubernetes costs, when it earns that cost, and what to run instead.

Zero Errors, Zero Records: Monitoring Salesforce Integrations with CloudWatch and Grafana

Post category:Cloud Computing DevOps Technical Guides

The error count was zero every day for three weeks. So was the invocation count. A stopped integration and a healthy one produce identical graphs, and every CloudWatch default is tuned to stay quiet when data stops arriving. Four signals worth emitting, and the alarm config that actually fires.

One Label Too Many: Centralized Logging With Loki Without Wrecking It

Post category:DevOps System Administration Technical Guides

Loki was fast until someone added one more label. Now queries time out during incidents and the index no longer fits in memory. Here's the model you have to internalise, what replaced Promtail, and how to keep labels, retention and storage costs under control.

Green Check, Broken Build: How to Build a Fail Fast Pipeline That Explains Why

Post category:DevOps Technical Guides Troubleshooting

A green pipeline that ships a broken build is worse than a red one. Here is how to order stages so failures surface in seconds, stop shell pipes from swallowing exit codes, and write failure output that tells the next engineer exactly what to fix.

Metrics, Logs and Traces: What Each One Answers

Post category:DevOps System Administration Web Performance

Metrics tell you that something is wrong. Traces tell you where. Logs tell you why. Use them in that order and each step narrows the search — start with logs and you are grepping a firehose. Here is what each one is actually for, and the field that connects all three.