Recommendation5d ago·1 entry
suggestion to go for AIOps
Let's migrate to AIOps from SRE and SDE
98 views26 likes0 comments0 bookmarks
sunilraju ch
@sunilrajuch
0 followers0 following15 expertise score4 posts
Community-recognized expertise
Built from shared experiences, perspectives, and verification signals — not vanity points.
Experiences shared
Learning8d ago·1 entry
I finally understood Postgres indexes the hard way
I used to think more indexes always meant faster queries. Production taught me about write amplification and table bloat instead. We had three indexes that nothing queried, slowing every insert. EXPLAIN ANALYZE finally showed which plans actually used which indexes. After dropping the dead ones, writes got healthier without hurting reads. Now I review unused indexes in the same ritual as reviewing slow queries.
284 views0 likes0 comments0 bookmarks
Problem solving9d ago·1 entry
a silent 502 that only hit 2% of traffic
No spike in CPU. Error budgets looked fine at a glance. Users still reported blank pages in a thin slice of traffic. Logs only showed upstream resets with no clear application exception. The culprit was a stale keep-alive timeout between nginx and the app. Aligning idle timeouts stopped the intermittent 502s within an hour. We also added a dashboard for upstream reset reasons so the next page is faster.
223 views0 likes0 comments0 bookmarks
Case study10d ago·1 entry
a monolith endpoint without a big-bang rewrite
We extracted one high-churn billing endpoint behind a strangler facade. Dual-writes ran for two weeks while we compared totals nightly. A feature flag controlled read traffic so we could roll back instantly. The hardest part was matching edge-case rounding in legacy invoices. Cutover finished with no customer-facing downtime and a smaller blast radius. We kept the facade until three more endpoints followed the same path.
173 views0 likes0 comments0 bookmarks