[{"data":1,"prerenderedAt":459},["ShallowReactive",2],{"site-header":3,"site-footer-license":37,"article-memahami-database-indexing-rahasia-query-super-cepat-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":57,"takeway":58,"body":59,"authors":60,"series":67},"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!","2026-08-17T04:26:10.325Z",{"id":49},"b123036f-1779-478c-a545-cf5f189b5fe9",[51,52,53,54,55,56],"database","sql","postgresql","indexing","performance","backend",4,"- *Index* ngerubah pencarian data dari *Full Table Scan* O(N) yang boros jadi *Index Scan* B-Tree O(log N) yang jauh lebih gesit.\n- Klausa *WHERE*, *JOIN*, *ORDER BY*, dan *GROUP BY* adalah tempat *index* paling sering ngebantu mempercepat *query*.\n- Harga yang dibayar adalah ruang *disk* tambahan dan beban *update* struktur *B-Tree* tiap operasi *write*.\n- Tabel kecil atau kolom ber-*cardinality* rendah—kayak kolom `jenis_kelamin`—justru nggak perlu dipasangi *index*.","Query kalian mendadak lelet padahal data baru nembus jutaan *row*? Tenang, kalian nggak sendirian. 😅\n\nSeringnya, reaksi pertama kita itu buru-buru kepengen *upgrade* spek server database (*vertical scaling*). Padahal, dalam banyak kasus, akar masalahnya sepele aja: *index*-nya kurang, atau malah salah pasang.\n\n[*Index*](https://use-the-index-luke.com/) sendiri adalah salah satu fitur paling fundamental—tapi paling ngefek—buat nyepetin pencarian data di database relasional kayak PostgreSQL atau MySQL. Yuk, kita bedah bareng gimana sih kerjanya.\n\n## Kenapa Pencarian Tanpa *Index* Itu Bikin Capek?\n\nCoba bayangin kalian lagi nyari definisi kata \"Konkurensi\" di ensiklopedia tebel setebel 1.000 halaman.\n\nKalau kalian harus baca dari halaman 1, kata demi kata, sampai ketemu di halaman 642—capek, kan? 🤔 Lama pula. Cara brutal kayak gini di dunia database disebut *Full Table Scan*.\n\nBeda cerita kalau kalian langsung ngebuka bagian *index* di halaman paling belakang. Di situ kata \"Konkurensi\" udah disusun urut alfabetis, lengkap sama nomor halamannya. Tinggal lompat ke halaman 642, tanpa perlu nyisir lembar lainnya. Gaya kedua inilah yang disebut *Index Scan*.\n\nSimpel, tapi bedanya kayak langit dan bumi.\n\n## Apa Sih yang Terjadi di Balik Layar?\n\nSecara *default*, hampir semua database relasional pakai struktur data *B-Tree* (*Balanced Tree*) buat nyimpen *index*-nya.\n\nStruktur *B-Tree* bikin database bisa nyari data dengan kompleksitas waktu O(log N). Artinya, buat nyari 1 *row* di antara 1.000.000 *row*, database cuma perlu **sekitar 20 kali perbandingan**. 😎 Jauh lebih hemat ketimbang ngecek sejuta *row* satu-satu.\n\nJadi, ngebayangin *index* itu kayak nempelin tab penanda di buku catatan. Kalian nggak perlu baca semua halaman tiap kali mau nemu satu bab.\n\n## Emang Ada Ruginya Pasang *Index*?\n\nAda dong, nggak ada makan siang gratis. 😄\n\n*Index* itu butuh ruang *disk* tambahan buat nyimpen datanya yang udah terurut. Di samping itu, setiap kali ada data baru yang di-*insert* atau di-*update*, database harus ikut ngerapihin struktur *B-Tree*-nya.\n\nEfeknya, operasi *write* alias `INSERT`, `UPDATE`, dan `DELETE` bisa jadi sedikit lebih lambat. Kerjaannya nambah, sih. Jadi, *index* itu **bukan barang yang makin banyak makin bagus**, lho.\n\n## Kapan Wajib Dipasang, Kapan Mendingan Nggak?\n\nGampangnya, pasang *index* di kolom yang jadi langganan *query* pencarian kalian.\n\n- Kolom yang sering muncul di klausa `WHERE`—misalnya `WHERE email = 'user@example.com'`.\n- Kolom yang sering dipakai buat nggabungin tabel alias `JOIN`.\n- Kolom yang dipakai buat ngurutin (`ORDER BY`) atau ngelempokin (`GROUP BY`).\n\nTapi, ada juga kondisi di mana *index* malah nggak ada gunanya:\n\n- Tabelnya kecil—cuma puluhan atau ratusan *row*—soalnya *Full Table Scan* justru lebih cepet.\n- Kolom yang nilainya sering berubah (*frequent write*).\n- Kolom dengan variasi nilai rendah (*low cardinality*), contohnya `jenis_kelamin` yang isinya cuma `L` atau `P`.\n\nKolom `jenis_kelamin` itu ibarat nyari buku cuma berdasarkan warna sampulnya. Nggak ngebantu banyak, hehe.\n\n## Contoh Bikin *Index* di SQL\n\nMisalkan kita punya tabel `users` yang isinya jutaan *row*.\n\n```sql\n-- Query pencarian tanpa index (bisa lelet pas datanya jutaan)\nSELECT * FROM users WHERE email = 'daffa@example.com';\n\n-- Membuat single-column index pada kolom email\nCREATE INDEX idx_users_email ON users(email);\n\n-- Membuat composite index untuk WHERE dengan dua kolom\nCREATE INDEX idx_users_status_created ON users(status, created_at);\n```\n\nPerhatiin, urutan kolom di *composite index* `(status, created_at)` itu ngaruh. Kalau kalian cuma nyari berdasarkan `created_at` doang tanpa `status`, *index*-nya sering nggak kepake—karena urutannya nggak cocok sama pola *query*-nya.\n\n## Jadi, Gimana Cara Cerdas Pasang *Index*?\n\nIntinya, *index* itu kayak jalan pintas rahasia di dalam labirin data. Dengan konfigurasi *B-Tree* yang tepat, pencarian di antara jutaan *row* bisa kelar dalam sekejap, tanpa nguras *CPU* server.\n\nKuncinya ada di **keseimbangan**: pasang *index* di kolom yang jadi langganan `WHERE`, `JOIN`, atau `ORDER BY`, tapi jangan berlebihan biar proses *write* tetap gesit dan *disk* tetap lega.\n\nBuat yang pengen ngebahas *indexing* lebih dalem, [use-the-index-luke.com](https://use-the-index-luke.com/) itu rujukan yang juara.\n\nSelamat ber-*indexing* ria, dan semoga *query* kalian selalu mulus di lorong *B-Tree*-nya! 👋",[61],{"authors_id":62},{"name":63,"slug":64,"role":65,"profile_picture":66},"Daffa Izzuddin","izzudd","Writer",null,{"id":68,"title":8,"slug":9,"articles":69,"parent_series":66},"9",[70,85,98,110,121,134,143,154,165,176,187,197,207,218,227,238,249,259,267,278,289,300,308,317,326,339,342,353,364,374,383,392,402],{"id":71,"title":72,"slug":73,"excerpt":74,"thumbnail_image":75,"tags":77},"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":76},"03c9d1a0-c80a-401d-9f2b-2b3ee7abb115",[56,78,79,80,81,82,83,84],"observa","logging","grafana","loki","vector","devops","system-design",{"id":86,"title":87,"slug":88,"excerpt":89,"thumbnail_image":90,"tags":92},"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":91},"0e0ed26d-20c6-443c-bde1-4a6200f6f801",[56,84,93,94,95,96,97],"rate-limiting","redis","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",[129,130,56,131,132,133],"rabbitmq","message-broker","microservices","async","queue",{"id":135,"title":136,"slug":137,"excerpt":138,"thumbnail_image":139,"tags":141},"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":140},"6f7a2d8c-2a37-4901-a522-50df8d9c0a20",[56,51,53,142,84,55],"connection-pooling",{"id":144,"title":145,"slug":146,"excerpt":147,"thumbnail_image":148,"tags":150},"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":149},"e119c6ad-fc37-4b92-abdc-3eb20f8e34b4",[56,151,152,153,129,94,132],"task-queue","celery","fastapi",{"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",[51,52,162,163,164,55,56],"orm","sqlalchemy","django",{"id":166,"title":167,"slug":168,"excerpt":169,"thumbnail_image":170,"tags":172},"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":171},"a368631c-f331-4c50-8322-1d0fc44927aa",[173,174,56,119,175,84],"golang","go","goroutine",{"id":177,"title":178,"slug":179,"excerpt":180,"thumbnail_image":181,"tags":183},"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":182},"ae27713e-5025-4d13-88b6-efb4860cc5b3",[184,185,186],"linux","windows","foss",{"id":188,"title":189,"slug":190,"excerpt":191,"thumbnail_image":192,"tags":194},"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":193},"18df5262-d813-43d1-b1f7-5595a7f53602",[106,195,196],"web","news",{"id":198,"title":199,"slug":200,"excerpt":201,"thumbnail_image":202,"tags":204},"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":203},"c5a8262b-43db-4479-8f6c-5a6a0d61653b",[205,185,206],"shell","powershell",{"id":208,"title":209,"slug":210,"excerpt":211,"thumbnail_image":212,"tags":214},"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":213},"99b01cc2-11ac-4449-9927-a1a7116347df",[215,216,217],"howto","java","editor",{"id":219,"title":220,"slug":221,"excerpt":222,"thumbnail_image":223,"tags":225},"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":224},"b5352a4b-f274-4489-aca9-36814947d514",[184,226],"distro",{"id":228,"title":229,"slug":230,"excerpt":231,"thumbnail_image":232,"tags":234},"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":233},"ff111270-80c2-4ccb-83d7-d5ab8c021201",[235,236,237],"web-development","frontend","framework",{"id":239,"title":240,"slug":241,"excerpt":242,"thumbnail_image":243,"tags":245},"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":244},"98e85e76-9e7b-42d1-b989-7c75e7f49abc",[246,247,248],"programming","types","comparison",{"id":250,"title":251,"slug":252,"excerpt":253,"thumbnail_image":254,"tags":256},"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":255},"d5e879fa-5cd0-4015-a155-b0cc69ff12fb",[257,258,235],"tailwind-css","css-framework",{"id":260,"title":261,"slug":262,"excerpt":263,"thumbnail_image":264,"tags":266},"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":265},"f615bb1f-8e36-4d6c-9c2c-f1629407173c",[109,106,235],{"id":268,"title":269,"slug":270,"excerpt":271,"thumbnail_image":272,"tags":274},"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":273},"8444bdbc-f60c-4d8b-8593-1b49400e8659",[275,276,277],"nuxt-3","vue-3","frontend-framework",{"id":279,"title":280,"slug":281,"excerpt":282,"thumbnail_image":283,"tags":285},"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":284},"84847c9e-70ab-4dcc-bed7-7be50165f7f4",[153,286,56,287,288],"python","asgi","pydantic",{"id":290,"title":291,"slug":292,"excerpt":293,"thumbnail_image":294,"tags":296},"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":295},"487500a0-9e09-469d-8736-1583c5ea83aa",[56,297,298,131,299,84],"grpc","rest-api","protobuf",{"id":301,"title":302,"slug":303,"excerpt":304,"thumbnail_image":305,"tags":307},"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":306},"21ab769d-6f82-4a22-be11-17ac16e9fb6b",[56,51,119,53,84,96,52],{"id":309,"title":310,"slug":311,"excerpt":312,"thumbnail_image":313,"tags":315},"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":314},"1401f9e5-6359-404a-8d80-273ddee9a372",[56,93,84,316,94,153],"api",{"id":318,"title":319,"slug":320,"excerpt":321,"thumbnail_image":322,"tags":324},"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":323},"d9e76018-fbcc-4c69-ad42-8f75ff229ecd",[56,84,325,130,96],"event-queue",{"id":327,"title":328,"slug":329,"excerpt":330,"thumbnail_image":331,"tags":333},"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":332},"1942a5c9-c1f6-476d-9913-768f78d9d8eb",[334,335,336,337,338],"system-programming","rust","zig","c","memory-safety",{"id":43,"title":44,"slug":45,"excerpt":46,"thumbnail_image":340,"tags":341},{"id":49},[51,52,53,54,55,56],{"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",[94,56,350,351,352,286],"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,83,363,56],"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",[56,316,372,84,373,153,94],"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",[56,131,382,84,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",[56,83,153,361,391,84,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",[56,51,53,84,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",[56,410,411,412,131,96,413],"distributed-systems","observability","open-telemetry","tracing","\u003Cp>Query kalian mendadak lelet padahal data baru nembus jutaan \u003Cem>row\u003C/em>? Tenang, kalian nggak sendirian. 😅\u003C/p>\n\u003Cp>Seringnya, reaksi pertama kita itu buru-buru kepengen \u003Cem>upgrade\u003C/em> spek server database (\u003Cem>vertical scaling\u003C/em>). Padahal, dalam banyak kasus, akar masalahnya sepele aja: \u003Cem>index\u003C/em>-nya kurang, atau malah salah pasang.\u003C/p>\n\u003Cp>\u003Ca href=\"https://use-the-index-luke.com/\">\u003Cem>Index\u003C/em>\u003C/a> sendiri adalah salah satu fitur paling fundamental—tapi paling ngefek—buat nyepetin pencarian data di database relasional kayak PostgreSQL atau MySQL. Yuk, kita bedah bareng gimana sih kerjanya.\u003C/p>\n\u003Ch2 id=\"kenapa-pencarian-tanpa-index-itu-bikin-capek\">Kenapa Pencarian Tanpa \u003Cem>Index\u003C/em> Itu Bikin Capek?\u003C/h2>\n\u003Cp>Coba bayangin kalian lagi nyari definisi kata "Konkurensi" di ensiklopedia tebel setebel 1.000 halaman.\u003C/p>\n\u003Cp>Kalau kalian harus baca dari halaman 1, kata demi kata, sampai ketemu di halaman 642—capek, kan? 🤔 Lama pula. Cara brutal kayak gini di dunia database disebut \u003Cem>Full Table Scan\u003C/em>.\u003C/p>\n\u003Cp>Beda cerita kalau kalian langsung ngebuka bagian \u003Cem>index\u003C/em> di halaman paling belakang. Di situ kata "Konkurensi" udah disusun urut alfabetis, lengkap sama nomor halamannya. Tinggal lompat ke halaman 642, tanpa perlu nyisir lembar lainnya. Gaya kedua inilah yang disebut \u003Cem>Index Scan\u003C/em>.\u003C/p>\n\u003Cp>Simpel, tapi bedanya kayak langit dan bumi.\u003C/p>\n\u003Ch2 id=\"apa-sih-yang-terjadi-di-balik-layar\">Apa Sih yang Terjadi di Balik Layar?\u003C/h2>\n\u003Cp>Secara \u003Cem>default\u003C/em>, hampir semua database relasional pakai struktur data \u003Cem>B-Tree\u003C/em> (\u003Cem>Balanced Tree\u003C/em>) buat nyimpen \u003Cem>index\u003C/em>-nya.\u003C/p>\n\u003Cp>Struktur \u003Cem>B-Tree\u003C/em> bikin database bisa nyari data dengan kompleksitas waktu O(log N). Artinya, buat nyari 1 \u003Cem>row\u003C/em> di antara 1.000.000 \u003Cem>row\u003C/em>, database cuma perlu \u003Cstrong>sekitar 20 kali perbandingan\u003C/strong>. 😎 Jauh lebih hemat ketimbang ngecek sejuta \u003Cem>row\u003C/em> satu-satu.\u003C/p>\n\u003Cp>Jadi, ngebayangin \u003Cem>index\u003C/em> itu kayak nempelin tab penanda di buku catatan. Kalian nggak perlu baca semua halaman tiap kali mau nemu satu bab.\u003C/p>\n\u003Ch2 id=\"emang-ada-ruginya-pasang-index\">Emang Ada Ruginya Pasang \u003Cem>Index\u003C/em>?\u003C/h2>\n\u003Cp>Ada dong, nggak ada makan siang gratis. 😄\u003C/p>\n\u003Cp>\u003Cem>Index\u003C/em> itu butuh ruang \u003Cem>disk\u003C/em> tambahan buat nyimpen datanya yang udah terurut. Di samping itu, setiap kali ada data baru yang di-\u003Cem>insert\u003C/em> atau di-\u003Cem>update\u003C/em>, database harus ikut ngerapihin struktur \u003Cem>B-Tree\u003C/em>-nya.\u003C/p>\n\u003Cp>Efeknya, operasi \u003Cem>write\u003C/em> alias \u003Ccode>INSERT\u003C/code>, \u003Ccode>UPDATE\u003C/code>, dan \u003Ccode>DELETE\u003C/code> bisa jadi sedikit lebih lambat. Kerjaannya nambah, sih. Jadi, \u003Cem>index\u003C/em> itu \u003Cstrong>bukan barang yang makin banyak makin bagus\u003C/strong>, lho.\u003C/p>\n\u003Ch2 id=\"kapan-wajib-dipasang-kapan-mendingan-nggak\">Kapan Wajib Dipasang, Kapan Mendingan Nggak?\u003C/h2>\n\u003Cp>Gampangnya, pasang \u003Cem>index\u003C/em> di kolom yang jadi langganan \u003Cem>query\u003C/em> pencarian kalian.\u003C/p>\n\u003Cul>\n\u003Cli>Kolom yang sering muncul di klausa \u003Ccode>WHERE\u003C/code>—misalnya \u003Ccode>WHERE email = 'user@example.com'\u003C/code>.\u003C/li>\n\u003Cli>Kolom yang sering dipakai buat nggabungin tabel alias \u003Ccode>JOIN\u003C/code>.\u003C/li>\n\u003Cli>Kolom yang dipakai buat ngurutin (\u003Ccode>ORDER BY\u003C/code>) atau ngelempokin (\u003Ccode>GROUP BY\u003C/code>).\u003C/li>\n\u003C/ul>\n\u003Cp>Tapi, ada juga kondisi di mana \u003Cem>index\u003C/em> malah nggak ada gunanya:\u003C/p>\n\u003Cul>\n\u003Cli>Tabelnya kecil—cuma puluhan atau ratusan \u003Cem>row\u003C/em>—soalnya \u003Cem>Full Table Scan\u003C/em> justru lebih cepet.\u003C/li>\n\u003Cli>Kolom yang nilainya sering berubah (\u003Cem>frequent write\u003C/em>).\u003C/li>\n\u003Cli>Kolom dengan variasi nilai rendah (\u003Cem>low cardinality\u003C/em>), contohnya \u003Ccode>jenis_kelamin\u003C/code> yang isinya cuma \u003Ccode>L\u003C/code> atau \u003Ccode>P\u003C/code>.\u003C/li>\n\u003C/ul>\n\u003Cp>Kolom \u003Ccode>jenis_kelamin\u003C/code> itu ibarat nyari buku cuma berdasarkan warna sampulnya. Nggak ngebantu banyak, hehe.\u003C/p>\n\u003Ch2 id=\"contoh-bikin-index-di-sql\">Contoh Bikin \u003Cem>Index\u003C/em> di SQL\u003C/h2>\n\u003Cp>Misalkan kita punya tabel \u003Ccode>users\u003C/code> yang isinya jutaan \u003Cem>row\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\">SQL\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=\"--%20Query%20pencarian%20tanpa%20index%20(bisa%20lelet%20pas%20datanya%20jutaan)%0ASELECT%20*%20FROM%20users%20WHERE%20email%20%3D%20'daffa%40example.com'%3B%0A%0A--%20Membuat%20single-column%20index%20pada%20kolom%20email%0ACREATE%20INDEX%20idx_users_email%20ON%20users(email)%3B%0A%0A--%20Membuat%20composite%20index%20untuk%20WHERE%20dengan%20dua%20kolom%0ACREATE%20INDEX%20idx_users_status_created%20ON%20users(status%2C%20created_at)%3B\" 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\">-- Query pencarian tanpa index (bisa lelet pas datanya jutaan)\u003C/span>\u003C/span>\n\u003Cspan class=\"line\">\u003Cspan style=\"color:#F97583\">SELECT\u003C/span>\u003Cspan style=\"color:#F97583\"> *\u003C/span>\u003Cspan style=\"color:#F97583\"> FROM\u003C/span>\u003Cspan style=\"color:#E1E4E8\"> users \u003C/span>\u003Cspan style=\"color:#F97583\">WHERE\u003C/span>\u003Cspan style=\"color:#E1E4E8\"> email \u003C/span>\u003Cspan style=\"color:#F97583\">=\u003C/span>\u003Cspan style=\"color:#9ECBFF\"> 'daffa@example.com'\u003C/span>\u003Cspan style=\"color:#E1E4E8\">;\u003C/span>\u003C/span>\n\u003Cspan class=\"line\">\u003C/span>\n\u003Cspan class=\"line\">\u003Cspan style=\"color:#6A737D\">-- Membuat single-column index pada kolom email\u003C/span>\u003C/span>\n\u003Cspan class=\"line\">\u003Cspan style=\"color:#F97583\">CREATE\u003C/span>\u003Cspan style=\"color:#F97583\"> INDEX\u003C/span>\u003Cspan style=\"color:#B392F0\"> idx_users_email\u003C/span>\u003Cspan style=\"color:#F97583\"> ON\u003C/span>\u003Cspan style=\"color:#E1E4E8\"> users(email);\u003C/span>\u003C/span>\n\u003Cspan class=\"line\">\u003C/span>\n\u003Cspan class=\"line\">\u003Cspan style=\"color:#6A737D\">-- Membuat composite index untuk WHERE dengan dua kolom\u003C/span>\u003C/span>\n\u003Cspan class=\"line\">\u003Cspan style=\"color:#F97583\">CREATE\u003C/span>\u003Cspan style=\"color:#F97583\"> INDEX\u003C/span>\u003Cspan style=\"color:#B392F0\"> idx_users_status_created\u003C/span>\u003Cspan style=\"color:#F97583\"> ON\u003C/span>\u003Cspan style=\"color:#E1E4E8\"> users(\u003C/span>\u003Cspan style=\"color:#F97583\">status\u003C/span>\u003Cspan style=\"color:#E1E4E8\">, created_at);\u003C/span>\u003C/span>\u003C/code>\u003C/pre>\n  \u003C/div>\n\u003C/div>\u003Cp>Perhatiin, urutan kolom di \u003Cem>composite index\u003C/em> \u003Ccode>(status, created_at)\u003C/code> itu ngaruh. Kalau kalian cuma nyari berdasarkan \u003Ccode>created_at\u003C/code> doang tanpa \u003Ccode>status\u003C/code>, \u003Cem>index\u003C/em>-nya sering nggak kepake—karena urutannya nggak cocok sama pola \u003Cem>query\u003C/em>-nya.\u003C/p>\n\u003Ch2 id=\"jadi-gimana-cara-cerdas-pasang-index\">Jadi, Gimana Cara Cerdas Pasang \u003Cem>Index\u003C/em>?\u003C/h2>\n\u003Cp>Intinya, \u003Cem>index\u003C/em> itu kayak jalan pintas rahasia di dalam labirin data. Dengan konfigurasi \u003Cem>B-Tree\u003C/em> yang tepat, pencarian di antara jutaan \u003Cem>row\u003C/em> bisa kelar dalam sekejap, tanpa nguras \u003Cem>CPU\u003C/em> server.\u003C/p>\n\u003Cp>Kuncinya ada di \u003Cstrong>keseimbangan\u003C/strong>: pasang \u003Cem>index\u003C/em> di kolom yang jadi langganan \u003Ccode>WHERE\u003C/code>, \u003Ccode>JOIN\u003C/code>, atau \u003Ccode>ORDER BY\u003C/code>, tapi jangan berlebihan biar proses \u003Cem>write\u003C/em> tetap gesit dan \u003Cem>disk\u003C/em> tetap lega.\u003C/p>\n\u003Cp>Buat yang pengen ngebahas \u003Cem>indexing\u003C/em> lebih dalem, \u003Ca href=\"https://use-the-index-luke.com/\">use-the-index-luke.com\u003C/a> itu rujukan yang juara.\u003C/p>\n\u003Cp>Selamat ber-\u003Cem>indexing\u003C/em> ria, dan semoga \u003Cem>query\u003C/em> kalian selalu mulus di lorong \u003Cem>B-Tree\u003C/em>-nya! 👋\u003C/p>\n","\u003Cul>\n\u003Cli>\u003Cem>Index\u003C/em> ngerubah pencarian data dari \u003Cem>Full Table Scan\u003C/em> O(N) yang boros jadi \u003Cem>Index Scan\u003C/em> B-Tree O(log N) yang jauh lebih gesit.\u003C/li>\n\u003Cli>Klausa \u003Cem>WHERE\u003C/em>, \u003Cem>JOIN\u003C/em>, \u003Cem>ORDER BY\u003C/em>, dan \u003Cem>GROUP BY\u003C/em> adalah tempat \u003Cem>index\u003C/em> paling sering ngebantu mempercepat \u003Cem>query\u003C/em>.\u003C/li>\n\u003Cli>Harga yang dibayar adalah ruang \u003Cem>disk\u003C/em> tambahan dan beban \u003Cem>update\u003C/em> struktur \u003Cem>B-Tree\u003C/em> tiap operasi \u003Cem>write\u003C/em>.\u003C/li>\n\u003Cli>Tabel kecil atau kolom ber-\u003Cem>cardinality\u003C/em> rendah—kayak kolom \u003Ccode>jenis_kelamin\u003C/code>—justru nggak perlu dipasangi \u003Cem>index\u003C/em>.\u003C/li>\n\u003C/ul>\n",[417,420,423,431],{"id":327,"title":328,"slug":329,"excerpt":330,"thumbnail_image":418,"tags":419},{"id":332},[334,335,336,337,338],{"id":86,"title":87,"slug":88,"excerpt":89,"thumbnail_image":421,"tags":422},{"id":91},[56,84,93,94,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",[56,131,96,51,130,84,53],{"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",[129,130,56,96,131,132,286],[440,444,447,450,453,456],{"text":441,"depth":442,"id":443},"Kenapa Pencarian Tanpa Index Itu Bikin Capek?",2,"kenapa-pencarian-tanpa-index-itu-bikin-capek",{"text":445,"depth":442,"id":446},"Apa Sih yang Terjadi di Balik Layar?","apa-sih-yang-terjadi-di-balik-layar",{"text":448,"depth":442,"id":449},"Emang Ada Ruginya Pasang Index?","emang-ada-ruginya-pasang-index",{"text":451,"depth":442,"id":452},"Kapan Wajib Dipasang, Kapan Mendingan Nggak?","kapan-wajib-dipasang-kapan-mendingan-nggak",{"text":454,"depth":442,"id":455},"Contoh Bikin Index di SQL","contoh-bikin-index-di-sql",{"text":457,"depth":442,"id":458},"Jadi, Gimana Cara Cerdas Pasang Index?","jadi-gimana-cara-cerdas-pasang-index",1791045073392]