[{"data":1,"prerenderedAt":456},["ShallowReactive",2],{"site-header":3,"site-footer-license":37,"article-kenapa-backend-butuh-graceful-shutdown-jangan-asal-cabut-kabel-server-with-latest":41},{"navigations":4},[5,20],{"collection":6,"item":7},"series",{"__typename":6,"title":8,"slug":9,"children_series":10},"Artikel","all",[11,14,17],{"title":12,"slug":13},"Algoritma dan Struktur Data","algoritma-struktur-data",{"title":15,"slug":16},"Konsep Dasar Pemrograman","konsep-dasar-pemrograman",{"title":18,"slug":19},"Kecerdasan Artifisial","kecerdasan-artifisial",{"collection":6,"item":21},{"__typename":6,"title":22,"slug":23,"children_series":24},"Tutorial","tutorial",[25,28,31,34],{"title":26,"slug":27},"Belajar Java","belajar-java",{"title":29,"slug":30},"Belajar Pascal","belajar-pascal",{"title":32,"slug":33},"Belajar Python","belajar-python",{"title":35,"slug":36},"Belajar Golang","belajar-golang",{"name":38,"url":39,"show":40},"CC BY-SA","https://creativecommons.org/licenses/by-sa/4.0/",false,{"article":42,"renderedBody":414,"renderedTakeaway":415,"latestArticles":416,"toc":439},{"id":43,"title":44,"slug":45,"excerpt":46,"published_at":47,"thumbnail_image":48,"tags":50,"reading_time":58,"takeway":59,"body":60,"authors":61,"series":68},"37","Kenapa Backend Butuh Graceful Shutdown? Jangan Asal Cabut Kabel Server!","kenapa-backend-butuh-graceful-shutdown-jangan-asal-cabut-kabel-server","Pernah nggak sih, abis kalian nge-*deploy* backend, beberapa detik kemudian monitoring malah banjir *alert* **502 Bad Gateway** dari pengguna? Saldo udah kepotong tapi status order belum keburu ter-*update* di *database*. Yuk, kita bahas kenapa *graceful shutdown* itu wajib banget!","2026-08-24T06:15:59.150Z",{"id":49},"251a54a7-1d24-47fd-8cbc-a46fd42cbb6f",[51,52,53,54,55,56,57],"backend","devops","fastapi","docker","kubernetes","system-design","architecture",5,"- *Graceful shutdown* adalah etika server buat menyelesaikan semua *in-flight request* sebelum prosesnya benar-benar dimatikan.\n- Tanpa *graceful shutdown*, transaksi *database* menggantung, *connection pool* bocor, dan pengguna disambut error **502 Bad Gateway** tepat saat *deploy*.\n- Sinyal *SIGTERM* minta aplikasi berhenti dengan sopan, sedangkan *SIGKILL* memutus proses tanpa kompromi dan nggak bisa ditolak.\n- Kombinasi *lifespan handler* di FastAPI, *exec form* di Dockerfile, `terminationGracePeriodSeconds`, dan `preStop` hook bikin *deployment* berjalan tanpa *downtime*.","Baru aja kalian selesai nge-*deploy* versi terbaru backend ke server. Eh, beberapa detik kemudian channel monitoring malah banjir *alert* **502 Bad Gateway** dan *Connection Reset by Peer* dari pengguna. 😅\n\nSetelah dicek, ternyata ada transaksi checkout yang gagal di tengah jalan. Saldo udah kepotong di *payment gateway*, tapi status order-nya belum sempat ter-*update* di *database*!\n\nBiang keroknya sering banget sepele: proses server lama dimatikan mendadak alias *un-graceful shutdown*. Kita asal tebas proses aja, tanpa nawarin pamit dulu.\n\nIbaratnya kayak kalian lagi makan malam di restoran. Kalau tepat jam 22.00 manajer langsung matiin lampu, ngunci pintu, dan ngusir pengunjung yang makanannya baru setengah tersaji, pasti kalian kesel banget, kan? Nah, itu versi paksa.\n\nVersi beradabnya beda. Jam 21.30 staf udah mengumumkan *\"last order\"* dan nggak nerima tamu baru. Tapi yang udah duduk di dalam tetap dipersilakan menikmati hidangan sampai tuntas. Baru setelah semua meja kosong dan kasir nutup pembukuan, pintunya dikunci rapi.\n\nDi dunia *software*, *graceful shutdown* adalah etika server buat menyelesaikan semua pekerjaan yang sedang berjalan (*in-flight requests*) sebelum benar-benar mematikan prosesnya. Kalau langkah ini dilewatin, semua koneksi HTTP yang lagi berlangsung langsung putus di tengah jalan, transaksi *database* menggantung, dan *connection pool* pun bocor (*leak*).\n\nAgar backend kalian bisa diperbarui kapan aja tanpa bikin pengguna kena error, mekanisme ini wajib dipasang. Yuk, kita kupas tuntas cara kerjanya!\n\n## Mengenal Sinyal Unix: SIGINT, SIGTERM, dan SIGKILL\n\nSistem operasi—termasuk [Docker](https://docs.docker.com/) dan Kubernetes—ngobrol sama aplikasi backend lewat sinyal standar POSIX.\n\n*SIGINT* dikirim pas kalian nekan Ctrl + C di terminal. Aplikasi biasanya merespons dengan menghentikan eksekusi secara ramah.\n\n*SIGTERM* ini yang paling sering muncul di produksi. Docker (`docker stop`) atau Kubernetes mengirimnya saat *rolling update* atau *scale down* pod. Pesannya kira-kira: *\"Tolong siap-siap berhenti, selesaikan tugas yang sedang aktif!\"*\n\n*SIGKILL* (sinyal 9) adalah pamungkas yang nggak bisa ditolak atau ditangkap (*uninterceptable*) oleh aplikasi. Kernel langsung memutus proses secara instan. Kalau aplikasi nggak kunjung kelar dalam batas *grace period*, sistem bakal nembak *SIGKILL* deh.\n\n## Gimana Siklus *Graceful Shutdown* yang Ideal?\n\nKetika *orchestrator* kayak Kubernetes atau Docker mau mematikan container backend, ada lima tahap yang idealnya terjadi berurutan.\n\nPertama, aplikasi nerima sinyal *SIGTERM* dari OS.\n\nKedua, aplikasi nolak *traffic* baru. Status *health check* atau *readiness probe*-nya ditandai *unhealthy*, biar *load balancer* berhenti ngarahin *request* ke server ini.\n\nKetiga, *request* yang lagi *in-flight* diselesaikan. Kasih jeda (*grace period*, misalnya 10–30 detik) supaya *request* HTTP, transaksi *database*, atau proses *upload* file yang sedang berjalan bisa tuntas.\n\nKeempat, koneksi eksternal ditutup teratur. Putus *database pool* ([PostgreSQL](https://www.postgresql.org/), [MySQL](https://www.mysql.com/)), simpan state *cache* ([Redis](https://redis.io/)), dan lakukan *acknowledge*/*nack* pada antrean pesan ([RabbitMQ](https://www.rabbitmq.com/)).\n\nTerakhir, proses keluar bersih dengan *exit code* 0. Server pamit dengan baik, tanpa drama. 😎\n\n## Contoh Lifespan di FastAPI dan Uvicorn\n\nFramework modern kayak [FastAPI](https://fastapi.tiangolo.com/advanced/events/) bareng server ASGI [Uvicorn](https://www.uvicorn.org/) udah nyediain *lifespan context manager* yang elegan banget buat nangani *startup* dan *graceful shutdown*:\n\n```python\nimport asyncio\nfrom contextlib import asynccontextmanager\nfrom fastapi import FastAPI\nimport asyncpg\n\n# Variabel global untuk connection pool\ndb_pool = None\n\n@asynccontextmanager\nasync def lifespan(app: FastAPI):\n    global db_pool\n    # [TAHAP STARTUP]\n    print(\"🚀 [STARTUP] Menginisialisasi Database Connection Pool...\")\n    db_pool = await asyncpg.create_pool(\n        dsn=\"postgresql://user:***@localhost:5432/mydb\",\n        min_size=5,\n        max_size=20\n    )\n    print(\"✅ [STARTUP] Koneksi Database siap menerima traffic!\")\n\n    yield  # Aplikasi berjalan dan melayani request di sini\n\n    # [TAHAP GRACEFUL SHUTDOWN - Saat menerima SIGTERM]\n    print(\"🛑 [SHUTDOWN] Sinyal terminasi diterima! Memulai Graceful Shutdown...\")\n\n    # Beri toleransi waktu untuk request in-flight selesai\n    await asyncio.sleep(2)\n\n    # Tutup koneksi database secara teratur\n    if db_pool:\n        print(\"🔒 [SHUTDOWN] Menutup Database Connection Pool...\")\n        await db_pool.close()\n        print(\"✅ [SHUTDOWN] Seluruh koneksi DB berhasil dilepas.\")\n\n    print(\"👋 [SHUTDOWN] Aplikasi backend berhenti dengan aman.\")\n\napp = FastAPI(lifespan=lifespan)\n\n@app.get(\"/api/data\")\nasync def get_data():\n    async with db_pool.acquire() as connection:\n        return await connection.fetch(\"SELECT * FROM users LIMIT 10\")\n```\n\nSaat perintah `docker stop` atau sinyal *SIGTERM* masuk, Uvicorn otomatis berhenti nerima *request* baru, nunggu *request* aktif selesai, lalu menjalankan blok kode setelah `yield` di dalam fungsi *lifespan*.\n\n## Konfigurasi Penting di Docker dan Kubernetes\n\nBiar mekanismenya jalan optimal di lingkungan *cloud* atau container, ada beberapa hal yang perlu kalian cek.\n\nPakai *exec form* di Dockerfile. Pastikan perintah CMD-nya berbentuk JSON *array*, misalnya `CMD [\"uvicorn\", \"main:app\", \"--host\", \"0.0.0.0\", \"--port\", \"8000\"]`. Kalau kalian pakai *shell form* (`CMD uvicorn ...`), sinyal **SIGTERM** bakal nyangkut di shell `/bin/sh` dan nggak diteruskan ke aplikasi Python. Jebakan ini halus banget, lho.\n\nAtur juga `terminationGracePeriodSeconds` di Kubernetes. Default-nya 30 detik sebelum *SIGKILL* dikirim. Kalau aplikasi kalian butuh waktu lebih lama buat ngerjain *background job*, naikin nilainya—misal jadi 60 detik—di manifest Deployment.\n\nTerakhir, manfaatkan `preStop` hook. Tambahkan `sleep` (misal 5 detik) di pod container Kubernetes, supaya *load balancer* punya cukup waktu nyoret IP pod dari daftar *endpoint* aktif sebelum pod mulai mematikan prosesnya.\n\n## Jadi, Kenapa Ini Penting Banget?\n\nNulis kode fitur yang jalan barulah setengah perjalanan. Memastikan aplikasi bisa nyala dan mati dengan anggun (*graceful*) adalah kunci membangun sistem yang tangguh (*resilient*), konsisten secara data, dan bebas *downtime* saat tim kalian rilis tiap hari.\n\nSelamat ber-*devops* ria, dan semoga server kalian selalu pamit dulu sebelum tidur! 👋",[62],{"authors_id":63},{"name":64,"slug":65,"role":66,"profile_picture":67},"Inva","inva","Writer",null,{"id":69,"title":8,"slug":9,"articles":70,"parent_series":67},"9",[71,84,96,108,119,132,144,154,166,177,188,198,208,219,228,239,250,260,268,279,290,301,309,318,327,340,349,360,370,380,389,392,402],{"id":72,"title":73,"slug":74,"excerpt":75,"thumbnail_image":76,"tags":78},"41","Log Aggregation Modern dengan Grafana Loki dan Vector: Hemat Storage Tanpa Indeks Raksasa","log-aggregation-modern-grafana-loki-vector-hemat-storage","Klaster Elasticsearch kalian rakus RAM dan boros storage, ya? Padahal nggak semua kata di log perlu diindeks, lho. Yuk, kita kenalan sama duet Grafana Loki dan Vector yang jauh lebih ramah kantong!",{"id":77},"03c9d1a0-c80a-401d-9f2b-2b3ee7abb115",[51,79,80,81,82,83,52,56],"observa","logging","grafana","loki","vector",{"id":85,"title":86,"slug":87,"excerpt":88,"thumbnail_image":89,"tags":91},"45","Rate Limiting Algorithms: Token Bucket vs Leaky Bucket vs Sliding Window","rate-limiting-algorithms-token-bucket-leaky-bucket-sliding-window","Udah tahu kenapa *rate limiting* itu wajib, tapi masih bingung beda Token Bucket, Leaky Bucket, Fixed Window, dan Sliding Window? Yuk, kita adu empat algoritma ini bareng-bareng dan cari tahu mana yang paling pas buat API kalian!",{"id":90},"0e0ed26d-20c6-443c-bde1-4a6200f6f801",[51,56,92,93,94,57,95],"rate-limiting","redis","api-gateway","traffict-management",{"id":97,"title":98,"slug":99,"excerpt":100,"thumbnail_image":101,"tags":103},"16","Menggunakan TypeScript dengan Node.js dan Express","menggunakan-typescript-dengan-node-js-dan-express","Pengen bikin server Express di Node.js tapi pakai fitur-fitur keren TypeScript? Yuk, intip cara setup lengkapnya dari nol di sini!",{"id":102},"798b60f1-9ef5-4f73-8d43-85825fd86acc",[104,105,106,107],"javascript","nodejs","express","typescript",{"id":109,"title":110,"slug":111,"excerpt":112,"thumbnail_image":113,"tags":115},"17","Pemrograman Asynchronous vs Multithreading, Apa Sih Bedanya?","pemrograman-asynchronous-dan-multithreading-apa-bedanya","Sering dengar istilah asynchronous dan multithreading pas ngoding tapi masih bingung bedanya? Yuk, kita bedah perbedaannya lewat analogi bikin mi instan yang gampang dipahami!",{"id":114},"9c05d0ae-e829-4f1b-b9f7-a84f3e0439d3",[116,117,118],"pemrograman","concurrency","tips-coding",{"id":120,"title":121,"slug":122,"excerpt":123,"thumbnail_image":124,"tags":126},"33","Berkenalan dengan RabbitMQ: Si Kurir Pesan Serba Bisa","berkenalan-dengan-rabbitmq-si-kurir-pesan-serba-bisa","Pernah nggak sih kalian klik Bayar Sekarang dan notifikasi suksesnya muncul seketika, padahal email konfirmasi baru nyampe beberapa detik kemudian? Rahasianya ada di satu kurir tak terlihat. Yuk, kita kenalan sama RabbitMQ!",{"id":125},"f6620f79-b3b2-4f9c-8104-283a335e06c4",[127,128,51,129,130,131],"rabbitmq","message-broker","microservices","async","queue",{"id":133,"title":134,"slug":135,"excerpt":136,"thumbnail_image":137,"tags":139},"34","Kenapa Backend Butuh Database Connection Pooling?","kenapa-backend-butuh-database-connection-pooling","Pernah kena error Too many connections padahal CPU server masih santai di angka 30%? Masalahnya bukan di query kalian, tapi di cara aplikasi ngobrol sama database. Yuk, kenalan sama Connection Pooling!",{"id":138},"6f7a2d8c-2a37-4901-a522-50df8d9c0a20",[51,140,141,142,56,143],"database","postgresql","connection-pooling","performance",{"id":145,"title":146,"slug":147,"excerpt":148,"thumbnail_image":149,"tags":151},"27","Background Worker & Task Queue: Jangan Jalankan Proses Berat di Request HTTP!","background-worker-task-queue-jangan-jalankan-proses-berat-di-http","Pernah nggak sih kalian klik Daftar Akun lalu halaman loading muter sampai 15 detik tanpa kepastian? Penyebabnya klasik banget. Yuk, kita bahas kenapa proses berat nggak boleh dijalanin di request HTTP!",{"id":150},"e119c6ad-fc37-4b92-abdc-3eb20f8e34b4",[51,152,153,53,127,93,130],"task-queue","celery",{"id":155,"title":156,"slug":157,"excerpt":158,"thumbnail_image":159,"tags":161},"28","Mengatasi N+1 Query Problem: Musuh Tersembunyi Performa Backend","mengatasi-n-plus-1-query-problem-musuh-tersembunyi-backend","Pernah bikin endpoint yang cuma nampilin 50 postingan beserta nama penulisnya, tapi response-nya lambat banget? Bisa jadi kalian kena N+1 Query. Yuk, kita bedah penyebabnya dan cara memberantasnya!",{"id":160},"34b94e14-3e9a-4778-9f1f-6df5898915fb",[140,162,163,164,165,143,51],"sql","orm","sqlalchemy","django",{"id":167,"title":168,"slug":169,"excerpt":170,"thumbnail_image":171,"tags":173},"30","Berkenalan dengan Bahasa Go: Kenapa Banyak Dipakai untuk Backend Modern?","berkenalan-dengan-bahasa-go-untuk-backend-modern","Kok bisa sih Go yang masih muda ini jadi bahasa andalan Docker sampai Kubernetes? Yuk, kita kenalan sama Goroutine, Channel, dan alasan dia hemat memori luar biasa!",{"id":172},"a368631c-f331-4c50-8322-1d0fc44927aa",[174,175,51,117,176,56],"golang","go","goroutine",{"id":178,"title":179,"slug":180,"excerpt":181,"thumbnail_image":182,"tags":184},"13","Hal yang Perlu Diperhatikan Sebelum Pindah ke Linux","hal-yang-perlu-diperhatikan-sebelum-pindah-ke-linux","Tertarik migrasi dari Windows ke Linux tapi masih ragu? Yuk, pelajari kelebihan, kekurangan, dan persiapan penting sebelum kamu benar-benar pindah!",{"id":183},"ae27713e-5025-4d13-88b6-efb4860cc5b3",[185,186,187],"linux","windows","foss",{"id":189,"title":190,"slug":191,"excerpt":192,"thumbnail_image":193,"tags":195},"11","Apa Kabar JavaScript? Rilis State of JS 2022","apa-kabar-javascript-rilis-state-of-js-2022","Survei State of JS 2022 resmi dirilis dengan lonjakan responden yang luar biasa! Framework dan build tool apa saja yang berhasil mencuri perhatian tahun ini?",{"id":194},"18df5262-d813-43d1-b1f7-5595a7f53602",[104,196,197],"web","news",{"id":199,"title":200,"slug":201,"excerpt":202,"thumbnail_image":203,"tags":205},"12","Buat PowerShell Lebih Berwarna dengan Starship","buat-powershell-lebih-berwarna-dengan-starship","Bosen sama tampilan PowerShell yang hitam putih dan kaku? Yuk, sulap terminalmu jadi lebih interaktif, estetik, dan berwarna pakai Starship!",{"id":204},"c5a8262b-43db-4479-8f6c-5a6a0d61653b",[206,186,207],"shell","powershell",{"id":209,"title":210,"slug":211,"excerpt":212,"thumbnail_image":213,"tags":215},"14","Instalasi Java dengan Visual Studio Code","instalasi-java-dengan-visual-studio-code","Mau belajar ngoding Java tapi spek laptop pas-pasan buat buka IDE berat? Yuk, cari tahu cara setup VS Code biar ngoding Java tetap lancar dan enteng!",{"id":214},"99b01cc2-11ac-4449-9927-a1a7116347df",[216,217,218],"howto","java","editor",{"id":220,"title":221,"slug":222,"excerpt":223,"thumbnail_image":224,"tags":226},"15","Kenapa Ada Banyak Sekali Distro Linux?","kenapa-ada-banyak-sekali-distro-linux","Pernah bingung pas mau install Linux tapi malah disuguhi puluhan pilihan distro? Tenang, kalian nggak sendirian. Yuk, cari tahu kenapa distro Linux bisa sebanyak itu dan apa bedanya!",{"id":225},"b5352a4b-f274-4489-aca9-36814947d514",[185,227],"distro",{"id":229,"title":230,"slug":231,"excerpt":232,"thumbnail_image":233,"tags":235},"18","React, Angular, atau Vue: Pilih Framework yang Mana?","react-angular-vue-pilih-framework-yang-mana","Bingung menentukan pilihan di antara React, Angular, dan Vue untuk proyek web kalian berikutnya? Tenang, yuk kita bandingkan kelebihan masing-masing di sini!",{"id":234},"ff111270-80c2-4ccb-83d7-d5ab8c021201",[236,237,238],"web-development","frontend","framework",{"id":240,"title":241,"slug":242,"excerpt":243,"thumbnail_image":244,"tags":246},"19","Static Typing dan Dynamic Typing: Apa Bedanya?","static-typing-dan-dynamic-typing-apa-bedanya","Pernah bingung kenapa di Java tipe data harus dideklarasikan, sementara di Python tinggal pakai aja? Yuk, cari tahu perbedaan static typing dan dynamic typing di sini!",{"id":245},"98e85e76-9e7b-42d1-b989-7c75e7f49abc",[247,248,249],"programming","types","comparison",{"id":251,"title":252,"slug":253,"excerpt":254,"thumbnail_image":255,"tags":257},"20","Tailwind v3.0 Rilis: Ada JIT, Arbitrary Values, dan Banyak Lagi!","tailwind-v3-0-rilis-jit-arbitrary-dan-banyak-lagi","Tailwind CSS v3.0 resmi dirilis dengan segudang peningkatan performa yang bikin proses coding makin asyik. Apa aja sih fitur andalan yang wajib dicoba?",{"id":256},"d5e879fa-5cd0-4015-a155-b0cc69ff12fb",[258,259,236],"tailwind-css","css-framework",{"id":261,"title":262,"slug":263,"excerpt":264,"thumbnail_image":265,"tags":267},"21","TypeScript: JavaScript dengan Gaya dan Tipe Data Statis","typescript-javascript-dengan-gaya","Pernah pusing gara-gara runtime error di JavaScript? Yuk, kenalan dengan TypeScript yang bawa fitur static typing biar kode kalian makin rapi dan aman!",{"id":266},"f615bb1f-8e36-4d6c-9c2c-f1629407173c",[107,104,236],{"id":269,"title":270,"slug":271,"excerpt":272,"thumbnail_image":273,"tags":275},"22","Yang Baru di Nuxt 3: Nitro Engine, Vite, dan Fitur Keren Lainnya","yang-baru-di-nuxt-3-nitro-vite-dan-banyak-lagi","Nuxt 3 hadir membawa perubahan arsitektur besar-besaran untuk menyelaraskan dengan Vue 3. Penasaran apa saja peningkatan performa dan fitur barunya?",{"id":274},"8444bdbc-f60c-4d8b-8593-1b49400e8659",[276,277,278],"nuxt-3","vue-3","frontend-framework",{"id":280,"title":281,"slug":282,"excerpt":283,"thumbnail_image":284,"tags":286},"23","Kenapa Pakai FastAPI dan Kenapa Dia Kenceng Banget?","kenapa-pakai-fastapi-dan-kenapa-dia-kenceng-banget","Sering dengar FastAPI tapi masih bingung kenapa dia bisa ngebut kayak NodeJS dan Go? Yuk, kita bedah bareng rahasia ASGI, sihir Pydantic, sampai dokumentasi otomatisnya!",{"id":285},"84847c9e-70ab-4dcc-bed7-7be50165f7f4",[53,287,51,288,289],"python","asgi","pydantic",{"id":291,"title":292,"slug":293,"excerpt":294,"thumbnail_image":295,"tags":297},"26","REST API vs gRPC: Kapan Sebaiknya Mulai Pindah dari JSON?","rest-api-vs-grpc-kapan-sebaiknya-pindah-dari-json","Pernah nggak sih sistem mikroservis kalian mulai kerasa berat padahal cuma tuker-tukeran data internal? Belum tentu masalah servernya. Yuk, kita bahas kapan REST + JSON masih juara dan kapan gRPC jadi jawabannya!",{"id":296},"487500a0-9e09-469d-8736-1583c5ea83aa",[51,298,299,129,300,56],"grpc","rest-api","protobuf",{"id":302,"title":303,"slug":304,"excerpt":305,"thumbnail_image":306,"tags":308},"38","Optimistic vs Pessimistic Locking: Mengatasi Rebutan Data di Database","optimistic-vs-pessimistic-locking-mengatasi-rebutan-data-di-database","Seribu orang ngeklik \"Beli Sekarang\" di detik yang sama buat rebutan 1 tiket terakhir. Kira-kira apa yang bakal terjadi di server kalian? Yuk, kita banding *pessimistic* sama *optimistic locking*!",{"id":307},"21ab769d-6f82-4a22-be11-17ac16e9fb6b",[51,140,117,141,56,57,162],{"id":310,"title":311,"slug":312,"excerpt":313,"thumbnail_image":314,"tags":316},"24","Kenapa Butuh Rate Limiting?","kenapa-butuh-rate-limiting","Pernah nggak sih endpoint login kalian diserbu bot yang nyoba nembak ribuan password cuma dalam semenit? Yuk, kita bahas kenapa Rate Limiting itu wajib, plus cara masangnya di FastAPI!",{"id":315},"1401f9e5-6359-404a-8d80-273ddee9a372",[51,92,56,317,93,53],"api",{"id":319,"title":320,"slug":321,"excerpt":322,"thumbnail_image":323,"tags":325},"25","Kenapa Event Queue Bikin Backend Kalian Nggak Gampang Tumbang?","kenapa-event-queue-bikin-backend-kamu-nggak-gampang-tumbang","Pernah klik tombol Beli Sekarang dan notifikasi suksesnya muncul dalam sekejap, padahal di belakang layar ada invoice, email, sampai push notification yang harus dibuat? Rahasianya Event Queue. Yuk, kita bedah!",{"id":324},"d9e76018-fbcc-4c69-ad42-8f75ff229ecd",[51,56,326,128,57],"event-queue",{"id":328,"title":329,"slug":330,"excerpt":331,"thumbnail_image":332,"tags":334},"46","Mengapa C Mulai Ditinggalkan: Duel Filosofi Keamanan Rust vs Kesederhanaan Zig","mengapa-c-mulai-ditinggalkan-duel-filosofi-rust-vs-zig","Pernah denger kalau sekitar 70% celah keamanan kritis software modern itu asalnya dari bahasa C? Iya, bahasa yang udah jadi fondasi internet ini 😅. Yuk, kita bedah duel filosofi Rust vs Zig dan cari tahu mana yang pas buat proyek kalian!",{"id":333},"1942a5c9-c1f6-476d-9913-768f78d9d8eb",[335,336,337,338,339],"system-programming","rust","zig","c","memory-safety",{"id":341,"title":342,"slug":343,"excerpt":344,"thumbnail_image":345,"tags":347},"29","Memahami Database Indexing: Rahasia Query Super Cepat","memahami-database-indexing-rahasia-query-super-cepat","Query kalian mulai lelet padahal data baru nembus jutaan baris? Sebelum buru-buru *upgrade* server, yuk cek dulu *index*-nya. Yuk, kita bedah gimana *database indexing* sebenernya kerja!",{"id":346},"b123036f-1779-478c-a545-cf5f189b5fe9",[140,162,141,348,143,51],"indexing",{"id":350,"title":351,"slug":352,"excerpt":353,"thumbnail_image":354,"tags":356},"31","Mengenal Redis: Lebih dari Sekadar In-Memory Cache","mengenal-redis-lebih-dari-sekadar-in-memory-cache","Masih nganggep Redis cuma buat caching? Padahal dia bisa jadi leaderboard, message broker, sampai rate limiter lho. Yuk, kita bedah semua kemampuannya!",{"id":355},"9595b7d7-60e0-48f5-a715-f3cf60f34e1d",[93,51,357,358,359,287],"cache","nosql","in-memory",{"id":361,"title":362,"slug":363,"excerpt":364,"thumbnail_image":365,"tags":367},"32","Docker Compose untuk Developer Santai: Satu Perintah Buat Jalankan Semua Service","docker-compose-untuk-developer-santai","Pernah nggak kalian ngulang-ngulang perintah `docker run` cuma buat nyalain web, database, dan cache satu-satu? Capek, kan? Yuk, kita rapikan semuanya jadi satu file dan satu perintah!",{"id":366},"f4c08f1b-e0d0-410c-b091-c3618944fb3e",[54,368,52,369,51],"docker-compose","containers",{"id":371,"title":372,"slug":373,"excerpt":374,"thumbnail_image":375,"tags":377},"35","Mengenal Idempotency Key: Rahasia Anti-Double Charge di API Pembayaran","mengenal-idempotency-key-rahasia-anti-double-charge-di-api-pembayaran","Pernah internet kalian ngadat pas lagi nekan tombol Bayar, terus panik ngekliknya tiga kali? Kalau endpoint-nya nggak idempotent, saldo bisa kepotong berkali-kali. Yuk, kenalan sama Idempotency Key!",{"id":376},"724cb83a-3ce5-4ee2-b0d7-533e3a0fc7df",[51,317,378,56,379,53,93],"idempotency","payment",{"id":381,"title":382,"slug":383,"excerpt":384,"thumbnail_image":385,"tags":387},"36","Mencegah Efek Domino di Mikroservis dengan Circuit Breaker Pattern","mencegah-efek-domino-di-mikroservis-dengan-circuit-breaker-pattern","Pernah nggak sih, satu fitur minor di aplikasi kalian mendadak lelet, eh malah bikin halaman checkout dan login ikut down total? Itu namanya *cascading failure*. Yuk, kita bahas gimana *circuit breaker pattern* (pemutus arus) nyelametin arsitektur kalian!",{"id":386},"c2e8e37f-8f9a-423f-a09d-74613b3c2924",[51,129,388,56,57],"circuit-breaker",{"id":43,"title":44,"slug":45,"excerpt":46,"thumbnail_image":390,"tags":391},{"id":49},[51,52,53,54,55,56,57],{"id":393,"title":394,"slug":395,"excerpt":396,"thumbnail_image":397,"tags":399},"39","Database Sharding vs Partitioning: Kapan Data Perlu Dipecah?","database-sharding-vs-partitioning-kapan-data-perlu-dipecah","Tabel transaksi kalian udah nembus miliaran baris dan tiap *query* laporan bikin *CPU* melonjak 100%? Sebelum asal pecah data, yuk kita pahami dulu beda *sharding* sama *partitioning*!",{"id":398},"08ef5fe5-d935-47b3-bbbc-d976948b2a9e",[51,140,141,56,57,400,401],"sharding","scaling",{"id":403,"title":404,"slug":405,"excerpt":406,"thumbnail_image":407,"tags":409},"40","Menyelami Distributed Tracing: Melacak Jejak Request di Balik Keruwetan Microservices","menyelami-distributed-tracing-melacak-jejak-request-microservices","Satu klik Checkout di backend kalian bisa memicu puluhan network call antar-service, tapi pas ada yang lambat, service mana sebenernya yang salah? Log aja nggak cukup buat njawab itu. Yuk, kita bedah Distributed Tracing!",{"id":408},"1ace92fa-b89c-4cef-ab75-4e4cd67a089c",[51,410,411,412,129,57,413],"distributed-systems","observability","open-telemetry","tracing","\u003Cp>Baru aja kalian selesai nge-\u003Cem>deploy\u003C/em> versi terbaru backend ke server. Eh, beberapa detik kemudian channel monitoring malah banjir \u003Cem>alert\u003C/em> \u003Cstrong>502 Bad Gateway\u003C/strong> dan \u003Cem>Connection Reset by Peer\u003C/em> dari pengguna. 😅\u003C/p>\n\u003Cp>Setelah dicek, ternyata ada transaksi checkout yang gagal di tengah jalan. Saldo udah kepotong di \u003Cem>payment gateway\u003C/em>, tapi status order-nya belum sempat ter-\u003Cem>update\u003C/em> di \u003Cem>database\u003C/em>!\u003C/p>\n\u003Cp>Biang keroknya sering banget sepele: proses server lama dimatikan mendadak alias \u003Cem>un-graceful shutdown\u003C/em>. Kita asal tebas proses aja, tanpa nawarin pamit dulu.\u003C/p>\n\u003Cp>Ibaratnya kayak kalian lagi makan malam di restoran. Kalau tepat jam 22.00 manajer langsung matiin lampu, ngunci pintu, dan ngusir pengunjung yang makanannya baru setengah tersaji, pasti kalian kesel banget, kan? Nah, itu versi paksa.\u003C/p>\n\u003Cp>Versi beradabnya beda. Jam 21.30 staf udah mengumumkan \u003Cem>&quot;last order&quot;\u003C/em> dan nggak nerima tamu baru. Tapi yang udah duduk di dalam tetap dipersilakan menikmati hidangan sampai tuntas. Baru setelah semua meja kosong dan kasir nutup pembukuan, pintunya dikunci rapi.\u003C/p>\n\u003Cp>Di dunia \u003Cem>software\u003C/em>, \u003Cem>graceful shutdown\u003C/em> adalah etika server buat menyelesaikan semua pekerjaan yang sedang berjalan (\u003Cem>in-flight requests\u003C/em>) sebelum benar-benar mematikan prosesnya. Kalau langkah ini dilewatin, semua koneksi HTTP yang lagi berlangsung langsung putus di tengah jalan, transaksi \u003Cem>database\u003C/em> menggantung, dan \u003Cem>connection pool\u003C/em> pun bocor (\u003Cem>leak\u003C/em>).\u003C/p>\n\u003Cp>Agar backend kalian bisa diperbarui kapan aja tanpa bikin pengguna kena error, mekanisme ini wajib dipasang. Yuk, kita kupas tuntas cara kerjanya!\u003C/p>\n\u003Ch2 id=\"mengenal-sinyal-unix-sigint-sigterm-dan-sigkill\">Mengenal Sinyal Unix: SIGINT, SIGTERM, dan SIGKILL\u003C/h2>\n\u003Cp>Sistem operasi—termasuk \u003Ca href=\"https://docs.docker.com/\">Docker\u003C/a> dan Kubernetes—ngobrol sama aplikasi backend lewat sinyal standar POSIX.\u003C/p>\n\u003Cp>\u003Cem>SIGINT\u003C/em> dikirim pas kalian nekan Ctrl + C di terminal. Aplikasi biasanya merespons dengan menghentikan eksekusi secara ramah.\u003C/p>\n\u003Cp>\u003Cem>SIGTERM\u003C/em> ini yang paling sering muncul di produksi. Docker (\u003Ccode>docker stop\u003C/code>) atau Kubernetes mengirimnya saat \u003Cem>rolling update\u003C/em> atau \u003Cem>scale down\u003C/em> pod. Pesannya kira-kira: \u003Cem>&quot;Tolong siap-siap berhenti, selesaikan tugas yang sedang aktif!&quot;\u003C/em>\u003C/p>\n\u003Cp>\u003Cem>SIGKILL\u003C/em> (sinyal 9) adalah pamungkas yang nggak bisa ditolak atau ditangkap (\u003Cem>uninterceptable\u003C/em>) oleh aplikasi. Kernel langsung memutus proses secara instan. Kalau aplikasi nggak kunjung kelar dalam batas \u003Cem>grace period\u003C/em>, sistem bakal nembak \u003Cem>SIGKILL\u003C/em> deh.\u003C/p>\n\u003Ch2 id=\"gimana-siklus-graceful-shutdown-yang-ideal\">Gimana Siklus \u003Cem>Graceful Shutdown\u003C/em> yang Ideal?\u003C/h2>\n\u003Cp>Ketika \u003Cem>orchestrator\u003C/em> kayak Kubernetes atau Docker mau mematikan container backend, ada lima tahap yang idealnya terjadi berurutan.\u003C/p>\n\u003Cp>Pertama, aplikasi nerima sinyal \u003Cem>SIGTERM\u003C/em> dari OS.\u003C/p>\n\u003Cp>Kedua, aplikasi nolak \u003Cem>traffic\u003C/em> baru. Status \u003Cem>health check\u003C/em> atau \u003Cem>readiness probe\u003C/em>-nya ditandai \u003Cem>unhealthy\u003C/em>, biar \u003Cem>load balancer\u003C/em> berhenti ngarahin \u003Cem>request\u003C/em> ke server ini.\u003C/p>\n\u003Cp>Ketiga, \u003Cem>request\u003C/em> yang lagi \u003Cem>in-flight\u003C/em> diselesaikan. Kasih jeda (\u003Cem>grace period\u003C/em>, misalnya 10–30 detik) supaya \u003Cem>request\u003C/em> HTTP, transaksi \u003Cem>database\u003C/em>, atau proses \u003Cem>upload\u003C/em> file yang sedang berjalan bisa tuntas.\u003C/p>\n\u003Cp>Keempat, koneksi eksternal ditutup teratur. Putus \u003Cem>database pool\u003C/em> (\u003Ca href=\"https://www.postgresql.org/\">PostgreSQL\u003C/a>, \u003Ca href=\"https://www.mysql.com/\">MySQL\u003C/a>), simpan state \u003Cem>cache\u003C/em> (\u003Ca href=\"https://redis.io/\">Redis\u003C/a>), dan lakukan \u003Cem>acknowledge\u003C/em>/\u003Cem>nack\u003C/em> pada antrean pesan (\u003Ca href=\"https://www.rabbitmq.com/\">RabbitMQ\u003C/a>).\u003C/p>\n\u003Cp>Terakhir, proses keluar bersih dengan \u003Cem>exit code\u003C/em> 0. Server pamit dengan baik, tanpa drama. 😎\u003C/p>\n\u003Ch2 id=\"contoh-lifespan-di-fastapi-dan-uvicorn\">Contoh Lifespan di FastAPI dan Uvicorn\u003C/h2>\n\u003Cp>Framework modern kayak \u003Ca href=\"https://fastapi.tiangolo.com/advanced/events/\">FastAPI\u003C/a> bareng server ASGI \u003Ca href=\"https://www.uvicorn.org/\">Uvicorn\u003C/a> udah nyediain \u003Cem>lifespan context manager\u003C/em> yang elegan banget buat nangani \u003Cem>startup\u003C/em> dan \u003Cem>graceful shutdown\u003C/em>:\u003C/p>\n\n\u003Cdiv class=\"code-block-wrapper my-6 not-prose rounded-xl border-2 border-black dark:border-gray-600 shadow-neo overflow-hidden bg-[#24292e] text-[#e1e4e8] transition-all\">\n  \u003Cdiv class=\"code-block-header flex items-center justify-between px-4 py-2.5 bg-[#1f2428] border-b-2 border-black dark:border-gray-600 font-mono text-xs font-bold text-gray-300 select-none\">\n    \u003Cdiv class=\"flex items-center gap-2\">\n      \u003Cspan class=\"w-3 h-3 rounded-full bg-[#ff5f56] border border-black/40 inline-block\">\u003C/span>\n      \u003Cspan class=\"w-3 h-3 rounded-full bg-[#ffbd2e] border border-black/40 inline-block\">\u003C/span>\n      \u003Cspan class=\"w-3 h-3 rounded-full bg-[#27c93f] border border-black/40 inline-block\">\u003C/span>\n      \u003Cspan class=\"ml-2 font-mono font-bold text-xs uppercase tracking-wider text-gray-300\">PYTHON\u003C/span>\n    \u003C/div>\n    \u003Cbutton type=\"button\" class=\"copy-code-btn flex items-center gap-1.5 px-3 py-1 text-xs font-bold bg-[#2f363d] text-gray-200 border-2 border-black dark:border-gray-500 rounded-lg shadow-neo-sm hover:translate-x-0.5 hover:translate-y-0.5 hover:shadow-none hover:bg-gray-700 transition-all cursor-pointer\" data-code=\"import%20asyncio%0Afrom%20contextlib%20import%20asynccontextmanager%0Afrom%20fastapi%20import%20FastAPI%0Aimport%20asyncpg%0A%0A%23%20Variabel%20global%20untuk%20connection%20pool%0Adb_pool%20%3D%20None%0A%0A%40asynccontextmanager%0Aasync%20def%20lifespan(app%3A%20FastAPI)%3A%0A%20%20%20%20global%20db_pool%0A%20%20%20%20%23%20%5BTAHAP%20STARTUP%5D%0A%20%20%20%20print(%22%F0%9F%9A%80%20%5BSTARTUP%5D%20Menginisialisasi%20Database%20Connection%20Pool...%22)%0A%20%20%20%20db_pool%20%3D%20await%20asyncpg.create_pool(%0A%20%20%20%20%20%20%20%20dsn%3D%22postgresql%3A%2F%2Fuser%3A***%40localhost%3A5432%2Fmydb%22%2C%0A%20%20%20%20%20%20%20%20min_size%3D5%2C%0A%20%20%20%20%20%20%20%20max_size%3D20%0A%20%20%20%20)%0A%20%20%20%20print(%22%E2%9C%85%20%5BSTARTUP%5D%20Koneksi%20Database%20siap%20menerima%20traffic!%22)%0A%0A%20%20%20%20yield%20%20%23%20Aplikasi%20berjalan%20dan%20melayani%20request%20di%20sini%0A%0A%20%20%20%20%23%20%5BTAHAP%20GRACEFUL%20SHUTDOWN%20-%20Saat%20menerima%20SIGTERM%5D%0A%20%20%20%20print(%22%F0%9F%9B%91%20%5BSHUTDOWN%5D%20Sinyal%20terminasi%20diterima!%20Memulai%20Graceful%20Shutdown...%22)%0A%0A%20%20%20%20%23%20Beri%20toleransi%20waktu%20untuk%20request%20in-flight%20selesai%0A%20%20%20%20await%20asyncio.sleep(2)%0A%0A%20%20%20%20%23%20Tutup%20koneksi%20database%20secara%20teratur%0A%20%20%20%20if%20db_pool%3A%0A%20%20%20%20%20%20%20%20print(%22%F0%9F%94%92%20%5BSHUTDOWN%5D%20Menutup%20Database%20Connection%20Pool...%22)%0A%20%20%20%20%20%20%20%20await%20db_pool.close()%0A%20%20%20%20%20%20%20%20print(%22%E2%9C%85%20%5BSHUTDOWN%5D%20Seluruh%20koneksi%20DB%20berhasil%20dilepas.%22)%0A%0A%20%20%20%20print(%22%F0%9F%91%8B%20%5BSHUTDOWN%5D%20Aplikasi%20backend%20berhenti%20dengan%20aman.%22)%0A%0Aapp%20%3D%20FastAPI(lifespan%3Dlifespan)%0A%0A%40app.get(%22%2Fapi%2Fdata%22)%0Aasync%20def%20get_data()%3A%0A%20%20%20%20async%20with%20db_pool.acquire()%20as%20connection%3A%0A%20%20%20%20%20%20%20%20return%20await%20connection.fetch(%22SELECT%20*%20FROM%20users%20LIMIT%2010%22)\" title=\"Salin kode\">\n      \u003Csvg class=\"w-3.5 h-3.5 copy-icon-svg\" fill=\"none\" stroke=\"currentColor\" viewBox=\"0 0 24 24\">\n        \u003Cpath stroke-linecap=\"round\" stroke-linejoin=\"round\" stroke-width=\"2\" d=\"M8 16H6a2 2 0 01-2-2V6a2 2 0 012-2h8a2 2 0 012 2v2m-6 12h8a2 2 0 002-2v-8a2 2 0 00-2-2h-8a2 2 0 00-2 2v8a2 2 0 002 2z\">\u003C/path>\n      \u003C/svg>\n      \u003Cspan class=\"copy-text\">Copy\u003C/span>\n    \u003C/button>\n  \u003C/div>\n  \u003Cdiv class=\"code-block-content p-4 overflow-x-auto text-sm font-mono leading-relaxed bg-[#24292e]\">\n    \u003Cpre class=\"shiki github-dark\" style=\"background-color:#24292e;color:#e1e4e8\" tabindex=\"0\">\u003Ccode>\u003Cspan class=\"line\">\u003Cspan style=\"color:#F97583\">import\u003C/span>\u003Cspan style=\"color:#E1E4E8\"> asyncio\u003C/span>\u003C/span>\n\u003Cspan class=\"line\">\u003Cspan style=\"color:#F97583\">from\u003C/span>\u003Cspan style=\"color:#E1E4E8\"> contextlib \u003C/span>\u003Cspan style=\"color:#F97583\">import\u003C/span>\u003Cspan style=\"color:#E1E4E8\"> asynccontextmanager\u003C/span>\u003C/span>\n\u003Cspan class=\"line\">\u003Cspan style=\"color:#F97583\">from\u003C/span>\u003Cspan style=\"color:#E1E4E8\"> fastapi \u003C/span>\u003Cspan style=\"color:#F97583\">import\u003C/span>\u003Cspan style=\"color:#E1E4E8\"> FastAPI\u003C/span>\u003C/span>\n\u003Cspan class=\"line\">\u003Cspan style=\"color:#F97583\">import\u003C/span>\u003Cspan style=\"color:#E1E4E8\"> asyncpg\u003C/span>\u003C/span>\n\u003Cspan class=\"line\">\u003C/span>\n\u003Cspan class=\"line\">\u003Cspan style=\"color:#6A737D\"># Variabel global untuk connection pool\u003C/span>\u003C/span>\n\u003Cspan class=\"line\">\u003Cspan style=\"color:#E1E4E8\">db_pool \u003C/span>\u003Cspan style=\"color:#F97583\">=\u003C/span>\u003Cspan style=\"color:#79B8FF\"> None\u003C/span>\u003C/span>\n\u003Cspan class=\"line\">\u003C/span>\n\u003Cspan class=\"line\">\u003Cspan style=\"color:#B392F0\">@asynccontextmanager\u003C/span>\u003C/span>\n\u003Cspan class=\"line\">\u003Cspan style=\"color:#F97583\">async\u003C/span>\u003Cspan style=\"color:#F97583\"> def\u003C/span>\u003Cspan style=\"color:#B392F0\"> lifespan\u003C/span>\u003Cspan style=\"color:#E1E4E8\">(app: FastAPI):\u003C/span>\u003C/span>\n\u003Cspan class=\"line\">\u003Cspan style=\"color:#F97583\">    global\u003C/span>\u003Cspan style=\"color:#E1E4E8\"> db_pool\u003C/span>\u003C/span>\n\u003Cspan class=\"line\">\u003Cspan style=\"color:#6A737D\">    # [TAHAP STARTUP]\u003C/span>\u003C/span>\n\u003Cspan class=\"line\">\u003Cspan style=\"color:#79B8FF\">    print\u003C/span>\u003Cspan style=\"color:#E1E4E8\">(\u003C/span>\u003Cspan style=\"color:#9ECBFF\">\"🚀 [STARTUP] Menginisialisasi Database Connection Pool...\"\u003C/span>\u003Cspan style=\"color:#E1E4E8\">)\u003C/span>\u003C/span>\n\u003Cspan class=\"line\">\u003Cspan style=\"color:#E1E4E8\">    db_pool \u003C/span>\u003Cspan style=\"color:#F97583\">=\u003C/span>\u003Cspan style=\"color:#F97583\"> await\u003C/span>\u003Cspan style=\"color:#E1E4E8\"> asyncpg.create_pool(\u003C/span>\u003C/span>\n\u003Cspan class=\"line\">\u003Cspan style=\"color:#FFAB70\">        dsn\u003C/span>\u003Cspan style=\"color:#F97583\">=\u003C/span>\u003Cspan style=\"color:#9ECBFF\">\"postgresql://user:***@localhost:5432/mydb\"\u003C/span>\u003Cspan style=\"color:#E1E4E8\">,\u003C/span>\u003C/span>\n\u003Cspan class=\"line\">\u003Cspan style=\"color:#FFAB70\">        min_size\u003C/span>\u003Cspan style=\"color:#F97583\">=\u003C/span>\u003Cspan style=\"color:#79B8FF\">5\u003C/span>\u003Cspan style=\"color:#E1E4E8\">,\u003C/span>\u003C/span>\n\u003Cspan class=\"line\">\u003Cspan style=\"color:#FFAB70\">        max_size\u003C/span>\u003Cspan style=\"color:#F97583\">=\u003C/span>\u003Cspan style=\"color:#79B8FF\">20\u003C/span>\u003C/span>\n\u003Cspan class=\"line\">\u003Cspan style=\"color:#E1E4E8\">    )\u003C/span>\u003C/span>\n\u003Cspan class=\"line\">\u003Cspan style=\"color:#79B8FF\">    print\u003C/span>\u003Cspan style=\"color:#E1E4E8\">(\u003C/span>\u003Cspan style=\"color:#9ECBFF\">\"✅ [STARTUP] Koneksi Database siap menerima traffic!\"\u003C/span>\u003Cspan style=\"color:#E1E4E8\">)\u003C/span>\u003C/span>\n\u003Cspan class=\"line\">\u003C/span>\n\u003Cspan class=\"line\">\u003Cspan style=\"color:#F97583\">    yield\u003C/span>\u003Cspan style=\"color:#6A737D\">  # Aplikasi berjalan dan melayani request di sini\u003C/span>\u003C/span>\n\u003Cspan class=\"line\">\u003C/span>\n\u003Cspan class=\"line\">\u003Cspan style=\"color:#6A737D\">    # [TAHAP GRACEFUL SHUTDOWN - Saat menerima SIGTERM]\u003C/span>\u003C/span>\n\u003Cspan class=\"line\">\u003Cspan style=\"color:#79B8FF\">    print\u003C/span>\u003Cspan style=\"color:#E1E4E8\">(\u003C/span>\u003Cspan style=\"color:#9ECBFF\">\"🛑 [SHUTDOWN] Sinyal terminasi diterima! Memulai Graceful Shutdown...\"\u003C/span>\u003Cspan style=\"color:#E1E4E8\">)\u003C/span>\u003C/span>\n\u003Cspan class=\"line\">\u003C/span>\n\u003Cspan class=\"line\">\u003Cspan style=\"color:#6A737D\">    # Beri toleransi waktu untuk request in-flight selesai\u003C/span>\u003C/span>\n\u003Cspan class=\"line\">\u003Cspan style=\"color:#F97583\">    await\u003C/span>\u003Cspan style=\"color:#E1E4E8\"> asyncio.sleep(\u003C/span>\u003Cspan style=\"color:#79B8FF\">2\u003C/span>\u003Cspan style=\"color:#E1E4E8\">)\u003C/span>\u003C/span>\n\u003Cspan class=\"line\">\u003C/span>\n\u003Cspan class=\"line\">\u003Cspan style=\"color:#6A737D\">    # Tutup koneksi database secara teratur\u003C/span>\u003C/span>\n\u003Cspan class=\"line\">\u003Cspan style=\"color:#F97583\">    if\u003C/span>\u003Cspan style=\"color:#E1E4E8\"> db_pool:\u003C/span>\u003C/span>\n\u003Cspan class=\"line\">\u003Cspan style=\"color:#79B8FF\">        print\u003C/span>\u003Cspan style=\"color:#E1E4E8\">(\u003C/span>\u003Cspan style=\"color:#9ECBFF\">\"🔒 [SHUTDOWN] Menutup Database Connection Pool...\"\u003C/span>\u003Cspan style=\"color:#E1E4E8\">)\u003C/span>\u003C/span>\n\u003Cspan class=\"line\">\u003Cspan style=\"color:#F97583\">        await\u003C/span>\u003Cspan style=\"color:#E1E4E8\"> db_pool.close()\u003C/span>\u003C/span>\n\u003Cspan class=\"line\">\u003Cspan style=\"color:#79B8FF\">        print\u003C/span>\u003Cspan style=\"color:#E1E4E8\">(\u003C/span>\u003Cspan style=\"color:#9ECBFF\">\"✅ [SHUTDOWN] Seluruh koneksi DB berhasil dilepas.\"\u003C/span>\u003Cspan style=\"color:#E1E4E8\">)\u003C/span>\u003C/span>\n\u003Cspan class=\"line\">\u003C/span>\n\u003Cspan class=\"line\">\u003Cspan style=\"color:#79B8FF\">    print\u003C/span>\u003Cspan style=\"color:#E1E4E8\">(\u003C/span>\u003Cspan style=\"color:#9ECBFF\">\"👋 [SHUTDOWN] Aplikasi backend berhenti dengan aman.\"\u003C/span>\u003Cspan style=\"color:#E1E4E8\">)\u003C/span>\u003C/span>\n\u003Cspan class=\"line\">\u003C/span>\n\u003Cspan class=\"line\">\u003Cspan style=\"color:#E1E4E8\">app \u003C/span>\u003Cspan style=\"color:#F97583\">=\u003C/span>\u003Cspan style=\"color:#E1E4E8\"> FastAPI(\u003C/span>\u003Cspan style=\"color:#FFAB70\">lifespan\u003C/span>\u003Cspan style=\"color:#F97583\">=\u003C/span>\u003Cspan style=\"color:#E1E4E8\">lifespan)\u003C/span>\u003C/span>\n\u003Cspan class=\"line\">\u003C/span>\n\u003Cspan class=\"line\">\u003Cspan style=\"color:#B392F0\">@app.get\u003C/span>\u003Cspan style=\"color:#E1E4E8\">(\u003C/span>\u003Cspan style=\"color:#9ECBFF\">\"/api/data\"\u003C/span>\u003Cspan style=\"color:#E1E4E8\">)\u003C/span>\u003C/span>\n\u003Cspan class=\"line\">\u003Cspan style=\"color:#F97583\">async\u003C/span>\u003Cspan style=\"color:#F97583\"> def\u003C/span>\u003Cspan style=\"color:#B392F0\"> get_data\u003C/span>\u003Cspan style=\"color:#E1E4E8\">():\u003C/span>\u003C/span>\n\u003Cspan class=\"line\">\u003Cspan style=\"color:#F97583\">    async\u003C/span>\u003Cspan style=\"color:#F97583\"> with\u003C/span>\u003Cspan style=\"color:#E1E4E8\"> db_pool.acquire() \u003C/span>\u003Cspan style=\"color:#F97583\">as\u003C/span>\u003Cspan style=\"color:#E1E4E8\"> connection:\u003C/span>\u003C/span>\n\u003Cspan class=\"line\">\u003Cspan style=\"color:#F97583\">        return\u003C/span>\u003Cspan style=\"color:#F97583\"> await\u003C/span>\u003Cspan style=\"color:#E1E4E8\"> connection.fetch(\u003C/span>\u003Cspan style=\"color:#9ECBFF\">\"SELECT * FROM users LIMIT 10\"\u003C/span>\u003Cspan style=\"color:#E1E4E8\">)\u003C/span>\u003C/span>\u003C/code>\u003C/pre>\n  \u003C/div>\n\u003C/div>\u003Cp>Saat perintah \u003Ccode>docker stop\u003C/code> atau sinyal \u003Cem>SIGTERM\u003C/em> masuk, Uvicorn otomatis berhenti nerima \u003Cem>request\u003C/em> baru, nunggu \u003Cem>request\u003C/em> aktif selesai, lalu menjalankan blok kode setelah \u003Ccode>yield\u003C/code> di dalam fungsi \u003Cem>lifespan\u003C/em>.\u003C/p>\n\u003Ch2 id=\"konfigurasi-penting-di-docker-dan-kubernetes\">Konfigurasi Penting di Docker dan Kubernetes\u003C/h2>\n\u003Cp>Biar mekanismenya jalan optimal di lingkungan \u003Cem>cloud\u003C/em> atau container, ada beberapa hal yang perlu kalian cek.\u003C/p>\n\u003Cp>Pakai \u003Cem>exec form\u003C/em> di Dockerfile. Pastikan perintah CMD-nya berbentuk JSON \u003Cem>array\u003C/em>, misalnya \u003Ccode>CMD [&quot;uvicorn&quot;, &quot;main:app&quot;, &quot;--host&quot;, &quot;0.0.0.0&quot;, &quot;--port&quot;, &quot;8000&quot;]\u003C/code>. Kalau kalian pakai \u003Cem>shell form\u003C/em> (\u003Ccode>CMD uvicorn ...\u003C/code>), sinyal \u003Cstrong>SIGTERM\u003C/strong> bakal nyangkut di shell \u003Ccode>/bin/sh\u003C/code> dan nggak diteruskan ke aplikasi Python. Jebakan ini halus banget, lho.\u003C/p>\n\u003Cp>Atur juga \u003Ccode>terminationGracePeriodSeconds\u003C/code> di Kubernetes. Default-nya 30 detik sebelum \u003Cem>SIGKILL\u003C/em> dikirim. Kalau aplikasi kalian butuh waktu lebih lama buat ngerjain \u003Cem>background job\u003C/em>, naikin nilainya—misal jadi 60 detik—di manifest Deployment.\u003C/p>\n\u003Cp>Terakhir, manfaatkan \u003Ccode>preStop\u003C/code> hook. Tambahkan \u003Ccode>sleep\u003C/code> (misal 5 detik) di pod container Kubernetes, supaya \u003Cem>load balancer\u003C/em> punya cukup waktu nyoret IP pod dari daftar \u003Cem>endpoint\u003C/em> aktif sebelum pod mulai mematikan prosesnya.\u003C/p>\n\u003Ch2 id=\"jadi-kenapa-ini-penting-banget\">Jadi, Kenapa Ini Penting Banget?\u003C/h2>\n\u003Cp>Nulis kode fitur yang jalan barulah setengah perjalanan. Memastikan aplikasi bisa nyala dan mati dengan anggun (\u003Cem>graceful\u003C/em>) adalah kunci membangun sistem yang tangguh (\u003Cem>resilient\u003C/em>), konsisten secara data, dan bebas \u003Cem>downtime\u003C/em> saat tim kalian rilis tiap hari.\u003C/p>\n\u003Cp>Selamat ber-\u003Cem>devops\u003C/em> ria, dan semoga server kalian selalu pamit dulu sebelum tidur! 👋\u003C/p>\n","\u003Cul>\n\u003Cli>\u003Cem>Graceful shutdown\u003C/em> adalah etika server buat menyelesaikan semua \u003Cem>in-flight request\u003C/em> sebelum prosesnya benar-benar dimatikan.\u003C/li>\n\u003Cli>Tanpa \u003Cem>graceful shutdown\u003C/em>, transaksi \u003Cem>database\u003C/em> menggantung, \u003Cem>connection pool\u003C/em> bocor, dan pengguna disambut error \u003Cstrong>502 Bad Gateway\u003C/strong> tepat saat \u003Cem>deploy\u003C/em>.\u003C/li>\n\u003Cli>Sinyal \u003Cem>SIGTERM\u003C/em> minta aplikasi berhenti dengan sopan, sedangkan \u003Cem>SIGKILL\u003C/em> memutus proses tanpa kompromi dan nggak bisa ditolak.\u003C/li>\n\u003Cli>Kombinasi \u003Cem>lifespan handler\u003C/em> di FastAPI, \u003Cem>exec form\u003C/em> di Dockerfile, \u003Ccode>terminationGracePeriodSeconds\u003C/code>, dan \u003Ccode>preStop\u003C/code> hook bikin \u003Cem>deployment\u003C/em> berjalan tanpa \u003Cem>downtime\u003C/em>.\u003C/li>\n\u003C/ul>\n",[417,420,423,431],{"id":328,"title":329,"slug":330,"excerpt":331,"thumbnail_image":418,"tags":419},{"id":333},[335,336,337,338,339],{"id":85,"title":86,"slug":87,"excerpt":88,"thumbnail_image":421,"tags":422},{"id":90},[51,56,92,93,94,57,95],{"id":424,"title":425,"slug":426,"excerpt":427,"thumbnail_image":428,"tags":430},"44","Transactional Outbox Pattern: Solusi Konsistensi Database dan Message Broker Tanpa 2PC","transactional-outbox-pattern-konsistensi-database-message-broker","Pernah nggak kalian lihat pesanan udah masuk database, tapi email konfirmasinya nggak pernah kekirim? Itu gejala *dual-write problem*. Yuk, kita bedah Transactional Outbox Pattern biar data dan *event* kalian nggak lagi berselisih paham!",{"id":429},"e3c617fd-1486-4b82-b937-94fbec846c77",[51,129,57,140,128,56,141],{"id":432,"title":433,"slug":434,"excerpt":435,"thumbnail_image":436,"tags":438},"43","Dead Letter Queue (DLQ) & Retry Policy: Menyelamatkan Pesan Nyasar di RabbitMQ Tanpa Bikin Worker Macet","dead-letter-queue-retry-policy-rabbitmq-resilient-messaging","Pernah nggak sih, *worker* kalian nolak satu pesan terus-terusan sampai CPU melonjak 100%? Itu namanya *poison message loop*, jebakan klasik di RabbitMQ. Yuk, kita bahas cara pasang *retry policy* dan *dead letter queue* yang bener!",{"id":437},"6c0a7ead-4841-4073-b29e-df7ae0f2aa3c",[127,128,51,57,129,130,287],[440,444,447,450,453],{"text":441,"depth":442,"id":443},"Mengenal Sinyal Unix: SIGINT, SIGTERM, dan SIGKILL",2,"mengenal-sinyal-unix-sigint-sigterm-dan-sigkill",{"text":445,"depth":442,"id":446},"Gimana Siklus Graceful Shutdown yang Ideal?","gimana-siklus-graceful-shutdown-yang-ideal",{"text":448,"depth":442,"id":449},"Contoh Lifespan di FastAPI dan Uvicorn","contoh-lifespan-di-fastapi-dan-uvicorn",{"text":451,"depth":442,"id":452},"Konfigurasi Penting di Docker dan Kubernetes","konfigurasi-penting-di-docker-dan-kubernetes",{"text":454,"depth":442,"id":455},"Jadi, Kenapa Ini Penting Banget?","jadi-kenapa-ini-penting-banget",1791045070731]