The engineering notebook / 01—05

Systems, explained.

Notes on building reliable infrastructure, writing better backends and making automation earn its place.

By Oğuzhan Gündüz
Cloud · Backend · Applied AI

01 / Cloud architecture

AWS High Availability: Design for Failure, Then Test It

A practical guide to failure domains, application state, database recovery and the capacity your surviving zone actually needs.

27 Sep 20267 min read

02 / FinOps

Move beyond the monthly invoice: choose a meaningful unit, find unnecessary work and verify savings without sacrificing reliability.

27 Sep 20267 min read

03 / Observability

Connect metrics, logs and traces to user-visible outcomes, then build an investigation path that works during a real failure.

27 Sep 20267 min read

04 / Backend engineering

Make caching predictable: define freshness, protect data boundaries and understand the races that annotations cannot solve alone.

27 Sep 20266 min read

05 / AI & infrastructure

Let a model interpret the request while code controls validation, authorization, change review and cluster execution.

27 Sep 20267 min read