[{"data":1,"prerenderedAt":459},["ShallowReactive",2],{"site-header":3,"site-footer-license":37,"article-background-worker-task-queue-jangan-jalankan-proses-berat-di-http-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},"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!","2026-08-17T04:26:10.284Z",{"id":49},"e119c6ad-fc37-4b92-abdc-3eb20f8e34b4",[51,52,53,54,55,56,57],"backend","task-queue","celery","fastapi","rabbitmq","redis","async",5,"- Background worker membebaskan siklus HTTP request-response agar API langsung merespon user dalam hitungan milidetik.\n- Pola ini mencegah worker thread web server terkunci dan kehabisan kapasitas saat lonjakan trafik.\n- Message broker seperti RabbitMQ atau Redis jadi penampung antrean tugas asinkron.\n- Background worker independen menangani pengiriman email, generate dokumen, dan olah media.","Pernah nggak kalian klik tombol \"Daftar Akun\" atau \"Download Laporan PDF\", lalu halaman *loading* muter terus selama 10-15 detik tanpa kepastian?\n\nBikin frustrasi banget, kan? Penyebabnya hampir selalu sama: *server backend* ngeksekusi proses berat secara sinkron (*synchronous*) langsung di dalam siklus *request-response* HTTP.\n\nPadahal ada aturan emas di arsitektur *backend* modern—balikin *response* ke pengguna secepat mungkin, dan serahin tugas beratnya ke **background worker**.\n\nYuk, kita bahas kenapa aturan ini wajib kalian terapkan.\n\n## Masalah Klasik: Request HTTP yang Menggantung\n\nPas seorang *user* ngirim *request* HTTP, misalnya registrasi akun baru, urutannya sering kayak gini:\n\n1. *Backend* bikin data *user* di database. (Cepat, sekitar 10 ms)\n2. *Backend* ngirim email verifikasi lewat SMTP atau API pihak ketiga. (Bisa makan 2-5 detik)\n3. *Backend* bikin avatar *default* dan sinkronisasi data analitik. (Bisa makan 1-3 detik)\n4. Baru setelah semua itu kelar, *response* `200 OK` dikirim ke *user*.\n\nKelihatan aman-aman aja pas trafiknya sepi. Dampak aslinya baru kerasa pas lagi rame:\n\n- *User experience* buruk. Pengguna nunggu lama cuma buat tahu pendaftarannya berhasil.\n- *Worker thread web server* terkunci. Server punya batas maksimal koneksi simultan. Kalau koneksi tertahan lama buat urusan kirim email, server bisa kehabisan kapasitas (*thread exhaustion*) dan tumbang pas ada lonjakan *traffic*.\n\nAnggap kasir minimarket yang sekali ngelayanin harus ikut nungguin pelanggan ngobrol lama di dalam toko. Antrean di belakangnya makin panjang, padahal kasirnya nggak salah apa-apa. 😅\n\n## Kasir vs Koki: Cara Kerja Dapur Restoran\n\nBiar makin kebayang, bayangin kalian mesen steak di restoran.\n\n- Tanpa *background worker*: kasir nyatet pesanan, lalu si kasir sendiri masuk ke dapur, nyalain kompor, manggang daging 20 menit, naruhnya di piring, baru ngasih struk ke kalian. Antrean di kasir mengular panjang karena kasir sibuk masak.\n- Dengan *background worker*: kasir nyatet pesanan, mencetak tiket ke dapur, lalu langsung ngasih struk nomor antrean ke kalian dalam hitungan detik. Koki di dapur—si *worker*—yang manggang daging secara terpisah. Kasir langsung bisa ngelayani pelanggan berikutnya tanpa jeda.\n\nPrinsipnya sama persis di *backend*. Yang nerima pesanan jangan disuruh masak. Ibaratnya kasir nggak perlu jadi koki, kok.\n\n## Solusi: Asynchronous Task Queue & Background Worker\n\nDengan pendekatan **asynchronous task queue**, alurnya berubah jadi gini:\n\n1. *Web server* nerima *request* dan nyimpen data penting, misal ID *user*.\n2. *Web server* melempar instruksi tugas—contohnya \"kirim email ke *user* ID 123\"—ke dalam antrean (*message queue*/*broker* kayak Redis atau RabbitMQ).\n3. *Web server* langsung ngembaliin *response* `200 OK` (\"Registrasi berhasil, silakan cek email Anda\") dalam hitungan milidetik.\n4. Di belakang layar, proses terpisah bernama *background worker*—misalnya [Celery](https://docs.celeryq.dev/), RQ, atau Temporal—ngambil tugas dari antrean dan nyelesaiinnya secara mandiri.\n\n## Komponen Utama di Ekosistem Worker\n\n1. *Producer* (web API): aplikasi web yang nerima *request* dari *user* dan bikin tugas baru.\n2. *Message broker* / *queue*: tempat penampungan antrean tugas sementara, biasanya Redis atau RabbitMQ.\n3. *Consumer* / *worker*: skrip atau proses terpisah di server yang terus mendengarkan antrean dan ngeksekusi tugasnya.\n\nSusunannya sederhana, sih. Tapi efeknya gede banget ke *responsiveness* aplikasi kalian.\n\n## Contoh Praktis di Python: FastAPI BackgroundTasks\n\nBuat kasus sederhana yang belum butuh *broker* besar kayak Celery, [FastAPI](https://fastapi.tiangolo.com/tutorial/background-tasks/) udah nyediain modul bawaan `BackgroundTasks` yang praktis banget:\n\n```python\nimport time\nfrom fastapi import FastAPI, BackgroundTasks\n\napp = FastAPI()\n\ndef send_welcome_email(email: str):\n    # Simulasi proses pengiriman email yang memakan waktu lama\n    time.sleep(4)\n    print(f\"Email selamat datang berhasil dikirim ke: {email}\")\n\n@app.post(\"/register\")\nasync def register_user(email: str, background_tasks: BackgroundTasks):\n    # 1. Simpan user ke database di sini...\n\n    # 2. Daftarkan tugas berat ke background\n    background_tasks.add_task(send_welcome_email, email)\n\n    # 3. Langsung kirim respon ke user tanpa menunggu email terkirim!\n    return {\n        \"status\": \"success\",\n        \"message\": \"Registrasi berhasil! Email verifikasi sedang dikirim di latar belakang.\"\n    }\n```\n\nDengan pola di atas, endpoint `/register` langsung merespon dalam hitungan milidetik, sementara pengiriman email tetap jalan aman di latar belakang.\n\nCatatan penting nih. **`BackgroundTasks` di FastAPI jalan di dalam proses aplikasi yang sama.** Cocok buat prototipe dan tugas ringan, tapi kalau *server*-nya mati, tugas yang lagi jalan ikut hilang. Buat skala produksi, pindahin fungsinya ke *worker service* tersendiri yang mendengarkan pesan dari *broker* kayak RabbitMQ atau Redis.\n\n## Jadi, Kapan Mulai Pasang Background Worker?\n\nMembebaskan siklus utama HTTP dari pekerjaan berat itu rahasia utama di balik aplikasi modern yang terasa enteng dan responsif.\n\nBegitu aplikasi kalian mulai punya fitur kirim email verifikasi, olah gambar atau video, pembuatan dokumen laporan, atau integrasi ke layanan pihak ketiga, langsung pisahin ke *background worker* atau antrean terdistribusi kayak [Celery](https://docs.celeryq.dev/). Pengguna senang karena nggak perlu nunggu lama, dan *server* kalian tetap kokoh pas diserbu ribuan pengunjung barengan.\n\nNggak perlu nunggu *traffic* kalian jebol dulu baru berbenah, deh. Mulai dari satu tugas berat aja.\n\nSelamat ber-*worker* ria, dan semoga *request* kalian selalu pulang tepat waktu! 👋",[62],{"authors_id":63},{"name":64,"slug":65,"role":66,"profile_picture":67},"Daffa Izzuddin","izzudd","Writer",null,{"id":69,"title":8,"slug":9,"articles":70,"parent_series":67},"9",[71,86,98,110,121,132,144,147,159,170,181,191,201,212,221,232,243,253,261,272,283,294,302,311,320,333,342,353,364,374,383,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,84,85],"observa","logging","grafana","loki","vector","devops","system-design",{"id":87,"title":88,"slug":89,"excerpt":90,"thumbnail_image":91,"tags":93},"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":92},"0e0ed26d-20c6-443c-bde1-4a6200f6f801",[51,85,94,56,95,96,97],"rate-limiting","api-gateway","architecture","traffict-management",{"id":99,"title":100,"slug":101,"excerpt":102,"thumbnail_image":103,"tags":105},"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":104},"798b60f1-9ef5-4f73-8d43-85825fd86acc",[106,107,108,109],"javascript","nodejs","express","typescript",{"id":111,"title":112,"slug":113,"excerpt":114,"thumbnail_image":115,"tags":117},"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":116},"9c05d0ae-e829-4f1b-b9f7-a84f3e0439d3",[118,119,120],"pemrograman","concurrency","tips-coding",{"id":122,"title":123,"slug":124,"excerpt":125,"thumbnail_image":126,"tags":128},"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":127},"f6620f79-b3b2-4f9c-8104-283a335e06c4",[55,129,51,130,57,131],"message-broker","microservices","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,85,143],"database","postgresql","connection-pooling","performance",{"id":43,"title":44,"slug":45,"excerpt":46,"thumbnail_image":145,"tags":146},{"id":49},[51,52,53,54,55,56,57],{"id":148,"title":149,"slug":150,"excerpt":151,"thumbnail_image":152,"tags":154},"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":153},"34b94e14-3e9a-4778-9f1f-6df5898915fb",[140,155,156,157,158,143,51],"sql","orm","sqlalchemy","django",{"id":160,"title":161,"slug":162,"excerpt":163,"thumbnail_image":164,"tags":166},"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":165},"a368631c-f331-4c50-8322-1d0fc44927aa",[167,168,51,119,169,85],"golang","go","goroutine",{"id":171,"title":172,"slug":173,"excerpt":174,"thumbnail_image":175,"tags":177},"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":176},"ae27713e-5025-4d13-88b6-efb4860cc5b3",[178,179,180],"linux","windows","foss",{"id":182,"title":183,"slug":184,"excerpt":185,"thumbnail_image":186,"tags":188},"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":187},"18df5262-d813-43d1-b1f7-5595a7f53602",[106,189,190],"web","news",{"id":192,"title":193,"slug":194,"excerpt":195,"thumbnail_image":196,"tags":198},"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":197},"c5a8262b-43db-4479-8f6c-5a6a0d61653b",[199,179,200],"shell","powershell",{"id":202,"title":203,"slug":204,"excerpt":205,"thumbnail_image":206,"tags":208},"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":207},"99b01cc2-11ac-4449-9927-a1a7116347df",[209,210,211],"howto","java","editor",{"id":213,"title":214,"slug":215,"excerpt":216,"thumbnail_image":217,"tags":219},"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":218},"b5352a4b-f274-4489-aca9-36814947d514",[178,220],"distro",{"id":222,"title":223,"slug":224,"excerpt":225,"thumbnail_image":226,"tags":228},"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":227},"ff111270-80c2-4ccb-83d7-d5ab8c021201",[229,230,231],"web-development","frontend","framework",{"id":233,"title":234,"slug":235,"excerpt":236,"thumbnail_image":237,"tags":239},"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":238},"98e85e76-9e7b-42d1-b989-7c75e7f49abc",[240,241,242],"programming","types","comparison",{"id":244,"title":245,"slug":246,"excerpt":247,"thumbnail_image":248,"tags":250},"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":249},"d5e879fa-5cd0-4015-a155-b0cc69ff12fb",[251,252,229],"tailwind-css","css-framework",{"id":254,"title":255,"slug":256,"excerpt":257,"thumbnail_image":258,"tags":260},"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":259},"f615bb1f-8e36-4d6c-9c2c-f1629407173c",[109,106,229],{"id":262,"title":263,"slug":264,"excerpt":265,"thumbnail_image":266,"tags":268},"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":267},"8444bdbc-f60c-4d8b-8593-1b49400e8659",[269,270,271],"nuxt-3","vue-3","frontend-framework",{"id":273,"title":274,"slug":275,"excerpt":276,"thumbnail_image":277,"tags":279},"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":278},"84847c9e-70ab-4dcc-bed7-7be50165f7f4",[54,280,51,281,282],"python","asgi","pydantic",{"id":284,"title":285,"slug":286,"excerpt":287,"thumbnail_image":288,"tags":290},"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":289},"487500a0-9e09-469d-8736-1583c5ea83aa",[51,291,292,130,293,85],"grpc","rest-api","protobuf",{"id":295,"title":296,"slug":297,"excerpt":298,"thumbnail_image":299,"tags":301},"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":300},"21ab769d-6f82-4a22-be11-17ac16e9fb6b",[51,140,119,141,85,96,155],{"id":303,"title":304,"slug":305,"excerpt":306,"thumbnail_image":307,"tags":309},"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":308},"1401f9e5-6359-404a-8d80-273ddee9a372",[51,94,85,310,56,54],"api",{"id":312,"title":313,"slug":314,"excerpt":315,"thumbnail_image":316,"tags":318},"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":317},"d9e76018-fbcc-4c69-ad42-8f75ff229ecd",[51,85,319,129,96],"event-queue",{"id":321,"title":322,"slug":323,"excerpt":324,"thumbnail_image":325,"tags":327},"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":326},"1942a5c9-c1f6-476d-9913-768f78d9d8eb",[328,329,330,331,332],"system-programming","rust","zig","c","memory-safety",{"id":334,"title":335,"slug":336,"excerpt":337,"thumbnail_image":338,"tags":340},"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":339},"b123036f-1779-478c-a545-cf5f189b5fe9",[140,155,141,341,143,51],"indexing",{"id":343,"title":344,"slug":345,"excerpt":346,"thumbnail_image":347,"tags":349},"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":348},"9595b7d7-60e0-48f5-a715-f3cf60f34e1d",[56,51,350,351,352,280],"cache","nosql","in-memory",{"id":354,"title":355,"slug":356,"excerpt":357,"thumbnail_image":358,"tags":360},"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":359},"f4c08f1b-e0d0-410c-b091-c3618944fb3e",[361,362,84,363,51],"docker","docker-compose","containers",{"id":365,"title":366,"slug":367,"excerpt":368,"thumbnail_image":369,"tags":371},"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":370},"724cb83a-3ce5-4ee2-b0d7-533e3a0fc7df",[51,310,372,85,373,54,56],"idempotency","payment",{"id":375,"title":376,"slug":377,"excerpt":378,"thumbnail_image":379,"tags":381},"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":380},"c2e8e37f-8f9a-423f-a09d-74613b3c2924",[51,130,382,85,96],"circuit-breaker",{"id":384,"title":385,"slug":386,"excerpt":387,"thumbnail_image":388,"tags":390},"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!",{"id":389},"251a54a7-1d24-47fd-8cbc-a46fd42cbb6f",[51,84,54,361,391,85,96],"kubernetes",{"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,85,96,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,130,96,413],"distributed-systems","observability","open-telemetry","tracing","\u003Cp>Pernah nggak kalian klik tombol "Daftar Akun" atau "Download Laporan PDF", lalu halaman \u003Cem>loading\u003C/em> muter terus selama 10-15 detik tanpa kepastian?\u003C/p>\n\u003Cp>Bikin frustrasi banget, kan? Penyebabnya hampir selalu sama: \u003Cem>server backend\u003C/em> ngeksekusi proses berat secara sinkron (\u003Cem>synchronous\u003C/em>) langsung di dalam siklus \u003Cem>request-response\u003C/em> HTTP.\u003C/p>\n\u003Cp>Padahal ada aturan emas di arsitektur \u003Cem>backend\u003C/em> modern—balikin \u003Cem>response\u003C/em> ke pengguna secepat mungkin, dan serahin tugas beratnya ke \u003Cstrong>background worker\u003C/strong>.\u003C/p>\n\u003Cp>Yuk, kita bahas kenapa aturan ini wajib kalian terapkan.\u003C/p>\n\u003Ch2 id=\"masalah-klasik-request-http-yang-menggantung\">Masalah Klasik: Request HTTP yang Menggantung\u003C/h2>\n\u003Cp>Pas seorang \u003Cem>user\u003C/em> ngirim \u003Cem>request\u003C/em> HTTP, misalnya registrasi akun baru, urutannya sering kayak gini:\u003C/p>\n\u003Col>\n\u003Cli>\u003Cem>Backend\u003C/em> bikin data \u003Cem>user\u003C/em> di database. (Cepat, sekitar 10 ms)\u003C/li>\n\u003Cli>\u003Cem>Backend\u003C/em> ngirim email verifikasi lewat SMTP atau API pihak ketiga. (Bisa makan 2-5 detik)\u003C/li>\n\u003Cli>\u003Cem>Backend\u003C/em> bikin avatar \u003Cem>default\u003C/em> dan sinkronisasi data analitik. (Bisa makan 1-3 detik)\u003C/li>\n\u003Cli>Baru setelah semua itu kelar, \u003Cem>response\u003C/em> \u003Ccode>200 OK\u003C/code> dikirim ke \u003Cem>user\u003C/em>.\u003C/li>\n\u003C/ol>\n\u003Cp>Kelihatan aman-aman aja pas trafiknya sepi. Dampak aslinya baru kerasa pas lagi rame:\u003C/p>\n\u003Cul>\n\u003Cli>\u003Cem>User experience\u003C/em> buruk. Pengguna nunggu lama cuma buat tahu pendaftarannya berhasil.\u003C/li>\n\u003Cli>\u003Cem>Worker thread web server\u003C/em> terkunci. Server punya batas maksimal koneksi simultan. Kalau koneksi tertahan lama buat urusan kirim email, server bisa kehabisan kapasitas (\u003Cem>thread exhaustion\u003C/em>) dan tumbang pas ada lonjakan \u003Cem>traffic\u003C/em>.\u003C/li>\n\u003C/ul>\n\u003Cp>Anggap kasir minimarket yang sekali ngelayanin harus ikut nungguin pelanggan ngobrol lama di dalam toko. Antrean di belakangnya makin panjang, padahal kasirnya nggak salah apa-apa. 😅\u003C/p>\n\u003Ch2 id=\"kasir-vs-koki-cara-kerja-dapur-restoran\">Kasir vs Koki: Cara Kerja Dapur Restoran\u003C/h2>\n\u003Cp>Biar makin kebayang, bayangin kalian mesen steak di restoran.\u003C/p>\n\u003Cul>\n\u003Cli>Tanpa \u003Cem>background worker\u003C/em>: kasir nyatet pesanan, lalu si kasir sendiri masuk ke dapur, nyalain kompor, manggang daging 20 menit, naruhnya di piring, baru ngasih struk ke kalian. Antrean di kasir mengular panjang karena kasir sibuk masak.\u003C/li>\n\u003Cli>Dengan \u003Cem>background worker\u003C/em>: kasir nyatet pesanan, mencetak tiket ke dapur, lalu langsung ngasih struk nomor antrean ke kalian dalam hitungan detik. Koki di dapur—si \u003Cem>worker\u003C/em>—yang manggang daging secara terpisah. Kasir langsung bisa ngelayani pelanggan berikutnya tanpa jeda.\u003C/li>\n\u003C/ul>\n\u003Cp>Prinsipnya sama persis di \u003Cem>backend\u003C/em>. Yang nerima pesanan jangan disuruh masak. Ibaratnya kasir nggak perlu jadi koki, kok.\u003C/p>\n\u003Ch2 id=\"solusi-asynchronous-task-queue-background-worker\">Solusi: Asynchronous Task Queue & Background Worker\u003C/h2>\n\u003Cp>Dengan pendekatan \u003Cstrong>asynchronous task queue\u003C/strong>, alurnya berubah jadi gini:\u003C/p>\n\u003Col>\n\u003Cli>\u003Cem>Web server\u003C/em> nerima \u003Cem>request\u003C/em> dan nyimpen data penting, misal ID \u003Cem>user\u003C/em>.\u003C/li>\n\u003Cli>\u003Cem>Web server\u003C/em> melempar instruksi tugas—contohnya "kirim email ke \u003Cem>user\u003C/em> ID 123"—ke dalam antrean (\u003Cem>message queue\u003C/em>/\u003Cem>broker\u003C/em> kayak Redis atau RabbitMQ).\u003C/li>\n\u003Cli>\u003Cem>Web server\u003C/em> langsung ngembaliin \u003Cem>response\u003C/em> \u003Ccode>200 OK\u003C/code> ("Registrasi berhasil, silakan cek email Anda") dalam hitungan milidetik.\u003C/li>\n\u003Cli>Di belakang layar, proses terpisah bernama \u003Cem>background worker\u003C/em>—misalnya \u003Ca href=\"https://docs.celeryq.dev/\">Celery\u003C/a>, RQ, atau Temporal—ngambil tugas dari antrean dan nyelesaiinnya secara mandiri.\u003C/li>\n\u003C/ol>\n\u003Ch2 id=\"komponen-utama-di-ekosistem-worker\">Komponen Utama di Ekosistem Worker\u003C/h2>\n\u003Col>\n\u003Cli>\u003Cem>Producer\u003C/em> (web API): aplikasi web yang nerima \u003Cem>request\u003C/em> dari \u003Cem>user\u003C/em> dan bikin tugas baru.\u003C/li>\n\u003Cli>\u003Cem>Message broker\u003C/em> / \u003Cem>queue\u003C/em>: tempat penampungan antrean tugas sementara, biasanya Redis atau RabbitMQ.\u003C/li>\n\u003Cli>\u003Cem>Consumer\u003C/em> / \u003Cem>worker\u003C/em>: skrip atau proses terpisah di server yang terus mendengarkan antrean dan ngeksekusi tugasnya.\u003C/li>\n\u003C/ol>\n\u003Cp>Susunannya sederhana, sih. Tapi efeknya gede banget ke \u003Cem>responsiveness\u003C/em> aplikasi kalian.\u003C/p>\n\u003Ch2 id=\"contoh-praktis-di-python-fastapi-backgroundtasks\">Contoh Praktis di Python: FastAPI BackgroundTasks\u003C/h2>\n\u003Cp>Buat kasus sederhana yang belum butuh \u003Cem>broker\u003C/em> besar kayak Celery, \u003Ca href=\"https://fastapi.tiangolo.com/tutorial/background-tasks/\">FastAPI\u003C/a> udah nyediain modul bawaan \u003Ccode>BackgroundTasks\u003C/code> yang praktis banget:\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%20time%0Afrom%20fastapi%20import%20FastAPI%2C%20BackgroundTasks%0A%0Aapp%20%3D%20FastAPI()%0A%0Adef%20send_welcome_email(email%3A%20str)%3A%0A%20%20%20%20%23%20Simulasi%20proses%20pengiriman%20email%20yang%20memakan%20waktu%20lama%0A%20%20%20%20time.sleep(4)%0A%20%20%20%20print(f%22Email%20selamat%20datang%20berhasil%20dikirim%20ke%3A%20%7Bemail%7D%22)%0A%0A%40app.post(%22%2Fregister%22)%0Aasync%20def%20register_user(email%3A%20str%2C%20background_tasks%3A%20BackgroundTasks)%3A%0A%20%20%20%20%23%201.%20Simpan%20user%20ke%20database%20di%20sini...%0A%0A%20%20%20%20%23%202.%20Daftarkan%20tugas%20berat%20ke%20background%0A%20%20%20%20background_tasks.add_task(send_welcome_email%2C%20email)%0A%0A%20%20%20%20%23%203.%20Langsung%20kirim%20respon%20ke%20user%20tanpa%20menunggu%20email%20terkirim!%0A%20%20%20%20return%20%7B%0A%20%20%20%20%20%20%20%20%22status%22%3A%20%22success%22%2C%0A%20%20%20%20%20%20%20%20%22message%22%3A%20%22Registrasi%20berhasil!%20Email%20verifikasi%20sedang%20dikirim%20di%20latar%20belakang.%22%0A%20%20%20%20%7D\" 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\"> time\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, BackgroundTasks\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>\u003C/span>\n\u003Cspan class=\"line\">\u003C/span>\n\u003Cspan class=\"line\">\u003Cspan style=\"color:#F97583\">def\u003C/span>\u003Cspan style=\"color:#B392F0\"> send_welcome_email\u003C/span>\u003Cspan style=\"color:#E1E4E8\">(email: \u003C/span>\u003Cspan style=\"color:#79B8FF\">str\u003C/span>\u003Cspan style=\"color:#E1E4E8\">):\u003C/span>\u003C/span>\n\u003Cspan class=\"line\">\u003Cspan style=\"color:#6A737D\">    # Simulasi proses pengiriman email yang memakan waktu lama\u003C/span>\u003C/span>\n\u003Cspan class=\"line\">\u003Cspan style=\"color:#E1E4E8\">    time.sleep(\u003C/span>\u003Cspan style=\"color:#79B8FF\">4\u003C/span>\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:#F97583\">f\u003C/span>\u003Cspan style=\"color:#9ECBFF\">\"Email selamat datang berhasil dikirim ke: \u003C/span>\u003Cspan style=\"color:#79B8FF\">{\u003C/span>\u003Cspan style=\"color:#E1E4E8\">email\u003C/span>\u003Cspan style=\"color:#79B8FF\">}\u003C/span>\u003Cspan style=\"color:#9ECBFF\">\"\u003C/span>\u003Cspan style=\"color:#E1E4E8\">)\u003C/span>\u003C/span>\n\u003Cspan class=\"line\">\u003C/span>\n\u003Cspan class=\"line\">\u003Cspan style=\"color:#B392F0\">@app.post\u003C/span>\u003Cspan style=\"color:#E1E4E8\">(\u003C/span>\u003Cspan style=\"color:#9ECBFF\">\"/register\"\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\"> register_user\u003C/span>\u003Cspan style=\"color:#E1E4E8\">(email: \u003C/span>\u003Cspan style=\"color:#79B8FF\">str\u003C/span>\u003Cspan style=\"color:#E1E4E8\">, background_tasks: BackgroundTasks):\u003C/span>\u003C/span>\n\u003Cspan class=\"line\">\u003Cspan style=\"color:#6A737D\">    # 1. Simpan user ke database di sini...\u003C/span>\u003C/span>\n\u003Cspan class=\"line\">\u003C/span>\n\u003Cspan class=\"line\">\u003Cspan style=\"color:#6A737D\">    # 2. Daftarkan tugas berat ke background\u003C/span>\u003C/span>\n\u003Cspan class=\"line\">\u003Cspan style=\"color:#E1E4E8\">    background_tasks.add_task(send_welcome_email, email)\u003C/span>\u003C/span>\n\u003Cspan class=\"line\">\u003C/span>\n\u003Cspan class=\"line\">\u003Cspan style=\"color:#6A737D\">    # 3. Langsung kirim respon ke user tanpa menunggu email terkirim!\u003C/span>\u003C/span>\n\u003Cspan class=\"line\">\u003Cspan style=\"color:#F97583\">    return\u003C/span>\u003Cspan style=\"color:#E1E4E8\"> {\u003C/span>\u003C/span>\n\u003Cspan class=\"line\">\u003Cspan style=\"color:#9ECBFF\">        \"status\"\u003C/span>\u003Cspan style=\"color:#E1E4E8\">: \u003C/span>\u003Cspan style=\"color:#9ECBFF\">\"success\"\u003C/span>\u003Cspan style=\"color:#E1E4E8\">,\u003C/span>\u003C/span>\n\u003Cspan class=\"line\">\u003Cspan style=\"color:#9ECBFF\">        \"message\"\u003C/span>\u003Cspan style=\"color:#E1E4E8\">: \u003C/span>\u003Cspan style=\"color:#9ECBFF\">\"Registrasi berhasil! Email verifikasi sedang dikirim di latar belakang.\"\u003C/span>\u003C/span>\n\u003Cspan class=\"line\">\u003Cspan style=\"color:#E1E4E8\">    }\u003C/span>\u003C/span>\u003C/code>\u003C/pre>\n  \u003C/div>\n\u003C/div>\u003Cp>Dengan pola di atas, endpoint \u003Ccode>/register\u003C/code> langsung merespon dalam hitungan milidetik, sementara pengiriman email tetap jalan aman di latar belakang.\u003C/p>\n\u003Cp>Catatan penting nih. \u003Cstrong>\u003Ccode>BackgroundTasks\u003C/code> di FastAPI jalan di dalam proses aplikasi yang sama.\u003C/strong> Cocok buat prototipe dan tugas ringan, tapi kalau \u003Cem>server\u003C/em>-nya mati, tugas yang lagi jalan ikut hilang. Buat skala produksi, pindahin fungsinya ke \u003Cem>worker service\u003C/em> tersendiri yang mendengarkan pesan dari \u003Cem>broker\u003C/em> kayak RabbitMQ atau Redis.\u003C/p>\n\u003Ch2 id=\"jadi-kapan-mulai-pasang-background-worker\">Jadi, Kapan Mulai Pasang Background Worker?\u003C/h2>\n\u003Cp>Membebaskan siklus utama HTTP dari pekerjaan berat itu rahasia utama di balik aplikasi modern yang terasa enteng dan responsif.\u003C/p>\n\u003Cp>Begitu aplikasi kalian mulai punya fitur kirim email verifikasi, olah gambar atau video, pembuatan dokumen laporan, atau integrasi ke layanan pihak ketiga, langsung pisahin ke \u003Cem>background worker\u003C/em> atau antrean terdistribusi kayak \u003Ca href=\"https://docs.celeryq.dev/\">Celery\u003C/a>. Pengguna senang karena nggak perlu nunggu lama, dan \u003Cem>server\u003C/em> kalian tetap kokoh pas diserbu ribuan pengunjung barengan.\u003C/p>\n\u003Cp>Nggak perlu nunggu \u003Cem>traffic\u003C/em> kalian jebol dulu baru berbenah, deh. Mulai dari satu tugas berat aja.\u003C/p>\n\u003Cp>Selamat ber-\u003Cem>worker\u003C/em> ria, dan semoga \u003Cem>request\u003C/em> kalian selalu pulang tepat waktu! 👋\u003C/p>\n","\u003Cul>\n\u003Cli>Background worker membebaskan siklus HTTP request-response agar API langsung merespon user dalam hitungan milidetik.\u003C/li>\n\u003Cli>Pola ini mencegah worker thread web server terkunci dan kehabisan kapasitas saat lonjakan trafik.\u003C/li>\n\u003Cli>Message broker seperti RabbitMQ atau Redis jadi penampung antrean tugas asinkron.\u003C/li>\n\u003Cli>Background worker independen menangani pengiriman email, generate dokumen, dan olah media.\u003C/li>\n\u003C/ul>\n",[417,420,423,431],{"id":321,"title":322,"slug":323,"excerpt":324,"thumbnail_image":418,"tags":419},{"id":326},[328,329,330,331,332],{"id":87,"title":88,"slug":89,"excerpt":90,"thumbnail_image":421,"tags":422},{"id":92},[51,85,94,56,95,96,97],{"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,130,96,140,129,85,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",[55,129,51,96,130,57,280],[440,444,447,450,453,456],{"text":441,"depth":442,"id":443},"Masalah Klasik: Request HTTP yang Menggantung",2,"masalah-klasik-request-http-yang-menggantung",{"text":445,"depth":442,"id":446},"Kasir vs Koki: Cara Kerja Dapur Restoran","kasir-vs-koki-cara-kerja-dapur-restoran",{"text":448,"depth":442,"id":449},"Solusi: Asynchronous Task Queue & Background Worker","solusi-asynchronous-task-queue-background-worker",{"text":451,"depth":442,"id":452},"Komponen Utama di Ekosistem Worker","komponen-utama-di-ekosistem-worker",{"text":454,"depth":442,"id":455},"Contoh Praktis di Python: FastAPI BackgroundTasks","contoh-praktis-di-python-fastapi-backgroundtasks",{"text":457,"depth":442,"id":458},"Jadi, Kapan Mulai Pasang Background Worker?","jadi-kapan-mulai-pasang-background-worker",1791045070695]