https://sade.dev/en/2026-09-05T00:00:00.000Zhttps://sade.dev/en/about/2026-08-30T00:00:00.000Zhttps://sade.dev/en/cookies/2026-08-08T00:00:00.000Zhttps://sade.dev/en/glossary/2026-09-05T00:00:00.000Zhttps://sade.dev/en/journal/2026-08-30T04:20:41.000Zhttps://sade.dev/en/journal/ai-assisted-engineering-workflow/2026-08-30T04:20:41.000Zhttps://sade.dev/_astro/ai-assisted-engineering-workflow.DH576_f3.jpgMy AI-Assisted Engineering Workflow — sade.devhttps://sade.dev/en/journal/ai-didnt-remove-the-bottleneck/2026-08-30T04:20:41.000Zhttps://sade.dev/_astro/ai-bottleneck-shift.85aM1CAy.jpgAI Didn't Remove the Bottleneck — It Moved It — sade.devhttps://sade.dev/en/journal/architecture-decisions-rot/2026-08-30T04:20:41.000Zhttps://sade.dev/_astro/executable-architecture.YwQcM_e2.jpgYour Architecture Decisions Rot Because Nothing Runs Them — sade.devhttps://sade.dev/en/journal/can-you-ship-vibe-coded-to-production/2026-08-30T04:20:41.000Zhttps://sade.dev/_astro/vibe-coding-ile-production.DaGSFmxY.jpgCan You Ship Vibe-Coded Software to Production? — sade.devhttps://sade.dev/en/journal/flaky-tests-and-determinism/2026-08-30T04:20:41.000Zhttps://sade.dev/_astro/flaky-tests-determinism.Bam2RNDx.jpgFlaky Tests: Retrying Isn't a Fix — sade.devhttps://sade.dev/en/journal/gitflow-vs-github-flow/2026-08-30T04:20:41.000Zhttps://sade.dev/_astro/gitflow-mu-github-flow-mu.XINmOnb0.jpgGitflow or GitHub Flow? How I Choose — sade.devhttps://sade.dev/en/journal/is-postgresql-enough-for-everything/2026-08-30T04:20:41.000Zhttps://sade.dev/_astro/postgresql-her-seye-yeter-mi.BxOS3_0K.jpgIs PostgreSQL Enough for Everything? — sade.devhttps://sade.dev/en/journal/layered-vs-clean-architecture/2026-08-30T04:20:41.000Zhttps://sade.dev/_astro/katmanli-mimari-mi-clean-architecture-mi.x60OgWFx.jpgLayered Architecture or Clean Architecture? — sade.devhttps://sade.dev/en/journal/schema-evolution-without-breaking/2026-08-30T04:20:41.000Zhttps://sade.dev/_astro/schema-evolution.DWacV6hD.jpgSchema Evolution: Changing a Contract Without Breaking It — sade.devhttps://sade.dev/en/journal/signals-of-an-over-complex-system/2026-07-25T00:00:00.000Zhttps://sade.dev/_astro/gereginden-karmasik-sistem-sinyalleri.BOBt36co.jpgSignals That a System Has Grown Too Complex — sade.devhttps://sade.dev/en/journal/the-cost-of-just-in-case-code/2026-08-30T04:20:41.000Zhttps://sade.dev/_astro/ileride-lazim-olur-kodunun-faturasi._e1TVcWL.jpgThe Production Cost of "Just-in-Case" Code — sade.devhttps://sade.dev/en/journal/the-nosql-trap/2026-08-30T04:20:41.000Zhttps://sade.dev/_astro/nosql-tuzagi.CCNNSW6L.jpgThe NoSQL Trap: Starting Because "It Has No Schema" — sade.devhttps://sade.dev/en/journal/when-i-move-to-microservices/2026-08-30T04:20:41.000Zhttps://sade.dev/_astro/mikroservise-ne-zaman-gecerim.D6wWXZyd.jpgWhen I Move to Microservices — sade.devhttps://sade.dev/en/journal/when-i-switch-to-trunk-based/2026-08-30T04:20:41.000Zhttps://sade.dev/_astro/trunk-based-ne-zaman-geciyorum.84rFjFnq.jpgWhen I Switch to Trunk-Based Development — sade.devhttps://sade.dev/en/journal/why-boring-architecture/2026-08-30T04:20:41.000Zhttps://sade.dev/_astro/neden-boring-architecture.D5cYmPZA.jpgWhy I Prefer Boring Architecture — sade.devhttps://sade.dev/en/journal/why-i-start-with-a-modular-monolith/2026-08-30T04:20:41.000Zhttps://sade.dev/_astro/projelere-neden-moduler-monolit-ile-basliyorum.GPVqis8x.jpgWhy I Start Projects With a Modular Monolith — sade.devhttps://sade.dev/en/notes/2026-09-05T00:00:00.000Zhttps://sade.dev/en/notes/bff-backend-for-frontend/2026-08-30T04:20:41.000Zhttps://sade.dev/_astro/bff-backend-for-frontend.BkSSou5k.jpgThe BFF Pattern: A Separate API Layer for Mobile and Web — sade.devhttps://sade.dev/en/notes/circuit-breaker-external-service-integration/2026-08-30T04:20:41.000Zhttps://sade.dev/_astro/circuit-breaker-dis-servis-entegrasyonu.DIkkqgha.jpgCircuit Breakers for External Service Integrations — sade.devhttps://sade.dev/en/notes/idempotency-duplicate-delivery/2026-09-02T19:36:54.000Zhttps://sade.dev/_astro/idempotency-duplicate-delivery.DTYbxLtJ.jpgIdempotency: When the Same Message Arrives Twice — sade.devhttps://sade.dev/en/notes/index-management/2026-09-05T00:00:00.000Zhttps://sade.dev/_astro/indeks-yonetimi.D20IsWTo.jpgIndex Management: Too Few Slow Reads, Too Many Kill Writes — sade.devhttps://sade.dev/en/notes/laravel-queue-production-slowdown/2026-08-30T04:20:41.000Zhttps://sade.dev/_astro/laravel-queue-production-yavaslama.CIbvna8o.jpgWhy Do Laravel Queues Slow Down in Production? — sade.devhttps://sade.dev/en/notes/nginx-php-fpm-pool-separation/2026-08-30T04:20:41.000Zhttps://sade.dev/_astro/nginx-php-fpm-pool-ayrimi.CvcaFm0K.jpgNginx + PHP-FPM Pool Separation — sade.devhttps://sade.dev/en/notes/pgbackrest-postgresql-backup-strategy/2026-08-30T04:20:41.000Zhttps://sade.dev/_astro/pgbackrest-postgresql-backup-stratejisi.DRsZpLiS.jpgA PostgreSQL Backup Strategy with pgBackRest — sade.devhttps://sade.dev/en/notes/pgbouncer-auth-query/2026-08-30T04:20:41.000Zhttps://sade.dev/_astro/pgbouncer-auth-query.BrIjf_Ar.jpgMultiple DB Users with pgBouncer auth_query — sade.devhttps://sade.dev/en/notes/read-write-splitting/2026-08-30T04:20:41.000Zhttps://sade.dev/_astro/read-write-splitting.D40FaGF4.jpgRead/Write Splitting: Separating Read and Write Load — sade.devhttps://sade.dev/en/notes/replaying-a-dead-letter-queue/2026-08-30T04:20:41.000Zhttps://sade.dev/_astro/replaying-a-dead-letter-queue.CWCTcULN.jpgReplaying a Dead-Letter Queue Without Making It Worse — sade.devhttps://sade.dev/en/notes/serverless-migration-decision/2026-08-30T04:20:41.000Zhttps://sade.dev/_astro/serverless-gecis-karari.BHdDXKxn.jpgThe Serverless Migration Decision: Cold-Start and Vendor Lock-in — sade.devhttps://sade.dev/en/notes/shared-redis-namespace-isolation/2026-08-30T04:20:41.000Zhttps://sade.dev/_astro/shared-redis-namespace-izolasyonu.F_LQvxI5.jpgNamespace Isolation for a Shared Redis — sade.devhttps://sade.dev/en/notes/sync-vs-async/2026-08-30T04:20:41.000Zhttps://sade.dev/_astro/senkron-mu-asenkron-mu.2PLCA7O2.jpgSynchronous or Asynchronous? The Line Between HTTP and the Queue — sade.devhttps://sade.dev/en/notes/the-right-cache-strategy/2026-08-30T04:20:41.000Zhttps://sade.dev/_astro/dogru-cache-stratejisi.CyjXSQDU.jpgBefore You Reach for Redis: The Right Cache Strategy — sade.devhttps://sade.dev/en/notes/validate-schema-at-the-edge/2026-08-30T04:20:41.000Zhttps://sade.dev/_astro/validate-schema-at-the-edge.DGFunoOX.jpgValidating the Schema at the Edge of the Queue — sade.devhttps://sade.dev/en/notes/when-event-driven-architecture/2026-06-20T00:00:00.000Zhttps://sade.dev/_astro/event-driven-mimari-ne-zaman.BXDxkXxl.jpgEvent-Driven Architecture: When It Saves You, When It Adds Complexity — sade.devhttps://sade.dev/en/notes/zero-downtime-database-migrations/2026-08-30T04:20:41.000Zhttps://sade.dev/_astro/zero-downtime-veritabani-gocleri.DrRLXSS-.jpgChanging Schema in Production With Zero Downtime — sade.devhttps://sade.dev/en/privacy/2026-08-08T00:00:00.000Zhttps://sade.dev/en/series/2026-09-05T00:00:00.000Zhttps://sade.dev/en/series/postgresql-in-production/2026-09-05T00:00:00.000Zhttps://sade.dev/en/stack/2026-08-08T00:00:00.000Zhttps://sade.dev/en/systems/2026-08-30T04:20:41.000Zhttps://sade.dev/en/systems/data-intensive-systems-breaking-points/2026-08-30T04:20:41.000Zhttps://sade.dev/diagrams/systems/en/data-intensive-systems-breaking-points.svgData load breaks at discrete points, not gradually. Order matters: taking the expensive step early means never having taken the cheap one.Breaking points of a data-intensive system, ordered from cheapest to most expensive: the starting state is PHP-FPM, pgBouncer and a single PostgreSQL primary alongside Redis. The first break is the working set outgrowing RAM, solved by index discipline, separating hot from cold data, and vertical scale. The second is read load saturating the single primary, solved with a read replica and a staleness classification. The third is one table growing too large, solved by partitioning and archiving. The fourth is write load saturating the primary, which requires sharding. The fifth is the data layer having to separate from the application. The last two steps are by far the most expensive.https://sade.dev/_astro/veri-yogunluklu-sistemler-kirilma-noktalari.GmvhhtO7.jpgScale Breaking Points in Data-Intensive Systems — sade.devhttps://sade.dev/en/systems/gpu-finops-with-ebpf/2026-08-30T04:20:41.000Zhttps://sade.dev/diagrams/systems/en/gpu-finops-with-ebpf.svgTwo different questions, two different tools. eBPF can issue the bill; DCGM tells you whether the bill was deserved.Two separate measurement paths for GPU chargeback: the GPU is invisible to existing CPU and RAM metrics. eBPF watches the syscall boundary and sees the control plane — who opened the device and for how long — attributing work to a pod, which answers the “who, how much” question and produces the bill. DCGM measures inside the silicon from userspace — SM utilisation, memory, power — and answers “how well did it run”. Real chargeback joins both on pod identity: a team’s spend and its efficiency together.https://sade.dev/_astro/ebpf-ile-gpu-finops.cL72w7Rv.jpgGPU FinOps with eBPF — sade.devhttps://sade.dev/en/systems/laravel-production-stack/2026-08-30T04:20:41.000Zhttps://sade.dev/diagrams/systems/en/laravel-production-stack.svgEvery box does one job on its own; what you lose by removing each is in the table at the end of the article.Request flow through a Laravel production stack: from Cloudflare (DDoS, WAF, CDN, TLS) to Nginx, then to PHP-FPM with opcache and preload enabled. PHP-FPM reaches three backing services: PostgreSQL behind pgBouncer, Redis serving cache, session and lock duties, and RabbitMQ for the durable queue. Horizon workers under Supervisor consume from RabbitMQ.https://sade.dev/_astro/laravel-production-stack.1Yoiu4Gk.jpgLaravel Production Stack — sade.devhttps://sade.dev/en/systems/polyglot-queue-distributed-tracing/2026-08-30T04:20:41.000Zhttps://sade.dev/diagrams/systems/en/polyglot-queue-distributed-tracing.svgThe trace was inside trace_id all along: a UUID and an OTel TraceID are the same sixteen bytes.How distributed tracing works across a polyglot queue: PHP, Go and Python services all produce and consume the same frozen envelope. The trace_id the envelope already carries is a UUID, which is exactly 16 bytes. An OpenTelemetry TraceID is also exactly 16 bytes, so the two map one to one — drop the dashes, read 32 hex characters — and every hop lands in the same trace with no change to the wire format. The limit this first phase accepts: because no span id travels on the wire, cross-hop parenthood rests on a synthetic ghost span and the hierarchy stays flat under one trace.https://sade.dev/_astro/polyglot-queue-distributed-tracing.CCy2PF3j.jpgDistributed Tracing Across a Polyglot Queue — sade.devhttps://sade.dev/en/systems/race-conditions-and-gaps-in-sequential-numbering/2026-08-30T04:20:41.000Zhttps://sade.dev/diagrams/systems/en/race-conditions-and-gaps-in-sequential-numbering.svgGenerate the number late and you get a race; generate it early and you get a gap. Reservation closes both — as long as the lock stays outside the external call.Order of a just-in-time reservation for sequential numbering: N parallel workers pick jobs off the queue, the counter row is advanced under a lock held for single-digit milliseconds only, the reserved number is written to the draft invoice and committed early, and the lock is released there. The external integrator call — which may be slow — happens outside the lock. On success the number is used; on failure or cancellation the reserved number is preserved and the retry reuses it, so the series gets neither duplicates nor gaps.https://sade.dev/_astro/sequential-numbering-jit-reservation.C6aDkIO6.jpgRace Conditions and Gaps in Sequential Numbering: JIT Reservation — sade.devhttps://sade.dev/en/systems/single-vps-multi-project-architecture/2026-08-30T04:20:41.000Zhttps://sade.dev/diagrams/systems/en/single-vps-multi-project-architecture.svgOne machine, three independent applications: isolation at the process and user level, sharing at the data layer.Layers of a single-VPS architecture: traffic on 80/443 enters Nginx, which dispatches over unix sockets to a separate PHP-FPM pool per project (billing, notify, blog — each running as its own unix user), and all three pools reach shared services over localhost: PostgreSQL behind pgBouncer with a separate database and role per project, a Redis instance isolated by key prefix, and Supervisor running one queue worker group per project.https://sade.dev/_astro/tek-vps-coklu-proje-mimarisi.yWxb7d5T.jpgMultiple Projects on a Single VPS — sade.devhttps://sade.dev/en/systems/transactional-outbox-dual-write-and-idempotent-consumption/2026-08-30T04:20:41.000Zhttps://sade.dev/diagrams/systems/en/transactional-outbox-dual-write-and-idempotent-consumption.svgThe outbox reduces dual-write to a single write; what it buys you is at-least-once, not exactly-once.Transactional outbox flow: the application writes the business row and the outbox row inside one transaction, removing the dual-write that the broker was never part of. A separate relay reads pending rows with SKIP LOCKED, publishes to RabbitMQ, and only then stamps them published — an order that prevents lost events but produces at-least-once redelivery. The consumer suppresses repeats by recording every event id in a processed_messages table and applies the business effect exactly once.https://sade.dev/_astro/transactional-outbox-dual-write-idempotent-consumption.Cy1faj4g.jpgTransactional Outbox: Dual-Write, At-Least-Once, and Idempotent Consumption — sade.devhttps://sade.dev/en/systems/zero-static-authority-multi-cluster-gitops/2026-08-30T04:20:41.000Zhttps://sade.dev/diagrams/systems/en/zero-static-authority-multi-cluster-gitops.svgA kubeconfig on disk is a long-lived credential aimed at your whole fleet. It is replaced by an SVID that expires in an hour and is never written down.The chain that removes static authority from multi-cluster GitOps: desired state lives in the Git repository, the GitOps controller on the hub cluster applies it and draws its identity from SPIRE’s Workload API. Through node attestation SPIRE issues the controller a workload SVID that lives about an hour and is never written to disk. Trust domain federation lets the spoke clusters’ apiservers accept that SVID over OIDC. The long-lived kubeconfig Secrets sitting on disk with authority over the whole fleet are then deleted outright.https://sade.dev/_astro/cok-kumeli-gitops-sifir-statik-yetki.DcG8HWjp.jpgZero Static Authority in Multi-Cluster GitOps — sade.devhttps://sade.dev/en/tags/2026-09-05T00:00:00.000Zhttps://sade.dev/en/tags/ai-workflow/2026-08-30T04:20:41.000Zhttps://sade.dev/en/tags/api/2026-08-30T04:20:41.000Zhttps://sade.dev/en/tags/architecture/2026-09-02T19:36:54.000Zhttps://sade.dev/en/tags/database/2026-09-05T00:00:00.000Zhttps://sade.dev/en/tags/decisions/2026-08-30T04:20:41.000Zhttps://sade.dev/en/tags/messaging/2026-08-30T04:20:41.000Zhttps://sade.dev/en/tags/opinion/2026-08-30T04:20:41.000Zhttps://sade.dev/en/tags/performance/2026-09-05T00:00:00.000Zhttps://sade.dev/en/tags/postgresql/2026-09-05T00:00:00.000Zhttps://sade.dev/en/tags/production/2026-08-30T04:20:41.000Zhttps://sade.dev/en/tags/queue/2026-09-02T19:36:54.000Zhttps://sade.dev/en/tags/redis/2026-08-30T04:20:41.000Zhttps://sade.dev/en/tags/reliability/2026-09-02T19:36:54.000Zhttps://sade.dev/en/tags/schema/2026-08-30T04:20:41.000Zhttps://sade.dev/en/tags/security/2026-08-30T04:20:41.000Zhttps://sade.dev/en/tags/simplicity/2026-08-30T04:20:41.000Zhttps://sade.dev/en/terms/2026-08-08T00:00:00.000Zhttps://sade.dev/en/tools/2026-08-30T04:20:41.000Zhttps://sade.dev/en/tools/backoff-calculator/2026-08-30T04:20:41.000Zhttps://sade.dev/en/tools/base64/2026-08-30T04:20:41.000Zhttps://sade.dev/en/tools/env-parser/2026-08-30T04:20:41.000Zhttps://sade.dev/en/tools/http-status/2026-08-30T04:20:41.000Zhttps://sade.dev/en/tools/json-formatter/2026-08-30T04:20:41.000Zhttps://sade.dev/en/tools/jwt-decoder/2026-08-30T04:20:41.000Zhttps://sade.dev/en/tools/password-generator/2026-08-30T04:20:41.000Zhttps://sade.dev/en/tools/schema-compat/2026-08-30T04:20:41.000Zhttps://sade.dev/en/tools/timestamp/2026-08-30T04:20:41.000Zhttps://sade.dev/en/tools/url-parser/2026-08-30T04:20:41.000Zhttps://sade.dev/en/tools/uuid/2026-08-30T04:20:41.000Zhttps://sade.dev/tr/2026-09-05T00:00:00.000Zhttps://sade.dev/tr/about/2026-08-30T00:00:00.000Zhttps://sade.dev/tr/cookies/2026-08-08T00:00:00.000Zhttps://sade.dev/tr/glossary/2026-09-05T00:00:00.000Zhttps://sade.dev/tr/journal/2026-08-30T04:20:41.000Zhttps://sade.dev/tr/journal/ai-assisted-engineering-workflow/2026-08-30T04:20:41.000Zhttps://sade.dev/_astro/ai-assisted-engineering-workflow.DH576_f3.jpgAI-Assisted Engineering Workflow'um — sade.devhttps://sade.dev/tr/journal/ai-darbogazi-kaldirmadi/2026-08-30T04:20:41.000Zhttps://sade.dev/_astro/ai-bottleneck-shift.85aM1CAy.jpgAI Darboğazı Kaldırmadı, Yerini Değiştirdi — sade.devhttps://sade.dev/tr/journal/gereginden-karmasik-sistem-sinyalleri/2026-08-30T04:20:41.000Zhttps://sade.dev/_astro/gereginden-karmasik-sistem-sinyalleri.BOBt36co.jpgBir Sistemin "Gereğinden Karmaşık" Olduğunu Gösteren Sinyaller — sade.devhttps://sade.dev/tr/journal/gitflow-mu-github-flow-mu/2026-08-30T04:20:41.000Zhttps://sade.dev/_astro/gitflow-mu-github-flow-mu.XINmOnb0.jpgGitflow mu, GitHub Flow mu? Neye Göre Seçiyorum? — sade.devhttps://sade.dev/tr/journal/ileride-lazim-olur-kodunun-faturasi/2026-08-30T04:20:41.000Zhttps://sade.dev/_astro/ileride-lazim-olur-kodunun-faturasi._e1TVcWL.jpg"İleride Lazım Olur" Kodunun Production Faturası — sade.devhttps://sade.dev/tr/journal/kararsiz-testler-ve-determinizm/2026-08-30T04:20:41.000Zhttps://sade.dev/_astro/flaky-tests-determinism.Bam2RNDx.jpgKararsız Testler: Retry Çözüm Değil — sade.devhttps://sade.dev/tr/journal/katmanli-mimari-mi-clean-architecture-mi/2026-08-30T04:20:41.000Zhttps://sade.dev/_astro/katmanli-mimari-mi-clean-architecture-mi.x60OgWFx.jpgKatmanlı Mimari mi, Clean Architecture mı? — sade.devhttps://sade.dev/tr/journal/mikroservise-ne-zaman-gecerim/2026-08-30T04:20:41.000Zhttps://sade.dev/_astro/mikroservise-ne-zaman-gecerim.D6wWXZyd.jpgMikroservise Ne Zaman Geçerim? — sade.devhttps://sade.dev/tr/journal/mimari-kararlar-curur/2026-08-30T04:20:41.000Zhttps://sade.dev/_astro/executable-architecture.YwQcM_e2.jpgMimari Kararların Çürüyor Çünkü Onları Hiçbir Şey Çalıştırmıyor — sade.devhttps://sade.dev/tr/journal/neden-boring-architecture/2026-08-30T04:20:41.000Zhttps://sade.dev/_astro/neden-boring-architecture.D5cYmPZA.jpgNeden Boring Architecture'ı Tercih Ediyorum — sade.devhttps://sade.dev/tr/journal/nosql-tuzagi/2026-08-30T04:20:41.000Zhttps://sade.dev/_astro/nosql-tuzagi.CCNNSW6L.jpgNoSQL Tuzağı: "Şeması Yok" Diye Başlamak — sade.devhttps://sade.dev/tr/journal/postgresql-her-seye-yeter-mi/2026-08-30T04:20:41.000Zhttps://sade.dev/_astro/postgresql-her-seye-yeter-mi.BxOS3_0K.jpgPostgreSQL Her Şeye Yeter mi? — sade.devhttps://sade.dev/tr/journal/projelere-neden-moduler-monolit-ile-basliyorum/2026-08-30T04:20:41.000Zhttps://sade.dev/_astro/projelere-neden-moduler-monolit-ile-basliyorum.GPVqis8x.jpgProjelere Neden Modüler Monolit ile Başlıyorum? — sade.devhttps://sade.dev/tr/journal/sema-evrimi-sozlesmeyi-kirmadan/2026-08-30T04:20:41.000Zhttps://sade.dev/_astro/schema-evolution.DWacV6hD.jpgŞema Evrimi: Sözleşmeyi Kırmadan Değiştirmek — sade.devhttps://sade.dev/tr/journal/trunk-based-ne-zaman-geciyorum/2026-08-30T04:20:41.000Zhttps://sade.dev/_astro/trunk-based-ne-zaman-geciyorum.84rFjFnq.jpgTrunk-Based Development'a Ne Zaman Geçiyorum? — sade.devhttps://sade.dev/tr/journal/vibe-coding-ile-production/2026-08-30T04:20:41.000Zhttps://sade.dev/_astro/vibe-coding-ile-production.DaGSFmxY.jpgVibe Coding ile Production'a Çıkılır mı? — sade.devhttps://sade.dev/tr/notes/2026-09-05T00:00:00.000Zhttps://sade.dev/tr/notes/bff-backend-for-frontend/2026-08-30T04:20:41.000Zhttps://sade.dev/_astro/bff-backend-for-frontend.BkSSou5k.jpgBFF Pattern: Mobil ve Web İçin Ayrı API Katmanı — sade.devhttps://sade.dev/tr/notes/circuit-breaker-dis-servis-entegrasyonu/2026-08-30T04:20:41.000Zhttps://sade.dev/_astro/circuit-breaker-dis-servis-entegrasyonu.DIkkqgha.jpgDış Servis Entegrasyonlarında Circuit Breaker — sade.devhttps://sade.dev/tr/notes/dead-letter-kuyrugunu-guvenle-replay-etmek/2026-08-30T04:20:41.000Zhttps://sade.dev/_astro/replaying-a-dead-letter-queue.CWCTcULN.jpgDead-Letter Kuyruğunu Daha Kötü Yapmadan Replay Etmek — sade.devhttps://sade.dev/tr/notes/dogru-cache-stratejisi/2026-08-30T04:20:41.000Zhttps://sade.dev/_astro/dogru-cache-stratejisi.CyjXSQDU.jpgRedis Koymadan Önce: Doğru Cache Stratejisi — sade.devhttps://sade.dev/tr/notes/event-driven-mimari-ne-zaman/2026-08-30T04:20:41.000Zhttps://sade.dev/_astro/event-driven-mimari-ne-zaman.BXDxkXxl.jpgEvent-Driven Mimari: Ne Zaman Kurtarır, Ne Zaman Karmaşıklaştırır? — sade.devhttps://sade.dev/tr/notes/idempotency-ayni-mesaj-iki-kez/2026-09-02T19:15:21.000Zhttps://sade.dev/_astro/idempotency-duplicate-delivery.DTYbxLtJ.jpgIdempotency: Aynı Mesaj İki Kez Geldiğinde — sade.devhttps://sade.dev/tr/notes/indeks-yonetimi/2026-09-05T00:00:00.000Zhttps://sade.dev/_astro/indeks-yonetimi.D20IsWTo.jpgİndeks Yönetimi: Eksik Yavaşlatır, Fazlası Yazmayı Öldürür — sade.devhttps://sade.dev/tr/notes/laravel-queue-production-yavaslama/2026-08-30T04:20:41.000Zhttps://sade.dev/_astro/laravel-queue-production-yavaslama.CIbvna8o.jpgLaravel Queue Production'da Neden Yavaşlar? — sade.devhttps://sade.dev/tr/notes/nginx-php-fpm-pool-ayrimi/2026-08-30T04:20:41.000Zhttps://sade.dev/_astro/nginx-php-fpm-pool-ayrimi.CvcaFm0K.jpgNginx + PHP-FPM Pool Ayrımı — sade.devhttps://sade.dev/tr/notes/pgbackrest-postgresql-backup-stratejisi/2026-08-30T04:20:41.000Zhttps://sade.dev/_astro/pgbackrest-postgresql-backup-stratejisi.DRsZpLiS.jpgpgBackRest ile PostgreSQL Backup Stratejisi — sade.devhttps://sade.dev/tr/notes/pgbouncer-auth-query/2026-08-30T04:20:41.000Zhttps://sade.dev/_astro/pgbouncer-auth-query.BrIjf_Ar.jpgpgBouncer auth_query ile Çoklu DB Kullanıcısı — sade.devhttps://sade.dev/tr/notes/read-write-splitting/2026-08-30T04:20:41.000Zhttps://sade.dev/_astro/read-write-splitting.D40FaGF4.jpgRead/Write Splitting: Okuma ve Yazma Yükünü Ayırmak — sade.devhttps://sade.dev/tr/notes/semayi-kuyrugun-kenarinda-dogrulamak/2026-08-30T04:20:41.000Zhttps://sade.dev/_astro/validate-schema-at-the-edge.DGFunoOX.jpgŞemayı Kuyruğun Kenarında Doğrulamak — sade.devhttps://sade.dev/tr/notes/senkron-mu-asenkron-mu/2026-08-30T04:20:41.000Zhttps://sade.dev/_astro/senkron-mu-asenkron-mu.2PLCA7O2.jpgSenkron mu, Asenkron mu? HTTP ile Kuyruk Arasındaki Sınır — sade.devhttps://sade.dev/tr/notes/serverless-gecis-karari/2026-08-30T04:20:41.000Zhttps://sade.dev/_astro/serverless-gecis-karari.BHdDXKxn.jpgServerless'a Geçiş Kararı: Cold-Start ve Vendor Lock-in — sade.devhttps://sade.dev/tr/notes/shared-redis-namespace-izolasyonu/2026-08-30T04:20:41.000Zhttps://sade.dev/_astro/shared-redis-namespace-izolasyonu.F_LQvxI5.jpgShared Redis Kullanırken Namespace İzolasyonu — sade.devhttps://sade.dev/tr/notes/zero-downtime-veritabani-gocleri/2026-08-30T04:20:41.000Zhttps://sade.dev/_astro/zero-downtime-veritabani-gocleri.DrRLXSS-.jpgCanlıda Sıfır Kesintiyle Şema Değiştirmek — sade.devhttps://sade.dev/tr/privacy/2026-08-08T00:00:00.000Zhttps://sade.dev/tr/series/2026-09-05T00:00:00.000Zhttps://sade.dev/tr/series/postgresql-in-production/2026-09-05T00:00:00.000Zhttps://sade.dev/tr/stack/2026-08-08T00:00:00.000Zhttps://sade.dev/tr/systems/2026-08-30T04:20:41.000Zhttps://sade.dev/tr/systems/ardisik-numara-uretiminde-race-condition-ve-gap/2026-08-30T04:20:41.000Zhttps://sade.dev/diagrams/systems/tr/ardisik-numara-uretiminde-race-condition-ve-gap.svgNumarayı geç üretmek race, erken üretmek gap doğurur. Rezervasyon ikisini de kapatır — kilit dış çağrının dışında kaldığı sürece.Ardışık numara üretiminde JIT rezervasyon sırası: kuyruktan gelen işi N paralel worker alır, sayaç satırı yalnızca tek haneli milisaniyeler süren bir kilitle ilerletilir, rezerve edilen numara taslak faturaya yazılıp erken commit edilir ve kilit orada açılır. Yavaş olabilen entegratör API çağrısı kilidin dışında yapılır. Çağrı başarılıysa numara kullanılmış olur; hata veya iptal durumunda rezerve edilen numara korunur ve retry aynı numarayla döner, böylece ne mükerrer numara ne de seride boşluk oluşur.https://sade.dev/_astro/sequential-numbering-jit-reservation.C6aDkIO6.jpgArdışık Numara Üretiminde Race Condition ve Gap: JIT Rezervasyon — sade.devhttps://sade.dev/tr/systems/cok-kumeli-gitops-sifir-statik-yetki/2026-08-30T04:20:41.000Zhttps://sade.dev/diagrams/systems/tr/cok-kumeli-gitops-sifir-statik-yetki.svgDiskte duran bir kubeconfig, filonuza nişan almış uzun ömürlü bir kimliktir. Yerine bir saatte sona eren, hiç yazılmayan bir SVID koyulur.Çok kümeli GitOps’ta statik yetkiyi kaldıran zincir: desired state Git deposunda durur, hub kümedeki GitOps controller onu uygular ve kimliğini SPIRE’ın Workload API’sinden alır. SPIRE node attestation ile controller’a yaklaşık bir saat ömürlü, diske hiç yazılmayan bir workload SVID basar. Trust domain federasyonu sayesinde spoke kümelerin apiserver’ları bu SVID’yi OIDC üzerinden kabul eder. Böylece diskte duran, uzun ömürlü ve tüm filoya yetkili kubeconfig Secret’ları tamamen silinir.https://sade.dev/_astro/cok-kumeli-gitops-sifir-statik-yetki.DcG8HWjp.jpgÇok Kümeli GitOps’ta Sıfır Statik Yetki — sade.devhttps://sade.dev/tr/systems/ebpf-ile-gpu-finops/2026-08-30T04:20:41.000Zhttps://sade.dev/diagrams/systems/tr/ebpf-ile-gpu-finops.svgİki farklı soru, iki farklı araç. eBPF faturayı kesebilir, DCGM faturanın haklı olup olmadığını söyler.GPU chargeback’in iki ayrı ölçüm yolu: GPU, mevcut CPU ve RAM metriklerine görünmez. eBPF syscall sınırını izleyerek kontrol düzlemini — cihazı kimin açtığını, ne kadar tuttuğunu — görür ve işi bir pod’a atfeder; bu “kim, ne kadar” sorusunu, yani faturayı cevaplar. DCGM ise userspace’ten silikonun içini — SM kullanımı, bellek, güç — ölçer ve “ne kadar iyi koştu” sorusunu cevaplar. Gerçek bir chargeback ikisini pod kimliğinde birleştirir: ekibin hem harcaması hem verimliliği.https://sade.dev/_astro/ebpf-ile-gpu-finops.cL72w7Rv.jpgeBPF ile GPU FinOps — sade.devhttps://sade.dev/tr/systems/laravel-production-stack/2026-08-30T04:20:41.000Zhttps://sade.dev/diagrams/systems/tr/laravel-production-stack.svgHer kutu bir işi tek başına yapar; birini çıkardığınızda ne kaybettiğiniz yazının sonundaki tabloda.Laravel production stack’inin akışı: istek Cloudflare’den (DDoS, WAF, CDN, TLS) Nginx’e, oradan opcache ve preload açık PHP-FPM’e gider. PHP-FPM üç arka servise bağlanır: pgBouncer arkasında PostgreSQL, cache/session/lock rollerini üstlenen Redis ve kalıcı kuyruk için RabbitMQ. RabbitMQ’dan mesajları Supervisor altında çalışan Horizon worker’ları çeker.https://sade.dev/_astro/laravel-production-stack.1Yoiu4Gk.jpgLaravel Production Stack — sade.devhttps://sade.dev/tr/systems/polyglot-kuyrukta-dagitik-izleme/2026-08-30T04:20:41.000Zhttps://sade.dev/diagrams/systems/tr/polyglot-kuyrukta-dagitik-izleme.svgTrace baştan beri trace_id’nin içindeydi: bir UUID ile bir OTel TraceID aynı on altı byte.Polyglot bir kuyrukta dağıtık izlemenin mekanizması: PHP, Go ve Python servisleri aynı donmuş envelope’u üretir ve tüketir. Envelope’un zaten taşıdığı trace_id alanı bir UUID’dir, yani tam olarak 16 byte. OpenTelemetry’de bir TraceID de tam olarak 16 byte olduğu için tireler atılıp 32 hex karakter okunarak birebir eşlenir; her hop aynı trace’e iner ve tel formatı hiç değişmez. Bu birinci fazın kabul ettiği sınır: span id telde taşınmadığı için hop’lar arası ebeveynlik sentetik bir hayalet span’e dayanır, hiyerarşi tek trace altında düz kalır.https://sade.dev/_astro/polyglot-queue-distributed-tracing.CCy2PF3j.jpgPolyglot Bir Kuyrukta Dağıtık İzleme — sade.devhttps://sade.dev/tr/systems/tek-vps-coklu-proje-mimarisi/2026-08-30T04:20:41.000Zhttps://sade.dev/diagrams/systems/tr/tek-vps-coklu-proje-mimarisi.svgBir makine, üç bağımsız uygulama: izolasyon süreç ve kullanıcı seviyesinde, paylaşım veri katmanında.Tek VPS mimarisinin katmanları: 80/443 trafiği Nginx’e girer, Nginx unix soket üzerinden proje başına ayrı PHP-FPM pool’larına dağıtır (billing, notify, blog — her biri kendi unix kullanıcısıyla), üç pool da localhost üzerinden paylaşılan servislere bağlanır: pgBouncer arkasında PostgreSQL (proje başına ayrı database ve role), prefix ile izole edilmiş Redis ve proje başına queue worker çalıştıran Supervisor.https://sade.dev/_astro/tek-vps-coklu-proje-mimarisi.yWxb7d5T.jpgTek VPS Üzerinde Çoklu Proje Mimarisi — sade.devhttps://sade.dev/tr/systems/transactional-outbox-dual-write-ve-idempotent-tuketim/2026-08-30T04:20:41.000Zhttps://sade.dev/diagrams/systems/tr/transactional-outbox-dual-write-ve-idempotent-tuketim.svgOutbox dual-write’ı tek write’a indirir; karşılığında aldığınız garanti exactly-once değil, at-least-once’tur.Transactional outbox akışı: uygulama iş satırını ve outbox satırını tek bir transaction içinde yazar, böylece broker’ı kapsamayan dual-write ortadan kalkar. Ayrı bir relay, SKIP LOCKED ile pending satırları okuyup RabbitMQ’ya publish eder ve ancak başarıdan sonra published damgası vurur; bu sıra kayıp event’i önler ama at-least-once tekrar üretir. Tüketici her event id’sini processed_messages tablosuna yazarak tekrarı bastırır ve iş etkisini tam bir kez uygular.https://sade.dev/_astro/transactional-outbox-dual-write-idempotent-consumption.Cy1faj4g.jpgTransactional Outbox: Dual-Write, At-Least-Once ve İdempotent Tüketim — sade.devhttps://sade.dev/tr/systems/veri-yogunluklu-sistemler-kirilma-noktalari/2026-08-30T04:20:41.000Zhttps://sade.dev/diagrams/systems/tr/veri-yogunluklu-sistemler-kirilma-noktalari.svgVeri yükü kademeli değil, ayrık noktalarda kırılır. Sıra önemli: pahalı adımı erken almak, ucuz adımı hiç almamış olmaktır.Veri yoğunluklu bir sistemin kırılma noktaları, ucuzdan pahalıya sıralı: başlangıç durumu PHP-FPM, pgBouncer ve tek bir PostgreSQL primary ile Redis’tir. Birinci kırılma working set’in RAM’e sığmamasıdır ve index disiplini, sıcak-soğuk veri ayrımı ve vertical scale ile çözülür. İkincisi okuma yükünün tek primary’yi doyurmasıdır, çözümü read replica ve bayatlık sınıflandırmasıdır. Üçüncüsü tek bir tablonun fazla büyümesidir, çözümü partition ve arşivlemedir. Dördüncüsü yazma yükünün primary’yi doyurmasıdır ve sharding gerektirir. Beşincisi veri katmanının uygulamadan ayrılmasıdır. Son iki adım açık ara en pahalı olanlardır.https://sade.dev/_astro/veri-yogunluklu-sistemler-kirilma-noktalari.GmvhhtO7.jpgVeri Yoğunluklu Sistemlerde Ölçek Kırılma Noktaları — sade.devhttps://sade.dev/tr/tags/2026-09-05T00:00:00.000Zhttps://sade.dev/tr/tags/ai-workflow/2026-08-30T04:20:41.000Zhttps://sade.dev/tr/tags/api/2026-08-30T04:20:41.000Zhttps://sade.dev/tr/tags/architecture/2026-09-02T19:15:21.000Zhttps://sade.dev/tr/tags/database/2026-09-05T00:00:00.000Zhttps://sade.dev/tr/tags/decisions/2026-08-30T04:20:41.000Zhttps://sade.dev/tr/tags/messaging/2026-08-30T04:20:41.000Zhttps://sade.dev/tr/tags/opinion/2026-08-30T04:20:41.000Zhttps://sade.dev/tr/tags/performance/2026-09-05T00:00:00.000Zhttps://sade.dev/tr/tags/postgresql/2026-09-05T00:00:00.000Zhttps://sade.dev/tr/tags/production/2026-08-30T04:20:41.000Zhttps://sade.dev/tr/tags/queue/2026-09-02T19:15:21.000Zhttps://sade.dev/tr/tags/redis/2026-08-30T04:20:41.000Zhttps://sade.dev/tr/tags/reliability/2026-09-02T19:15:21.000Zhttps://sade.dev/tr/tags/schema/2026-08-30T04:20:41.000Zhttps://sade.dev/tr/tags/security/2026-08-30T04:20:41.000Zhttps://sade.dev/tr/tags/simplicity/2026-08-30T04:20:41.000Zhttps://sade.dev/tr/terms/2026-08-08T00:00:00.000Zhttps://sade.dev/tr/tools/2026-08-30T04:20:41.000Zhttps://sade.dev/tr/tools/backoff-calculator/2026-08-30T04:20:41.000Zhttps://sade.dev/tr/tools/base64/2026-08-30T04:20:41.000Zhttps://sade.dev/tr/tools/env-parser/2026-08-30T04:20:41.000Zhttps://sade.dev/tr/tools/http-status/2026-08-30T04:20:41.000Zhttps://sade.dev/tr/tools/json-formatter/2026-08-30T04:20:41.000Zhttps://sade.dev/tr/tools/jwt-decoder/2026-08-30T04:20:41.000Zhttps://sade.dev/tr/tools/password-generator/2026-08-30T04:20:41.000Zhttps://sade.dev/tr/tools/schema-compat/2026-08-30T04:20:41.000Zhttps://sade.dev/tr/tools/timestamp/2026-08-30T04:20:41.000Zhttps://sade.dev/tr/tools/url-parser/2026-08-30T04:20:41.000Zhttps://sade.dev/tr/tools/uuid/2026-08-30T04:20:41.000Z