[{"data":1,"prerenderedAt":463},["ShallowReactive",2],{"site-header":3,"site-footer-license":37,"article-mengatasi-n-plus-1-query-problem-musuh-tersembunyi-backend-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},"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!","2026-08-17T04:26:10.309Z",{"id":49},"34b94e14-3e9a-4778-9f1f-6df5898915fb",[51,52,53,54,55,56,57],"database","sql","orm","sqlalchemy","django","performance","backend",5,"- N+1 Query menjalankan 1 query awal buat ngambil daftar utama, lalu N query tambahan satu per satu di dalam perulangan.\n- Akar masalahnya adalah perilaku Lazy Loading yang jadi bawaan hampir semua ORM.\n- Solusinya Eager Loading alias ngambil relasi sekaligus, lewat joinedload atau selectinload di SQLAlchemy, serta select_related atau prefetch_related di Django.\n- Efeknya besar: puluhan round-trip ke database bisa menyusut jadi satu atau dua query saja.","Pernah nggak kalian bikin endpoint API yang kelihatannya simpel banget—cuma nampilin daftar 50 postingan blog beserta nama penulisnya masing-masing—tapi pas dites, response-nya makan waktu sampai 2-3 detik?\n\nSetelah dicek log *database*-nya, ternyata server database kalian dibombardir 51 *query* terpisah cuma buat ngelayanin satu *request* itu. Padahal datanya cuma segitu-gitu aja, lho.\n\nFenomena ini dikenal luas sebagai **N+1 Query Problem**. Ini salah satu *performance anti-pattern* paling klasik, dan sering banget menjebak developer backend yang pakai ORM.\n\n## Apa Sih N+1 Query Problem Itu?\n\nSecara sederhana, N+1 Query terjadi ketika aplikasi kalian melakukan dua hal:\n\n1. **1 query awal** buat ngambil daftar data utama sebanyak $N$ baris, misalnya `SELECT * FROM posts LIMIT 50;`.\n2. **N query tambahan** buat ngambil data relasinya satu per satu di dalam perulangan, misalnya `SELECT * FROM authors WHERE id = 1;`, lalu id = 2, dan seterusnya sampai 50 kali.\n\nTotal query yang dieksekusi ke database jadi **1 + N = 51 query**. Bayangkan kalau ada 1.000 orang mengakses halaman itu bersamaan. Database kalian bakal kebanjiran puluhan ribu *round-trip* yang sebenernya bisa diselesaikan cuma dalam satu atau dua query.\n\nBiar kebayang borosnya, coba pakai analogi belanja ini deh. Kalian disuruh beli 10 barang berbeda di minimarket.\n\n- Cara N+1: beli susu, pulang ke rumah. Balik ke minimarket, beli roti, pulang lagi. Ulangi 10 kali. Waktunya habis di jalan, bukan di belanjanya.\n- Cara efisien: bawa daftar belanjaan lengkap, ambil 10 barang sekaligus, bayar di kasir, terus pulang sekali jalan.\n\nNah, \"jalan bolak-balik\" itulah *network latency*. Semakin sering kalian bolak-balik ngeksekusi query kecil, semakin lambat response API kalian.\n\n## Kenapa ORM Sering Menjebak Kita?\n\nHampir semua ORM modern pakai mekanisme *Lazy Loading* secara bawaan.\n\nArtinya, data relasi nggak bakal dimuat ke memori sampai atributnya diakses secara eksplisit di dalam kode. Sekilas ini praktis dan hemat memori, ya. Tapi begitu kalian nge-*loop* `for` ke objek relasinya, ORM bakal otomatis ngeksekusi query baru di setiap iterasi tanpa kalian sadari. Nggak ada error, nggak ada warning—cuma lambat. 😅\n\n## Cara Mengatasinya: Eager Loading vs Lazy Loading\n\nSolusi utamanya adalah menerapkan **Eager Loading**, atau sering disebut juga *pre-fetching*.\n\nAlih-alih nunggu relasinya diakses satu per satu, kita kasih tahu ORM sejak awal: \"Tolong sekalian ambilkan data relasinya dalam satu *query* JOIN atau *query* `IN (...)` ya.\" Bedanya bisa drastis, lho—dari 51 query jadi 1 query.\n\n## Contoh Kode: Cara Memperbaiki di Python\n\n### 1. Di SQLAlchemy (FastAPI / Flask)\n\n```python\n# Masalah N+1 (Lazy Loading)\nposts = db.query(Post).all()\nfor post in posts:\n    print(post.author.name)  # Memicu query baru tiap iterasi!\n\n# Solusi: Eager Loading dengan joinedload atau selectinload\nfrom sqlalchemy.orm import joinedload\n\nposts = db.query(Post).options(joinedload(Post.author)).all()\nfor post in posts:\n    print(post.author.name)  # Data author sudah dimuat sekaligus via JOIN!\n```\n\n### 2. Di Django ORM\n\n```python\n# Masalah N+1\nposts = Post.objects.all()\nfor post in posts:\n    print(post.author.name)  # Query berulang ke tabel Author\n\n# Solusi untuk ForeignKey / OneToOne: select_related\nposts = Post.objects.select_related('author').all()\n\n# Solusi untuk ManyToMany / Reverse ForeignKey: prefetch_related\nposts = Post.objects.prefetch_related('tags').all()\n```\n\n## Kapan Lazy Loading Masih Wajar Dipakai?\n\nEager loading bukan berarti kalian harus ngehapus semua *lazy loading*, ya. Ada kalanya *lazy loading* justru lebih hemat, kok.\n\n- Kalau relasinya cuma diakses di sebagian kecil baris, misalnya cuma halaman detail satu postingan, lazy loading itu nggak masalah.\n- Kalau kalian nge-*prefetch* tabel relasi yang gede padahal cuma butuh beberapa kolomnya, memori aplikasi kalian justru bisa membengkak.\n- Yang paling penting, biasakan cek query log atau pakai *profiling tool* di fase development. Tools kayak Django Debug Toolbar atau opsi `echo=True` di SQLAlchemy bakal langsung nunjukin kalau *query* kalian tiba-tiba menumpuk.\n\nN+1 Query itu jebakan klasik yang nggak kerasa di *localhost* dengan segelintir data *dummy*, tapi langsung bikin server *timeout* begitu datanya menyentuh angka ribuan. Jadi, biasakan inspeksi *query* kalian sejak awal ya, dan manfaatkan *eager loading* kayak [`joinedload` di SQLAlchemy](https://docs.sqlalchemy.org/en/20/orm/queryguide/relationships.html#joined-eager-loading) atau [`select_related` di Django](https://docs.djangoproject.com/en/stable/ref/models/querysets/#select-related) tiap kali berurusan dengan relasi data dalam jumlah banyak.\n\nSelamat ber-*database* ria, dan semoga query kalian selalu cukup satu! 👋",[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,99,111,122,135,145,156,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",[57,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",[57,85,94,95,96,97,98],"rate-limiting","redis","api-gateway","architecture","traffict-management",{"id":100,"title":101,"slug":102,"excerpt":103,"thumbnail_image":104,"tags":106},"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":105},"798b60f1-9ef5-4f73-8d43-85825fd86acc",[107,108,109,110],"javascript","nodejs","express","typescript",{"id":112,"title":113,"slug":114,"excerpt":115,"thumbnail_image":116,"tags":118},"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":117},"9c05d0ae-e829-4f1b-b9f7-a84f3e0439d3",[119,120,121],"pemrograman","concurrency","tips-coding",{"id":123,"title":124,"slug":125,"excerpt":126,"thumbnail_image":127,"tags":129},"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":128},"f6620f79-b3b2-4f9c-8104-283a335e06c4",[130,131,57,132,133,134],"rabbitmq","message-broker","microservices","async","queue",{"id":136,"title":137,"slug":138,"excerpt":139,"thumbnail_image":140,"tags":142},"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":141},"6f7a2d8c-2a37-4901-a522-50df8d9c0a20",[57,51,143,144,85,56],"postgresql","connection-pooling",{"id":146,"title":147,"slug":148,"excerpt":149,"thumbnail_image":150,"tags":152},"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":151},"e119c6ad-fc37-4b92-abdc-3eb20f8e34b4",[57,153,154,155,130,95,133],"task-queue","celery","fastapi",{"id":43,"title":44,"slug":45,"excerpt":46,"thumbnail_image":157,"tags":158},{"id":49},[51,52,53,54,55,56,57],{"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,57,120,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",[107,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",[110,107,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",[155,280,57,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",[57,291,292,132,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",[57,51,120,143,85,97,52],{"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",[57,94,85,310,95,155],"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",[57,85,319,131,97],"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",[51,52,143,341,56,57],"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",[95,57,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,57],"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",[57,310,372,85,373,155,95],"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",[57,132,382,85,97],"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",[57,84,155,361,391,85,97],"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",[57,51,143,85,97,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",[57,410,411,412,132,97,413],"distributed-systems","observability","open-telemetry","tracing","\u003Cp>Pernah nggak kalian bikin endpoint API yang kelihatannya simpel banget—cuma nampilin daftar 50 postingan blog beserta nama penulisnya masing-masing—tapi pas dites, response-nya makan waktu sampai 2-3 detik?\u003C/p>\n\u003Cp>Setelah dicek log \u003Cem>database\u003C/em>-nya, ternyata server database kalian dibombardir 51 \u003Cem>query\u003C/em> terpisah cuma buat ngelayanin satu \u003Cem>request\u003C/em> itu. Padahal datanya cuma segitu-gitu aja, lho.\u003C/p>\n\u003Cp>Fenomena ini dikenal luas sebagai \u003Cstrong>N+1 Query Problem\u003C/strong>. Ini salah satu \u003Cem>performance anti-pattern\u003C/em> paling klasik, dan sering banget menjebak developer backend yang pakai ORM.\u003C/p>\n\u003Ch2 id=\"apa-sih-n-1-query-problem-itu\">Apa Sih N+1 Query Problem Itu?\u003C/h2>\n\u003Cp>Secara sederhana, N+1 Query terjadi ketika aplikasi kalian melakukan dua hal:\u003C/p>\n\u003Col>\n\u003Cli>\u003Cstrong>1 query awal\u003C/strong> buat ngambil daftar data utama sebanyak $N$ baris, misalnya \u003Ccode>SELECT * FROM posts LIMIT 50;\u003C/code>.\u003C/li>\n\u003Cli>\u003Cstrong>N query tambahan\u003C/strong> buat ngambil data relasinya satu per satu di dalam perulangan, misalnya \u003Ccode>SELECT * FROM authors WHERE id = 1;\u003C/code>, lalu id = 2, dan seterusnya sampai 50 kali.\u003C/li>\n\u003C/ol>\n\u003Cp>Total query yang dieksekusi ke database jadi \u003Cstrong>1 + N = 51 query\u003C/strong>. Bayangkan kalau ada 1.000 orang mengakses halaman itu bersamaan. Database kalian bakal kebanjiran puluhan ribu \u003Cem>round-trip\u003C/em> yang sebenernya bisa diselesaikan cuma dalam satu atau dua query.\u003C/p>\n\u003Cp>Biar kebayang borosnya, coba pakai analogi belanja ini deh. Kalian disuruh beli 10 barang berbeda di minimarket.\u003C/p>\n\u003Cul>\n\u003Cli>Cara N+1: beli susu, pulang ke rumah. Balik ke minimarket, beli roti, pulang lagi. Ulangi 10 kali. Waktunya habis di jalan, bukan di belanjanya.\u003C/li>\n\u003Cli>Cara efisien: bawa daftar belanjaan lengkap, ambil 10 barang sekaligus, bayar di kasir, terus pulang sekali jalan.\u003C/li>\n\u003C/ul>\n\u003Cp>Nah, "jalan bolak-balik" itulah \u003Cem>network latency\u003C/em>. Semakin sering kalian bolak-balik ngeksekusi query kecil, semakin lambat response API kalian.\u003C/p>\n\u003Ch2 id=\"kenapa-orm-sering-menjebak-kita\">Kenapa ORM Sering Menjebak Kita?\u003C/h2>\n\u003Cp>Hampir semua ORM modern pakai mekanisme \u003Cem>Lazy Loading\u003C/em> secara bawaan.\u003C/p>\n\u003Cp>Artinya, data relasi nggak bakal dimuat ke memori sampai atributnya diakses secara eksplisit di dalam kode. Sekilas ini praktis dan hemat memori, ya. Tapi begitu kalian nge-\u003Cem>loop\u003C/em> \u003Ccode>for\u003C/code> ke objek relasinya, ORM bakal otomatis ngeksekusi query baru di setiap iterasi tanpa kalian sadari. Nggak ada error, nggak ada warning—cuma lambat. 😅\u003C/p>\n\u003Ch2 id=\"cara-mengatasinya-eager-loading-vs-lazy-loading\">Cara Mengatasinya: Eager Loading vs Lazy Loading\u003C/h2>\n\u003Cp>Solusi utamanya adalah menerapkan \u003Cstrong>Eager Loading\u003C/strong>, atau sering disebut juga \u003Cem>pre-fetching\u003C/em>.\u003C/p>\n\u003Cp>Alih-alih nunggu relasinya diakses satu per satu, kita kasih tahu ORM sejak awal: "Tolong sekalian ambilkan data relasinya dalam satu \u003Cem>query\u003C/em> JOIN atau \u003Cem>query\u003C/em> \u003Ccode>IN (...)\u003C/code> ya." Bedanya bisa drastis, lho—dari 51 query jadi 1 query.\u003C/p>\n\u003Ch2 id=\"contoh-kode-cara-memperbaiki-di-python\">Contoh Kode: Cara Memperbaiki di Python\u003C/h2>\n\u003Ch3 id=\"1-di-sqlalchemy-fastapi-flask\">1. Di SQLAlchemy (FastAPI / Flask)\u003C/h3>\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=\"%23%20Masalah%20N%2B1%20(Lazy%20Loading)%0Aposts%20%3D%20db.query(Post).all()%0Afor%20post%20in%20posts%3A%0A%20%20%20%20print(post.author.name)%20%20%23%20Memicu%20query%20baru%20tiap%20iterasi!%0A%0A%23%20Solusi%3A%20Eager%20Loading%20dengan%20joinedload%20atau%20selectinload%0Afrom%20sqlalchemy.orm%20import%20joinedload%0A%0Aposts%20%3D%20db.query(Post).options(joinedload(Post.author)).all()%0Afor%20post%20in%20posts%3A%0A%20%20%20%20print(post.author.name)%20%20%23%20Data%20author%20sudah%20dimuat%20sekaligus%20via%20JOIN!\" 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:#6A737D\"># Masalah N+1 (Lazy Loading)\u003C/span>\u003C/span>\n\u003Cspan class=\"line\">\u003Cspan style=\"color:#E1E4E8\">posts \u003C/span>\u003Cspan style=\"color:#F97583\">=\u003C/span>\u003Cspan style=\"color:#E1E4E8\"> db.query(Post).all()\u003C/span>\u003C/span>\n\u003Cspan class=\"line\">\u003Cspan style=\"color:#F97583\">for\u003C/span>\u003Cspan style=\"color:#E1E4E8\"> post \u003C/span>\u003Cspan style=\"color:#F97583\">in\u003C/span>\u003Cspan style=\"color:#E1E4E8\"> posts:\u003C/span>\u003C/span>\n\u003Cspan class=\"line\">\u003Cspan style=\"color:#79B8FF\">    print\u003C/span>\u003Cspan style=\"color:#E1E4E8\">(post.author.name)  \u003C/span>\u003Cspan style=\"color:#6A737D\"># Memicu query baru tiap iterasi!\u003C/span>\u003C/span>\n\u003Cspan class=\"line\">\u003C/span>\n\u003Cspan class=\"line\">\u003Cspan style=\"color:#6A737D\"># Solusi: Eager Loading dengan joinedload atau selectinload\u003C/span>\u003C/span>\n\u003Cspan class=\"line\">\u003Cspan style=\"color:#F97583\">from\u003C/span>\u003Cspan style=\"color:#E1E4E8\"> sqlalchemy.orm \u003C/span>\u003Cspan style=\"color:#F97583\">import\u003C/span>\u003Cspan style=\"color:#E1E4E8\"> joinedload\u003C/span>\u003C/span>\n\u003Cspan class=\"line\">\u003C/span>\n\u003Cspan class=\"line\">\u003Cspan style=\"color:#E1E4E8\">posts \u003C/span>\u003Cspan style=\"color:#F97583\">=\u003C/span>\u003Cspan style=\"color:#E1E4E8\"> db.query(Post).options(joinedload(Post.author)).all()\u003C/span>\u003C/span>\n\u003Cspan class=\"line\">\u003Cspan style=\"color:#F97583\">for\u003C/span>\u003Cspan style=\"color:#E1E4E8\"> post \u003C/span>\u003Cspan style=\"color:#F97583\">in\u003C/span>\u003Cspan style=\"color:#E1E4E8\"> posts:\u003C/span>\u003C/span>\n\u003Cspan class=\"line\">\u003Cspan style=\"color:#79B8FF\">    print\u003C/span>\u003Cspan style=\"color:#E1E4E8\">(post.author.name)  \u003C/span>\u003Cspan style=\"color:#6A737D\"># Data author sudah dimuat sekaligus via JOIN!\u003C/span>\u003C/span>\u003C/code>\u003C/pre>\n  \u003C/div>\n\u003C/div>\u003Ch3 id=\"2-di-django-orm\">2. Di Django ORM\u003C/h3>\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=\"%23%20Masalah%20N%2B1%0Aposts%20%3D%20Post.objects.all()%0Afor%20post%20in%20posts%3A%0A%20%20%20%20print(post.author.name)%20%20%23%20Query%20berulang%20ke%20tabel%20Author%0A%0A%23%20Solusi%20untuk%20ForeignKey%20%2F%20OneToOne%3A%20select_related%0Aposts%20%3D%20Post.objects.select_related('author').all()%0A%0A%23%20Solusi%20untuk%20ManyToMany%20%2F%20Reverse%20ForeignKey%3A%20prefetch_related%0Aposts%20%3D%20Post.objects.prefetch_related('tags').all()\" 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:#6A737D\"># Masalah N+1\u003C/span>\u003C/span>\n\u003Cspan class=\"line\">\u003Cspan style=\"color:#E1E4E8\">posts \u003C/span>\u003Cspan style=\"color:#F97583\">=\u003C/span>\u003Cspan style=\"color:#E1E4E8\"> Post.objects.all()\u003C/span>\u003C/span>\n\u003Cspan class=\"line\">\u003Cspan style=\"color:#F97583\">for\u003C/span>\u003Cspan style=\"color:#E1E4E8\"> post \u003C/span>\u003Cspan style=\"color:#F97583\">in\u003C/span>\u003Cspan style=\"color:#E1E4E8\"> posts:\u003C/span>\u003C/span>\n\u003Cspan class=\"line\">\u003Cspan style=\"color:#79B8FF\">    print\u003C/span>\u003Cspan style=\"color:#E1E4E8\">(post.author.name)  \u003C/span>\u003Cspan style=\"color:#6A737D\"># Query berulang ke tabel Author\u003C/span>\u003C/span>\n\u003Cspan class=\"line\">\u003C/span>\n\u003Cspan class=\"line\">\u003Cspan style=\"color:#6A737D\"># Solusi untuk ForeignKey / OneToOne: select_related\u003C/span>\u003C/span>\n\u003Cspan class=\"line\">\u003Cspan style=\"color:#E1E4E8\">posts \u003C/span>\u003Cspan style=\"color:#F97583\">=\u003C/span>\u003Cspan style=\"color:#E1E4E8\"> Post.objects.select_related(\u003C/span>\u003Cspan style=\"color:#9ECBFF\">'author'\u003C/span>\u003Cspan style=\"color:#E1E4E8\">).all()\u003C/span>\u003C/span>\n\u003Cspan class=\"line\">\u003C/span>\n\u003Cspan class=\"line\">\u003Cspan style=\"color:#6A737D\"># Solusi untuk ManyToMany / Reverse ForeignKey: prefetch_related\u003C/span>\u003C/span>\n\u003Cspan class=\"line\">\u003Cspan style=\"color:#E1E4E8\">posts \u003C/span>\u003Cspan style=\"color:#F97583\">=\u003C/span>\u003Cspan style=\"color:#E1E4E8\"> Post.objects.prefetch_related(\u003C/span>\u003Cspan style=\"color:#9ECBFF\">'tags'\u003C/span>\u003Cspan style=\"color:#E1E4E8\">).all()\u003C/span>\u003C/span>\u003C/code>\u003C/pre>\n  \u003C/div>\n\u003C/div>\u003Ch2 id=\"kapan-lazy-loading-masih-wajar-dipakai\">Kapan Lazy Loading Masih Wajar Dipakai?\u003C/h2>\n\u003Cp>Eager loading bukan berarti kalian harus ngehapus semua \u003Cem>lazy loading\u003C/em>, ya. Ada kalanya \u003Cem>lazy loading\u003C/em> justru lebih hemat, kok.\u003C/p>\n\u003Cul>\n\u003Cli>Kalau relasinya cuma diakses di sebagian kecil baris, misalnya cuma halaman detail satu postingan, lazy loading itu nggak masalah.\u003C/li>\n\u003Cli>Kalau kalian nge-\u003Cem>prefetch\u003C/em> tabel relasi yang gede padahal cuma butuh beberapa kolomnya, memori aplikasi kalian justru bisa membengkak.\u003C/li>\n\u003Cli>Yang paling penting, biasakan cek query log atau pakai \u003Cem>profiling tool\u003C/em> di fase development. Tools kayak Django Debug Toolbar atau opsi \u003Ccode>echo=True\u003C/code> di SQLAlchemy bakal langsung nunjukin kalau \u003Cem>query\u003C/em> kalian tiba-tiba menumpuk.\u003C/li>\n\u003C/ul>\n\u003Cp>N+1 Query itu jebakan klasik yang nggak kerasa di \u003Cem>localhost\u003C/em> dengan segelintir data \u003Cem>dummy\u003C/em>, tapi langsung bikin server \u003Cem>timeout\u003C/em> begitu datanya menyentuh angka ribuan. Jadi, biasakan inspeksi \u003Cem>query\u003C/em> kalian sejak awal ya, dan manfaatkan \u003Cem>eager loading\u003C/em> kayak \u003Ca href=\"https://docs.sqlalchemy.org/en/20/orm/queryguide/relationships.html#joined-eager-loading\">\u003Ccode>joinedload\u003C/code> di SQLAlchemy\u003C/a> atau \u003Ca href=\"https://docs.djangoproject.com/en/stable/ref/models/querysets/#select-related\">\u003Ccode>select_related\u003C/code> di Django\u003C/a> tiap kali berurusan dengan relasi data dalam jumlah banyak.\u003C/p>\n\u003Cp>Selamat ber-\u003Cem>database\u003C/em> ria, dan semoga query kalian selalu cukup satu! 👋\u003C/p>\n","\u003Cul>\n\u003Cli>N+1 Query menjalankan 1 query awal buat ngambil daftar utama, lalu N query tambahan satu per satu di dalam perulangan.\u003C/li>\n\u003Cli>Akar masalahnya adalah perilaku Lazy Loading yang jadi bawaan hampir semua ORM.\u003C/li>\n\u003Cli>Solusinya Eager Loading alias ngambil relasi sekaligus, lewat joinedload atau selectinload di SQLAlchemy, serta select_related atau prefetch_related di Django.\u003C/li>\n\u003Cli>Efeknya besar: puluhan round-trip ke database bisa menyusut jadi satu atau dua query saja.\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},[57,85,94,95,96,97,98],{"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",[57,132,97,51,131,85,143],{"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",[130,131,57,97,132,133,280],[440,444,447,450,453,457,460],{"text":441,"depth":442,"id":443},"Apa Sih N+1 Query Problem Itu?",2,"apa-sih-n-1-query-problem-itu",{"text":445,"depth":442,"id":446},"Kenapa ORM Sering Menjebak Kita?","kenapa-orm-sering-menjebak-kita",{"text":448,"depth":442,"id":449},"Cara Mengatasinya: Eager Loading vs Lazy Loading","cara-mengatasinya-eager-loading-vs-lazy-loading",{"text":451,"depth":442,"id":452},"Contoh Kode: Cara Memperbaiki di Python","contoh-kode-cara-memperbaiki-di-python",{"text":454,"depth":455,"id":456},"1. Di SQLAlchemy (FastAPI / Flask)",3,"1-di-sqlalchemy-fastapi-flask",{"text":458,"depth":455,"id":459},"2. Di Django ORM","2-di-django-orm",{"text":461,"depth":442,"id":462},"Kapan Lazy Loading Masih Wajar Dipakai?","kapan-lazy-loading-masih-wajar-dipakai",1791045070592]