[{"data":1,"prerenderedAt":830},["ShallowReactive",2],{"tag-labels":3,"site-header":4,"article-garbage-collector-dituduh-bikin-aplikasi-lemot-id":72},{},{"featuredPost":5,"navigations":29},{"id":6,"title":7,"title_en":8,"slug":9,"excerpt":10,"excerpt_en":11,"has_translation":12,"published_at":13,"reading_time":14,"hidden_from_listing":15,"tags":16,"thumbnail_image":21,"og_image":22,"series":23,"authors":28},110,"Ketika Pilih Framework Cuma Biar Kelihatan Beda","When You Pick a Framework Just to Look Different","ketika-pilih-framework-cuma-biar-kelihatan-beda","Terakhir kali kamu milih framework atau library baru, itu karena masalahmu butuh alat itu, atau karena alatnya kedengaran keren dan belum banyak yang pakai? Pertanyaan ini nggak enak dijawab. Soalnya keputusan teknologi sering diambil dengan alasan yang nggak pernah ditulis di dokumen teknis mana pun.","The last time you chose a new framework or library, was it because your problem needed that tool, or because it sounded cool and few people around you were using it? That question is uncomfortable. Technology decisions are often made for reasons that never appear in any technical document.",true,"2026-10-06T15:25:21.000Z",5,false,[17,18,19,20],"karier","framework","opini","pengalaman",null,"\u002Fog\u002Fketika-pilih-framework-cuma-biar-kelihatan-beda.png",{"id":24,"title":25,"title_en":26,"slug":27},9,"Artikel","Articles","all",[],[30,46,67],{"collection":31,"item":32},"series",{"__typename":31,"title":25,"title_en":26,"slug":27,"children_series":33},[34,38,42],{"title":35,"title_en":36,"slug":37},"Kecerdasan Artifisial","Artificial Intelligence","kecerdasan-artifisial",{"title":39,"title_en":40,"slug":41},"Konsep Dasar Pemrograman","Programming Fundamentals","konsep-dasar-pemrograman",{"title":43,"title_en":44,"slug":45},"Algoritma dan Struktur Data","Algorithms and Data Structures","algoritma-struktur-data",{"collection":31,"item":47},{"__typename":31,"title":48,"title_en":48,"slug":49,"children_series":50},"Tutorial","tutorial",[51,55,59,63],{"title":52,"title_en":53,"slug":54},"Belajar Python","Learning Python","belajar-python",{"title":56,"title_en":57,"slug":58},"Belajar Golang","Learning Go","belajar-golang",{"title":60,"title_en":61,"slug":62},"Belajar Java","Learning Java","belajar-java",{"title":64,"title_en":65,"slug":66},"Belajar Pascal","Learning Pascal","belajar-pascal",{"collection":31,"item":68},{"__typename":31,"title":69,"title_en":69,"slug":70,"children_series":71},"Lab","lab",[],{"article":73,"renderedBody":705,"renderedTakeaway":706,"latestArticles":707,"toc":804},{"id":74,"title":75,"title_en":76,"slug":77,"excerpt":78,"excerpt_en":79,"has_translation":12,"published_at":80,"reading_time":81,"hidden_from_listing":15,"tags":82,"thumbnail_image":21,"og_image":89,"series":90,"authors":699,"body_locale":700,"available_locales":701,"body":703,"takeway":704,"prerequisite":21},113,"Garbage Collector dituduh bikin aplikasi lemot. Seberapa adil tuduhan itu?","The Garbage Collector Gets Blamed for Slow Apps. How Fair Is That?","garbage-collector-dituduh-bikin-aplikasi-lemot","GC sering jadi tersangka utama tiap aplikasi melambat, dan banyak yang percaya dia jalan pakai timer tiap beberapa detik. Dua-duanya nggak sepenuhnya benar. Yuk bedah cara kerja GC dari dalam, plus satu pengecualian yang bikin Discord kesakitan tiap 2 menit. 🤔","GC is always the prime suspect when an app slows down, and many people believe it runs on a timer every few seconds. Both beliefs are only partly right. Let's open up how GC works inside, plus one exception that made Discord hurt every 2 minutes.","2026-10-09T01:34:00.000Z",7,[83,84,85,86,87,88],"backend","performance","golang","jvm","garbage-collector","memory","\u002Fog\u002Fgarbage-collector-dituduh-bikin-aplikasi-lemot.png",{"id":24,"title":25,"title_en":26,"slug":27,"description":21,"description_en":91,"articles":92,"children_series":692,"parent_series":21},"Everything that isn't a tutorial or a lab: explainers, opinions, and notes from building things.",[93,108,123,137,150,165,180,194,209,223,235,250,273,291,311,329,347,366,382,399,417,432,447,463,478,493,507,523,541,560,575,594,610,622,626,642,655,658,674],{"id":94,"title":95,"title_en":96,"slug":97,"excerpt":98,"excerpt_en":99,"has_translation":12,"published_at":100,"reading_time":14,"hidden_from_listing":15,"tags":101,"thumbnail_image":21,"og_image":105,"series":106,"authors":107},11,"Apa Kabar JavaScript? Rilis State of JS 2022","How's JavaScript Doing? The State of JS 2022 Results Are In","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?","The State of JS 2022 survey is out, and the respondent count jumped hard. Which frameworks and build tools actually stole the year?","2026-06-15T02:36:30.205Z",[102,103,104],"javascript","web","news","\u002Fog\u002Fapa-kabar-javascript-rilis-state-of-js-2022.png",{"id":24,"title":25,"title_en":26,"slug":27},[],{"id":109,"title":110,"title_en":111,"slug":112,"excerpt":113,"excerpt_en":114,"has_translation":12,"published_at":115,"reading_time":14,"hidden_from_listing":15,"tags":116,"thumbnail_image":21,"og_image":120,"series":121,"authors":122},12,"Buat PowerShell Lebih Berwarna dengan Starship","Make PowerShell More Colorful with 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!","Tired of PowerShell looking black, white, and stiff? Turn your terminal into something interactive, aesthetic, and colorful with Starship!","2026-06-15T02:37:24.143Z",[117,118,119],"shell","windows","powershell","\u002Fog\u002Fbuat-powershell-lebih-berwarna-dengan-starship.png",{"id":24,"title":25,"title_en":26,"slug":27},[],{"id":124,"title":125,"title_en":126,"slug":127,"excerpt":128,"excerpt_en":129,"has_translation":12,"published_at":130,"reading_time":14,"hidden_from_listing":15,"tags":131,"thumbnail_image":21,"og_image":134,"series":135,"authors":136},13,"Hal yang Perlu Diperhatikan Sebelum Pindah ke Linux","Things to Consider Before Switching to 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!","Tempted to migrate from Windows to Linux but still unsure? Learn the upsides, the downsides, and the prep you need before you actually switch.","2026-06-15T02:37:24.570Z",[132,118,133],"linux","foss","\u002Fog\u002Fhal-yang-perlu-diperhatikan-sebelum-pindah-ke-linux.png",{"id":24,"title":25,"title_en":26,"slug":27},[],{"id":138,"title":139,"title_en":140,"slug":141,"excerpt":142,"excerpt_en":143,"has_translation":12,"published_at":144,"reading_time":14,"hidden_from_listing":15,"tags":145,"thumbnail_image":21,"og_image":147,"series":148,"authors":149},15,"Kenapa Ada Banyak Sekali Distro Linux?","Why Are There So Many Linux Distros?","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!","Were you confused when installing Linux handed you dozens of distro options? You're not alone. Here's why there are so many, and what actually differs.","2026-06-15T02:38:14.569Z",[132,146],"distro","\u002Fog\u002Fkenapa-ada-banyak-sekali-distro-linux.png",{"id":24,"title":25,"title_en":26,"slug":27},[],{"id":151,"title":152,"title_en":153,"slug":154,"excerpt":155,"excerpt_en":156,"has_translation":12,"published_at":157,"reading_time":14,"hidden_from_listing":15,"tags":158,"thumbnail_image":21,"og_image":162,"series":163,"authors":164},16,"Menggunakan TypeScript dengan Node.js dan Express","Using TypeScript with Node.js and 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!","Want to build an Express server on Node.js but use TypeScript's nicer features? Here's the complete setup from scratch.","2026-06-15T02:38:30.735Z",[102,159,160,161],"nodejs","express","typescript","\u002Fog\u002Fmenggunakan-typescript-dengan-node-js-dan-express.png",{"id":24,"title":25,"title_en":26,"slug":27},[],{"id":166,"title":167,"title_en":168,"slug":169,"excerpt":170,"excerpt_en":171,"has_translation":12,"published_at":172,"reading_time":14,"hidden_from_listing":15,"tags":173,"thumbnail_image":21,"og_image":177,"series":178,"authors":179},17,"Pemrograman Asynchronous vs Multithreading, Apa Sih Bedanya?","Asynchronous Programming vs Multithreading: What's the Real Difference?","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!","You keep hearing asynchronous and multithreading while coding, but the difference stays fuzzy? Let's take it apart with an instant-noodle analogy you can follow.","2026-06-15T02:38:31.093Z",[174,175,176],"pemrograman","concurrency","tips-coding","\u002Fog\u002Fpemrograman-asynchronous-dan-multithreading-apa-bedanya.png",{"id":24,"title":25,"title_en":26,"slug":27},[],{"id":181,"title":182,"title_en":183,"slug":184,"excerpt":185,"excerpt_en":186,"has_translation":12,"published_at":187,"reading_time":14,"hidden_from_listing":15,"tags":188,"thumbnail_image":21,"og_image":191,"series":192,"authors":193},18,"React, Angular, atau Vue: Pilih Framework yang Mana?","React, Angular, or Vue: Which Framework Should You Pick?","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!","Stuck choosing between React, Angular, and Vue for your next web project? Here's a side-by-side look at what each one actually does well.","2026-06-15T02:38:31.431Z",[189,190,18],"web-development","frontend","\u002Fog\u002Freact-angular-vue-pilih-framework-yang-mana.png",{"id":24,"title":25,"title_en":26,"slug":27},[],{"id":195,"title":196,"title_en":197,"slug":198,"excerpt":199,"excerpt_en":200,"has_translation":12,"published_at":201,"reading_time":14,"hidden_from_listing":15,"tags":202,"thumbnail_image":21,"og_image":206,"series":207,"authors":208},19,"Static Typing dan Dynamic Typing: Apa Bedanya?","Static Typing vs Dynamic Typing: What's the Difference?","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!","Ever wondered why Java makes you declare a type while Python just takes the value? Here's the difference between static typing and dynamic typing.","2026-06-15T02:39:15.869Z",[203,204,205],"programming","types","comparison","\u002Fog\u002Fstatic-typing-dan-dynamic-typing-apa-bedanya.png",{"id":24,"title":25,"title_en":26,"slug":27},[],{"id":210,"title":211,"title_en":212,"slug":213,"excerpt":214,"excerpt_en":215,"has_translation":12,"published_at":216,"reading_time":14,"hidden_from_listing":15,"tags":217,"thumbnail_image":21,"og_image":220,"series":221,"authors":222},20,"Tailwind v3.0 Rilis: Ada JIT, Arbitrary Values, dan Banyak Lagi!","Tailwind v3.0 Is Out: JIT, Arbitrary Values, and Plenty More","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?","Tailwind CSS v3.0 shipped with a pile of performance upgrades that make styling more fun. Which features are worth trying first?","2026-06-15T02:39:25.372Z",[218,219,189],"tailwind-css","css-framework","\u002Fog\u002Ftailwind-v3-0-rilis-jit-arbitrary-dan-banyak-lagi.png",{"id":24,"title":25,"title_en":26,"slug":27},[],{"id":224,"title":225,"title_en":226,"slug":227,"excerpt":228,"excerpt_en":229,"has_translation":12,"published_at":230,"reading_time":14,"hidden_from_listing":15,"tags":231,"thumbnail_image":21,"og_image":232,"series":233,"authors":234},21,"TypeScript: JavaScript dengan Gaya dan Tipe Data Statis","TypeScript: JavaScript with Style and Static Types","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!","Tired of runtime errors in JavaScript? Meet TypeScript, which brings static typing so your code stays tidier and safer.","2026-06-15T02:39:25.712Z",[161,102,189],"\u002Fog\u002Ftypescript-javascript-dengan-gaya.png",{"id":24,"title":25,"title_en":26,"slug":27},[],{"id":236,"title":237,"title_en":238,"slug":239,"excerpt":240,"excerpt_en":241,"has_translation":12,"published_at":242,"reading_time":14,"hidden_from_listing":15,"tags":243,"thumbnail_image":21,"og_image":247,"series":248,"authors":249},22,"Yang Baru di Nuxt 3: Nitro Engine, Vite, dan Fitur Keren Lainnya","What's New in Nuxt 3: Nitro Engine, Vite, and Other Sharp Features","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?","Nuxt 3 brings a sweeping architecture change to line up with Vue 3. Here's what got faster and which new features are worth trying.","2026-06-15T02:39:26.086Z",[244,245,246],"nuxt-3","vue-3","frontend-framework","\u002Fog\u002Fyang-baru-di-nuxt-3-nitro-vite-dan-banyak-lagi.png",{"id":24,"title":25,"title_en":26,"slug":27},[],{"id":251,"title":252,"title_en":253,"slug":254,"excerpt":255,"excerpt_en":256,"has_translation":12,"published_at":257,"reading_time":258,"hidden_from_listing":15,"tags":259,"thumbnail_image":21,"og_image":264,"series":265,"authors":266},23,"Kenapa Pakai FastAPI dan Kenapa Dia Kenceng Banget?","Why Use FastAPI, and Why Is It So Fast?","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!","You keep hearing about FastAPI but still wonder how it can keep pace with NodeJS and Go? Let's take apart ASGI, the Pydantic magic, and the automatic docs.","2026-08-16T13:22:46.956Z",4,[260,261,83,262,263],"fastapi","python","asgi","pydantic","\u002Fog\u002Fkenapa-pakai-fastapi-dan-kenapa-dia-kenceng-banget.png",{"id":24,"title":25,"title_en":26,"slug":27},[267],{"authors_id":268},{"id":269,"name":270,"slug":271,"role":272,"profile_picture":21},2,"Inva","inva","Writer",{"id":274,"title":275,"title_en":276,"slug":277,"excerpt":278,"excerpt_en":279,"has_translation":12,"published_at":280,"reading_time":258,"hidden_from_listing":15,"tags":281,"thumbnail_image":21,"og_image":286,"series":287,"authors":288},24,"Kenapa Butuh Rate Limiting?","Why Do You Need 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!","Has your login endpoint ever been hammered by a bot trying thousands of passwords in a single minute? Here is why rate limiting is mandatory, and how to wire it into FastAPI.","2026-08-17T04:00:27.728Z",[83,282,283,284,285,260],"rate-limiting","system-design","api","redis","\u002Fog\u002Fkenapa-butuh-rate-limiting.png",{"id":24,"title":25,"title_en":26,"slug":27},[289],{"authors_id":290},{"id":269,"name":270,"slug":271,"role":272,"profile_picture":21},{"id":292,"title":293,"title_en":294,"slug":295,"excerpt":296,"excerpt_en":297,"has_translation":12,"published_at":298,"reading_time":14,"hidden_from_listing":15,"tags":299,"thumbnail_image":21,"og_image":303,"series":304,"authors":305},25,"Kenapa Event Queue Bikin Backend Kalian Nggak Gampang Tumbang?","Why an Event Queue Keeps Your Backend From Collapsing","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!","You hit Buy Now and the success notice appears instantly, while an invoice, an email, and a push notification still have to be built behind the scenes. The secret is the event queue.","2026-08-17T04:11:23.685Z",[83,283,300,301,302],"event-queue","message-broker","architecture","\u002Fog\u002Fkenapa-event-queue-bikin-backend-kamu-nggak-gampang-tumbang.png",{"id":24,"title":25,"title_en":26,"slug":27},[306],{"authors_id":307},{"id":308,"name":309,"slug":310,"role":272,"profile_picture":21},1,"Daffa Izzuddin","izzudd",{"id":312,"title":313,"title_en":314,"slug":315,"excerpt":316,"excerpt_en":317,"has_translation":12,"published_at":318,"reading_time":14,"hidden_from_listing":15,"tags":319,"thumbnail_image":21,"og_image":324,"series":325,"authors":326},26,"REST API vs gRPC: Kapan Sebaiknya Mulai Pindah dari JSON?","REST API vs gRPC: When Should You Start Moving Off 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!","Has your microservice system started feeling heavy even though it only shuffles internal data? The server may not be the problem. Here is when REST + JSON still wins, and when gRPC is the answer.","2026-08-17T04:26:10.249Z",[83,320,321,322,323,283],"grpc","rest-api","microservices","protobuf","\u002Fog\u002Frest-api-vs-grpc-kapan-sebaiknya-pindah-dari-json.png",{"id":24,"title":25,"title_en":26,"slug":27},[327],{"authors_id":328},{"id":269,"name":270,"slug":271,"role":272,"profile_picture":21},{"id":330,"title":331,"title_en":332,"slug":333,"excerpt":334,"excerpt_en":335,"has_translation":12,"published_at":336,"reading_time":14,"hidden_from_listing":15,"tags":337,"thumbnail_image":21,"og_image":342,"series":343,"authors":344},27,"Background Worker & Task Queue: Jangan Jalankan Proses Berat di Request HTTP!","Background Workers & Task Queues: Don't Run Heavy Work Inside an HTTP Request","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!","You tap Create Account and the loading page spins for 15 seconds with no answer? The cause is classic. Here is why heavy work does not belong in an HTTP request.","2026-08-17T04:26:10.284Z",[83,338,339,260,340,285,341],"task-queue","celery","rabbitmq","async","\u002Fog\u002Fbackground-worker-task-queue-jangan-jalankan-proses-berat-di-http.png",{"id":24,"title":25,"title_en":26,"slug":27},[345],{"authors_id":346},{"id":308,"name":309,"slug":310,"role":272,"profile_picture":21},{"id":348,"title":349,"title_en":350,"slug":351,"excerpt":352,"excerpt_en":353,"has_translation":12,"published_at":354,"reading_time":14,"hidden_from_listing":15,"tags":355,"thumbnail_image":21,"og_image":361,"series":362,"authors":363},28,"Mengatasi N+1 Query Problem: Musuh Tersembunyi Performa Backend","Taming the N+1 Query Problem: The Hidden Enemy of Backend Performance","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!","You built an endpoint that only lists 50 posts with their author names, and the response takes 2-3 seconds? You may have hit N+1 Query. Here is the cause, and the cure.","2026-08-17T04:26:10.309Z",[356,357,358,359,360,84,83],"database","sql","orm","sqlalchemy","django","\u002Fog\u002Fmengatasi-n-plus-1-query-problem-musuh-tersembunyi-backend.png",{"id":24,"title":25,"title_en":26,"slug":27},[364],{"authors_id":365},{"id":308,"name":309,"slug":310,"role":272,"profile_picture":21},{"id":367,"title":368,"title_en":369,"slug":370,"excerpt":371,"excerpt_en":372,"has_translation":12,"published_at":373,"reading_time":258,"hidden_from_listing":15,"tags":374,"thumbnail_image":21,"og_image":377,"series":378,"authors":379},29,"Memahami Database Indexing: Rahasia Query Super Cepat","Understanding Database Indexing: The Secret to Very Fast Queries","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!","Your queries have gone sluggish even though the data only just crossed a million rows? Before you rush to upgrade the server, check the indexes. Here is how database indexing actually works.","2026-08-17T04:26:10.325Z",[356,357,375,376,84,83],"postgresql","indexing","\u002Fog\u002Fmemahami-database-indexing-rahasia-query-super-cepat.png",{"id":24,"title":25,"title_en":26,"slug":27},[380],{"authors_id":381},{"id":308,"name":309,"slug":310,"role":272,"profile_picture":21},{"id":383,"title":384,"title_en":385,"slug":386,"excerpt":387,"excerpt_en":388,"has_translation":12,"published_at":389,"reading_time":258,"hidden_from_listing":15,"tags":390,"thumbnail_image":21,"og_image":394,"series":395,"authors":396},31,"Mengenal Redis: Lebih dari Sekadar In-Memory Cache","Getting to Know Redis: More Than Just an 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!","Still treating Redis as nothing but a cache? It can be a leaderboard, a message broker, even a rate limiter. Let's take apart everything it can do.","2026-08-17T04:26:10.360Z",[285,83,391,392,393,261],"cache","nosql","in-memory","\u002Fog\u002Fmengenal-redis-lebih-dari-sekadar-in-memory-cache.png",{"id":24,"title":25,"title_en":26,"slug":27},[397],{"authors_id":398},{"id":308,"name":309,"slug":310,"role":272,"profile_picture":21},{"id":400,"title":401,"title_en":402,"slug":403,"excerpt":404,"excerpt_en":405,"has_translation":12,"published_at":406,"reading_time":258,"hidden_from_listing":15,"tags":407,"thumbnail_image":21,"og_image":412,"series":413,"authors":414},32,"Docker Compose untuk Developer Santai: Satu Perintah Buat Jalankan Semua Service","Docker Compose for the Relaxed Developer: One Command to Run Every 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!","Do you keep retyping `docker run` just to bring up the web app, the database, and the cache one at a time? Here is how to fold all of them into one file and one command.","2026-08-17T04:26:10.375Z",[408,409,410,411,83],"docker","docker-compose","devops","containers","\u002Fog\u002Fdocker-compose-untuk-developer-santai.png",{"id":24,"title":25,"title_en":26,"slug":27},[415],{"authors_id":416},{"id":308,"name":309,"slug":310,"role":272,"profile_picture":21},{"id":418,"title":419,"title_en":420,"slug":421,"excerpt":422,"excerpt_en":423,"has_translation":12,"published_at":424,"reading_time":258,"hidden_from_listing":15,"tags":425,"thumbnail_image":21,"og_image":427,"series":428,"authors":429},33,"Berkenalan dengan RabbitMQ: Si Kurir Pesan Serba Bisa","Meet RabbitMQ: The Versatile Message Courier","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!","You tap Pay Now and the success notice appears instantly, while the confirmation email only lands a few seconds later? The secret is one invisible courier. Meet RabbitMQ.","2026-08-17T04:26:10.388Z",[340,301,83,322,341,426],"queue","\u002Fog\u002Fberkenalan-dengan-rabbitmq-si-kurir-pesan-serba-bisa.png",{"id":24,"title":25,"title_en":26,"slug":27},[430],{"authors_id":431},{"id":269,"name":270,"slug":271,"role":272,"profile_picture":21},{"id":433,"title":434,"title_en":435,"slug":436,"excerpt":437,"excerpt_en":438,"has_translation":12,"published_at":439,"reading_time":258,"hidden_from_listing":15,"tags":440,"thumbnail_image":21,"og_image":442,"series":443,"authors":444},34,"Kenapa Backend Butuh Database Connection Pooling?","Why Does a Backend Need 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!","Ever hit Too many connections while server CPU is still lounging at 30%? The problem is not your queries, it is how the application talks to the database. Meet connection pooling.","2026-08-24T06:06:47.088Z",[83,356,375,441,283,84],"connection-pooling","\u002Fog\u002Fkenapa-backend-butuh-database-connection-pooling.png",{"id":24,"title":25,"title_en":26,"slug":27},[445],{"authors_id":446},{"id":269,"name":270,"slug":271,"role":272,"profile_picture":21},{"id":448,"title":449,"title_en":450,"slug":451,"excerpt":452,"excerpt_en":453,"has_translation":12,"published_at":454,"reading_time":14,"hidden_from_listing":15,"tags":455,"thumbnail_image":21,"og_image":458,"series":459,"authors":460},35,"Mengenal Idempotency Key: Rahasia Anti-Double Charge di API Pembayaran","Idempotency Keys: The Secret to No Double Charges in Payment APIs","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!","Ever had your connection stall right as you hit Pay, then panic-clicked three times? If the endpoint is not idempotent, the balance can be cut more than once. Meet the idempotency key.","2026-08-24T06:09:11.645Z",[83,284,456,283,457,260,285],"idempotency","payment","\u002Fog\u002Fmengenal-idempotency-key-rahasia-anti-double-charge-di-api-pembayaran.png",{"id":24,"title":25,"title_en":26,"slug":27},[461],{"authors_id":462},{"id":269,"name":270,"slug":271,"role":272,"profile_picture":21},{"id":464,"title":465,"title_en":466,"slug":467,"excerpt":468,"excerpt_en":469,"has_translation":12,"published_at":470,"reading_time":14,"hidden_from_listing":15,"tags":471,"thumbnail_image":21,"og_image":473,"series":474,"authors":475},36,"Mencegah Efek Domino di Mikroservis dengan Circuit Breaker Pattern","Stopping the Domino Effect in Microservices With the 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!","Ever had one minor feature go slow and take the checkout page and login down with it? That is a cascading failure. Here is how the circuit breaker pattern saves your architecture.","2026-08-24T06:13:36.734Z",[83,322,472,283,302],"circuit-breaker","\u002Fog\u002Fmencegah-efek-domino-di-mikroservis-dengan-circuit-breaker-pattern.png",{"id":24,"title":25,"title_en":26,"slug":27},[476],{"authors_id":477},{"id":269,"name":270,"slug":271,"role":272,"profile_picture":21},{"id":479,"title":480,"title_en":481,"slug":482,"excerpt":483,"excerpt_en":484,"has_translation":12,"published_at":485,"reading_time":14,"hidden_from_listing":15,"tags":486,"thumbnail_image":21,"og_image":488,"series":489,"authors":490},37,"Kenapa Backend Butuh Graceful Shutdown? Jangan Asal Cabut Kabel Server!","Why Does a Backend Need Graceful Shutdown? Don't Yank the Server Cable","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!","You deploy the backend and seconds later monitoring floods with 502 Bad Gateway alerts. The balance was cut but the order status never reached the database. Here is why graceful shutdown is mandatory.","2026-08-24T06:15:59.150Z",[83,410,260,408,487,283,302],"kubernetes","\u002Fog\u002Fkenapa-backend-butuh-graceful-shutdown-jangan-asal-cabut-kabel-server.png",{"id":24,"title":25,"title_en":26,"slug":27},[491],{"authors_id":492},{"id":269,"name":270,"slug":271,"role":272,"profile_picture":21},{"id":494,"title":495,"title_en":496,"slug":497,"excerpt":498,"excerpt_en":499,"has_translation":12,"published_at":500,"reading_time":14,"hidden_from_listing":15,"tags":501,"thumbnail_image":21,"og_image":502,"series":503,"authors":504},38,"Optimistic vs Pessimistic Locking: Mengatasi Rebutan Data di Database","Optimistic vs Pessimistic Locking: Handling the Data Fight in a 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*!","A thousand people tap Buy Now in the same second, fighting over the last ticket. What happens on your server? Here is pessimistic against optimistic locking.","2026-08-24T06:16:37.198Z",[83,356,175,375,283,302,357],"\u002Fog\u002Foptimistic-vs-pessimistic-locking-mengatasi-rebutan-data-di-database.png",{"id":24,"title":25,"title_en":26,"slug":27},[505],{"authors_id":506},{"id":269,"name":270,"slug":271,"role":272,"profile_picture":21},{"id":508,"title":509,"title_en":510,"slug":511,"excerpt":512,"excerpt_en":513,"has_translation":12,"published_at":514,"reading_time":14,"hidden_from_listing":15,"tags":515,"thumbnail_image":21,"og_image":518,"series":519,"authors":520},39,"Database Sharding vs Partitioning: Kapan Data Perlu Dipecah?","Database Sharding vs Partitioning: When Does Data Need Splitting?","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*!","Your transaction table has crossed a billion rows and every report query spikes CPU to 100%? Before splitting data blindly, understand the difference between sharding and partitioning.","2026-08-24T06:17:10.104Z",[83,356,375,283,302,516,517],"sharding","scaling","\u002Fog\u002Fdatabase-sharding-vs-partitioning-kapan-data-perlu-dipecah.png",{"id":24,"title":25,"title_en":26,"slug":27},[521],{"authors_id":522},{"id":269,"name":270,"slug":271,"role":272,"profile_picture":21},{"id":524,"title":525,"title_en":526,"slug":527,"excerpt":528,"excerpt_en":529,"has_translation":12,"published_at":530,"reading_time":14,"hidden_from_listing":15,"tags":531,"thumbnail_image":21,"og_image":536,"series":537,"authors":538},40,"Menyelami Distributed Tracing: Melacak Jejak Request di Balik Keruwetan Microservices","Inside Distributed Tracing: Following a Request Through Microservice Chaos","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!","One Checkout click in your backend can trigger dozens of network calls between services, but when one is slow, which service is at fault? Logs alone cannot answer that. Here is distributed tracing.","2026-08-31T02:33:31.602Z",[83,532,533,534,322,302,535],"distributed-systems","observability","open-telemetry","tracing","\u002Fog\u002Fmenyelami-distributed-tracing-melacak-jejak-request-microservices.png",{"id":24,"title":25,"title_en":26,"slug":27},[539],{"authors_id":540},{"id":269,"name":270,"slug":271,"role":272,"profile_picture":21},{"id":542,"title":543,"title_en":544,"slug":545,"excerpt":546,"excerpt_en":547,"has_translation":12,"published_at":548,"reading_time":14,"hidden_from_listing":15,"tags":549,"thumbnail_image":21,"og_image":555,"series":556,"authors":557},41,"Log Aggregation Modern dengan Grafana Loki dan Vector: Hemat Storage Tanpa Indeks Raksasa","Modern Log Aggregation With Grafana Loki and Vector: Save Storage Without a Giant Index","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!","Your Elasticsearch cluster is greedy for RAM and wasteful with storage? Not every word in a log needs indexing. Meet the duo of Grafana Loki and Vector, far kinder to your wallet.","2026-09-01T15:45:01.066Z",[83,550,551,552,553,554,410,283],"observa","logging","grafana","loki","vector","\u002Fog\u002Flog-aggregation-modern-grafana-loki-vector-hemat-storage.png",{"id":24,"title":25,"title_en":26,"slug":27},[558],{"authors_id":559},{"id":269,"name":270,"slug":271,"role":272,"profile_picture":21},{"id":561,"title":562,"title_en":562,"slug":563,"excerpt":564,"excerpt_en":565,"has_translation":12,"published_at":566,"reading_time":14,"hidden_from_listing":15,"tags":567,"thumbnail_image":21,"og_image":570,"series":571,"authors":572},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!","You already know why *rate limiting* is mandatory, but the difference between Token Bucket, Leaky Bucket, Fixed Window, and Sliding Window is still fuzzy. Let's put all four algorithms side by side and find the one that fits your API.","2026-09-09T01:57:55.886Z",[83,283,282,285,568,302,569],"api-gateway","traffict-management","\u002Fog\u002Frate-limiting-algorithms-token-bucket-leaky-bucket-sliding-window.png",{"id":24,"title":25,"title_en":26,"slug":27},[573],{"authors_id":574},{"id":269,"name":270,"slug":271,"role":272,"profile_picture":21},{"id":576,"title":577,"title_en":578,"slug":579,"excerpt":580,"excerpt_en":581,"has_translation":12,"published_at":582,"reading_time":14,"hidden_from_listing":15,"tags":583,"thumbnail_image":21,"og_image":589,"series":590,"authors":591},46,"Mengapa C Mulai Ditinggalkan: Duel Filosofi Keamanan Rust vs Kesederhanaan Zig","Why C Is Being Left Behind: Rust's Safety Philosophy vs Zig's Simplicity","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!","Have you heard that around 70% of critical security holes in modern software come from C? Yes, the language the internet is built on. Let's unpack the philosophy duel between Rust and Zig and see which one fits your project.","2026-09-09T02:19:05.266Z",[584,585,586,587,588],"system-programming","rust","zig","c","memory-safety","\u002Fog\u002Fmengapa-c-mulai-ditinggalkan-duel-filosofi-rust-vs-zig.png",{"id":24,"title":25,"title_en":26,"slug":27},[592],{"authors_id":593},{"id":269,"name":270,"slug":271,"role":272,"profile_picture":21},{"id":595,"title":596,"title_en":597,"slug":598,"excerpt":599,"excerpt_en":600,"has_translation":12,"published_at":601,"reading_time":81,"hidden_from_listing":15,"tags":602,"thumbnail_image":21,"og_image":607,"series":608,"authors":609},107,"Cara kamu pakai AI lebih menentukan daripada apakah kamu pakai AI","How You Use AI Matters More Than Whether You Use AI","cara-pakai-ai-menentukan-pemahaman-kode","Fiturnya selesai, test-nya hijau, dan dua hari kemudian kamu baca kodenya kayak kode orang lain. Ternyata ada satu cara pakai AI yang bikin kamu paham lebih baik daripada nggak pakai AI sama sekali. Yuk lihat datanya.","The feature is done, the tests are green, and two days later you read the code like a stranger wrote it. It turns out one way of using AI leaves you understanding more than not using AI at all. Here is the data.","2026-10-10T11:08:29.000Z",[603,604,605,606],"ai","belajar","kognitif","ai-assisted-coding","\u002Fog\u002Fcara-pakai-ai-menentukan-pemahaman-kode.png",{"id":24,"title":25,"title_en":26,"slug":27},[],{"id":611,"title":612,"title_en":613,"slug":614,"excerpt":615,"excerpt_en":616,"has_translation":12,"published_at":13,"reading_time":14,"hidden_from_listing":15,"tags":617,"thumbnail_image":21,"og_image":619,"series":620,"authors":621},109,"State of JS 2025 Bilang Developer Cuma Pakai 2,6 Framework Sepanjang Karier","State of JS 2025 Says Developers Use Only 2.6 Frameworks in a Whole Career","state-of-js-2025-developer-cuma-pakai-2-6-framework","Coba hitung semua framework yang pernah kamu coba, lalu potong jadi yang beneran dipakai buat kerjaan. Daftarnya jauh lebih pendek dari dugaan. State of JS 2025 nanya ke 13.002 developer, dan rata-ratanya cuma 2,6. Yuk, lihat angkanya bareng-bareng!","Try counting every framework you have ever touched, then cut the list down to what you actually used for work. It comes out far shorter than you would guess. State of JS 2025 asked 13,002 developers, and the average is only 2.6.",[102,618,18,17],"survei","\u002Fog\u002Fstate-of-js-2025-developer-cuma-pakai-2-6-framework.png",{"id":24,"title":25,"title_en":26,"slug":27},[],{"id":6,"title":7,"title_en":8,"slug":9,"excerpt":10,"excerpt_en":11,"has_translation":12,"published_at":13,"reading_time":14,"hidden_from_listing":15,"tags":623,"thumbnail_image":21,"og_image":22,"series":624,"authors":625},[17,18,19,20],{"id":24,"title":25,"title_en":26,"slug":27},[],{"id":627,"title":628,"title_en":629,"slug":630,"excerpt":631,"excerpt_en":632,"has_translation":12,"published_at":633,"reading_time":634,"hidden_from_listing":15,"tags":635,"thumbnail_image":21,"og_image":637,"series":638,"authors":639},111,"Rust Masuk Kernel Linux: Revolusi Nyata atau Cuma Euforia RIIR?","Rust Enters the Linux Kernel: A Real Revolution or Just RIIR Euphoria?","rust-di-kernel-linux-revolusi-atau-cuma-hype","Selama lebih dari 30 tahun kernel Linux cuma mau bahasa C, lalu tiba-tiba Rust resmi masuk di Linux 6.1. Itu revolusi beneran atau cuma kebawa euforia meme Rewrite It In Rust? Yuk lihat datanya, bukan cuma opininya.","For more than 30 years the Linux kernel only wanted C, then Rust officially landed in Linux 6.1. Is that a real revolution, or just the pull of the Rewrite It In Rust meme? Let's look at the data, not the opinions.","2026-10-07T03:40:24.000Z",6,[585,132,636,584,588],"kernel","\u002Fog\u002Frust-di-kernel-linux-revolusi-atau-cuma-hype.png",{"id":24,"title":25,"title_en":26,"slug":27},[640],{"authors_id":641},{"id":308,"name":309,"slug":310,"role":272,"profile_picture":21},{"id":643,"title":644,"title_en":645,"slug":646,"excerpt":647,"excerpt_en":648,"has_translation":12,"published_at":649,"reading_time":14,"hidden_from_listing":15,"tags":650,"thumbnail_image":21,"og_image":652,"series":653,"authors":654},112,"Aplikasimu lambat, dan kamu udah kepikiran ganti bahasa. Tunggu dulu","Your App Is Slow, and You're Already Thinking About Changing Languages. Wait.","aplikasimu-lambat-dan-kamu-udah-kepikiran-ganti-bahasa-tunggu-dulu","Ada endpoint yang grafiknya spike tiap beberapa menit, dan kepikiran buat pindah dari Go ke Rust? Discord dan Cloudflare beneran melakukannya — tapi cuma setelah kehabisan cara lain dan punya datanya. Yuk, bedah gejala mana yang beneran butuh rewrite, dan mana yang cuma butuh profiling. 🤔","An endpoint spikes every few minutes, and you are thinking of moving from Go to Rust? Discord and Cloudflare really did it, but only after running out of other options and having the data. Let's sort out which symptoms need a rewrite and which only need a profiler.","2026-10-08T09:40:00.000Z",[83,84,85,585,283,651],"profiling","\u002Fog\u002Faplikasimu-lambat-dan-kamu-udah-kepikiran-ganti-bahasa-tunggu-dulu.png",{"id":24,"title":25,"title_en":26,"slug":27},[],{"id":74,"title":75,"title_en":76,"slug":77,"excerpt":78,"excerpt_en":79,"has_translation":12,"published_at":80,"reading_time":81,"hidden_from_listing":15,"tags":82,"thumbnail_image":21,"og_image":89,"series":656,"authors":657},{"id":24,"title":25,"title_en":26,"slug":27},[],{"id":659,"title":660,"title_en":661,"slug":662,"excerpt":663,"excerpt_en":664,"has_translation":12,"published_at":665,"reading_time":14,"hidden_from_listing":15,"tags":666,"thumbnail_image":21,"og_image":669,"series":670,"authors":671},118,"Belajar Idempotency dari Stok yang Keburu Kebeli","Learning Idempotency from Stock That Got Bought Too Soon","pub-sub-sendiri-lalu-belajar-idempotency","Tugas pertama saya di kerjaan pertama: sistem yang kewalahan menerima webhook. Saya putuskan membangun pub\u002Fsub sendiri dari nol, dan pelajaran yang akhirnya datang bukan dari situ — tapi dari stok gudang yang keburu kebeli orang.","My first task at my first job was a system drowning in webhooks. I decided to build my own pub\u002Fsub from scratch, and the lesson that finally landed came from somewhere else: warehouse stock that got bought before the count caught up.","2026-10-10T14:03:00.000Z",[456,667,339,340,668],"event-driven","post-mortem","\u002Fog\u002Fpub-sub-sendiri-lalu-belajar-idempotency.png",{"id":24,"title":25,"title_en":26,"slug":27},[672],{"authors_id":673},{"id":308,"name":309,"slug":310,"role":272,"profile_picture":21},{"id":675,"title":676,"title_en":677,"slug":678,"excerpt":679,"excerpt_en":680,"has_translation":12,"published_at":681,"reading_time":634,"hidden_from_listing":15,"tags":682,"thumbnail_image":21,"og_image":685,"series":686,"authors":687},124,"Rahasia Zero-Cost Abstraction di Rust, Dibedah dari Assembly","The Secret of Zero-Cost Abstractions in Rust, Opened Up from the Assembly","rahasia-zero-cost-abstraction-di-rust","\"Abstraksi tinggi selalu lebih lambat\" itu anggapan lama. Iterator Rust bisa menyamai loop manual, dan assembly-nya bisa kita baca sendiri. Yuk, kita bongkar!","\"Higher abstractions are always slower\" is an old assumption. Rust iterators can match a hand-written loop, and the assembly is there for you to read. Let's take it apart.","2026-10-13T05:19:00.000Z",[585,84,584,683,684],"compiler","optimasi","\u002Fog\u002Frahasia-zero-cost-abstraction-di-rust.png",{"id":24,"title":25,"title_en":26,"slug":27},[688,690],{"authors_id":689},{"id":308,"name":309,"slug":310,"role":272,"profile_picture":21},{"authors_id":691},{"id":308,"name":309,"slug":310,"role":272,"profile_picture":21},[693,695,697],{"id":694,"title":35,"slug":37,"description":21,"cover_image":21},8,{"id":109,"title":39,"slug":41,"description":696,"cover_image":21},"Mengenal konsep dasar pemrograman. Pada seri ini kita akan membahas tentang bagaimana cara berkutat dengan variabel, mengatur alur program dengan struktur kontrol, me-reuse kode dengan fungsi, dan aturan sintaks pada bahasa pemrograman. Konsep-konsep ini pastinya akan sangat berguna ketika kita mulai mengkoding ceria.",{"id":138,"title":43,"slug":45,"description":698,"cover_image":21},"Algoritma dan struktur data adalah konsep fundamental dalam dunia pemrograman. Keduanya sangat penting dalam menyelesaikan masalah yang kompleks dengan efisien dan efektif. Dalam seri ini kita akan membahas berbagai macam struktur data dan algoritma yang harapannya bisa bikin kode kita lebih efektif dan efisien. Yuk belajar ASD bareng Inva! 👋",[],"id",[702,700],"en","Kalau kamu pernah mampir ke forum pemrograman, kamu pasti pernah ketemu kalimat ini: \"mau aplikasi kencang? Jauhi bahasa ber-*GC* kayak Java, Go, C#, Python, atau *JavaScript*, pakai C, C++, atau Rust aja.\" Anggapan itu berumur panjang, dan di baliknya ada satu gambaran soal cara kerja GC yang perlu kita periksa.\n\nAda benarnya, sih: GC emang beneran makan sumber daya, dan itu bukan hal yang bisa dibantah. Cuma, dua hal yang sering dianggap pasti soal GC—dia jalan tiap beberapa detik, dan dia selalu bikin lemot—lebih baik kamu lihat sendiri mekanismenya. Di [artikel sebelumnya](https:\u002F\u002Finvasikode.com\u002Fp\u002Faplikasimu-lambat-dan-kamu-udah-kepikiran-ganti-bahasa-tunggu-dulu) kita udah lihat Discord dan Cloudflare menghadapi batasan ini dengan mengukur dulu, bukan menebak. Sekarang waktunya ngintip batasan itu dari dalam, yuk. 🙂\n\n## GC jalan pakai timer?\n\nSketsa paling gampang buat mbayangin cara kerja GC itu kira-kira begini:\n\n```text\nwhile true:\n    sleep(5)                        # tunggu 5 detik\n    cari_objek_yang_udah_nggak_dipakai()\n```\n\nTapi bentuk aslinya tuh nggak kayak gitu. Kalau benar ada *timer* di situ, servermu yang nganggur di tengah malam bakal tetap sibuk memindai memori tiap lima detik: CPU-nya kebakar, tagihan *cloud*-nya naik, dan yang dibersihkan cuma kekosongan. Untungnya, GC modern nggak sedungu itu. 😅\n\nYang dipakai hampir semua *runtime* modern sekarang adalah **ambang alokasi**, bukan jam. GC cuma bangun kalau memori yang dialokasikan aplikasi nyentuh batas tertentu. Di Go, batas itu diatur lewat *environment variable* `GOGC`, yang default-nya 100.\n\nAngka 100 itu artinya begini: GC membiarkan *heap* tumbuh sampai sekitar dua kali lipat memori hidup. Contohnya nih, kalau setelah satu siklus selesai memori yang masih hidup tinggal 10 MB, GC baru jalan lagi saat heap menyentuh 20 MB. Selama aplikasimu main di bawah angka itu, GC tidur nyenyak. Masuk akal kan?\n\nAngka 100-nya sendiri bisa kamu putar. Turunin ke 50, targetnya jadi sekitar 15 MB—GC lebih sering jalan, tapi RAM lebih hemat. Naikin ke 200, targetnya jadi sekitar 30 MB—GC lebih jarang jalan, tapi RAM lebih boros. Rumus lengkapnya ada di [panduan resmi GC Go](https:\u002F\u002Fgo.dev\u002Fdoc\u002Fgc-guide) kalau kamu mau ngitung sendiri, tapi intinya cuma itu.\n\nJadi jawabannya: nggak. GC nggak dijalankan pakai timer.\n\n### Tapi ada juga yang memang berbasis waktu\n\nDi sinilah pertanyaannya jadi lebih menarik: beberapa *runtime* memang punya pemicu berbasis waktu. Go salah satunya. Dia **memaksa GC jalan minimal tiap 2 menit**, terlepas dari seberapa lambat *heap*-nya tumbuh. Bukan gosip forum, itu ada sebagai [komentar di kode sumber Go](https:\u002F\u002Fgo.googlesource.com\u002Fgo\u002F+\u002Frefs\u002Fheads\u002Fmaster\u002Fsrc\u002Fruntime\u002Fproc.go): kalau sudah 2 menit nggak ada koleksi, satu siklus dipaksa jalan.\n\nKenapa sampai perlu? Karena ambang `GOGC` cuma berguna kalau aplikasimu rajin mengalokasi. Kalau *live heap*-nya besar tapi alokasinya lambat—persis seperti Read States di Discord—ambang itu nggak pernah kesentuh, dan timer 2 menit inilah yang akhirnya ambil alih. Setiap kali dia jalan, GC harus memindai seluruh *LRU cache* yang isinya jutaan *user*. Dari situ [blog Discord](https:\u002F\u002Fdiscord.com\u002Fblog\u002Fwhy-discord-is-switching-from-go-to-rust) sendiri nyimpulin kenapa grafik mereka punya *spike* yang datang rapi tiap sekitar 2 menit, dan kenapa usaha nge-*tuning* `GC percent` gagal total.\n\nGo bukan satu-satunya. V8 di Chrome punya [*idle-time* GC](https:\u002F\u002Fv8.dev\u002Fblog\u002Ffree-garbage-collection): kerja bersih-bersihnya dititipkan ke *idle task* yang dijadwalkan browser, bukan ke jadwal tetap. HotSpot malah menyediakan opsi [`G1PeriodicGCInterval`](https:\u002F\u002Fopenjdk.org\u002Fjeps\u002F346) yang memicu siklus GC berkala saat aplikasinya menganggur, biasanya buat balikin memori ke sistem operasi.\n\nSatu catatan jujur sebelum lanjut: kasus Discord itu terjadi di 2020, waktu Go masih di seri 1.8–1.10, dan cara kerja GC-nya sudah banyak berubah sejak itu. Yang nggak berubah: selama heap-mu gede dan isinya banyak *pointer*, memindainya tetap kerja yang harus dibayar. Perubahan itulah yang mendorong Go 1.19 menambah `GOMEMLIMIT`, supaya kamu bisa nentuin batas memori absolut, bukan cuma rasio.\n\nJadi kalau selama ini kamu mbayangin GC punya jadwal rutin, tebakanmu nggak ngawur. Yang bikin beda cuma porsinya: pemicu berbasis waktu itu jaring pengaman atau kerja sampingan, bukan mesin utamanya.\n\n## GC itu sebenarnya ngapain di dalam?\n\nGC tuh ibarat tukang bersih-bersih yang nggak keliling tiap jam: dia baru bergerak kalau ada yang memanggilnya. Dan hampir semua GC modern ikut keluarga **tracing**, dengan pola dasar yang sama: *mark*, lalu *sweep*. Biar kebayang, kita bedah dua fase itu satu-satu.\n\n### Gimana GC tahu objek mana yang masih hidup?\n\nGC nggak baca memori dari alamat nol secara buta. Dia mulai dari **GC roots**: variabel lokal di *stack*, variabel global, dan register CPU. Dari situ dia jalan ngikutin *pointer* seperti menelusuri pohon. Objek yang kejangkau ditandai hidup. Setelah penelusuran selesai, heap disapu dan semua yang nggak ketandai dikembalikan ke daftar bebas, siap dipakai ulang tanpa minta alokasi baru ke sistem operasi.\n\nSatu detail yang sering kelewat: GC Go itu *non-moving*. Objeknya nggak digeser-geser di memori. Bahasa lain ada yang menggeser objeknya (*compacting*) supaya memori lebih rapat, tapi harganya semua *pointer* harus ikut diperbarui. Java dan V8 memilih jalan tengah dengan **generational** *collector*, yang nebak bahwa objek muda lebih cepat mati, jadi nggak semua objek perlu diperiksa sama sering.\n\n### Tracing vs menghitung referensi\n\nAda dua keluarga besar di sini. *Tracing* dipakai Go, Java, dan V8. *Reference counting* dipakai Python dan Swift, dengan cara yang beda: tiap objek nyimpen jumlah referensinya, dan begitu angkanya nol, memori langsung dibebaskan. Python bahkan pakai dua-duanya sekaligus, karena *refcount* sendirian nggak bisa ngurus objek yang saling tunjuk membentuk lingkaran.\n\nPembagian ini penting buat diingat, soalnya dari sini kebijakan buat nge-*tune* GC jadi beda-beda: mulai dari `GOGC` dan `GOMEMLIMIT` di Go, pilihan *collector* G1 sampai ZGC di JVM, sampai pilihan buat mematikan sebagian GC di Python.\n\n## Terus biaya performanya di mana?\n\nKalau algoritmanya cuma jalanin *pointer*, apa yang sebenarnya kita bayar? Tiga hal ini:\n\n- Jeda singkat di peralihan fase. Di Go, aplikasi cuma benar-benar berhenti (*stop-the-world*) sebentar aja di transisi antara *mark* dan *sweep*, dan panjangnya sengaja dibikin nggak tumbuh seiring ukuran *heap*. Di JVM, [ZGC](https:\u002F\u002Fwiki.openjdk.org\u002Fdisplay\u002Fzgc\u002FMain) malah sudah jadi fitur produksi sejak JDK 15 dengan jeda sub-milidetik, bahkan di heap yang ukurannya bukan main.\n- Porsi CPU yang disedot GC. Fase *mark* ngambil sekitar 25% CPU, dan itu artinya *thread* aplikasimu rebutan prosesor. Yang paling bikin kesel: kalau alokasimu cepat, goroutine-mu sendiri ikut ditarik buat bantu GC (*GC assist*).\n- Overhead memori. `GOGC=100` artinya kamu nyiapin ruang sekitar dua kali lipat memori hidup. Naikin `GOGC`, GC jadi jarang jalan dan CPU lebih lega, tapi RAM lebih boros. Pasang `GOMEMLIMIT` terlalu ketat, kamu dapat masalah baru bernama *thrashing*: GC jalan terus-terusan, dan aplikasi bisa melambat sampai dua kali lipat.\n\nAda juga efek samping yang lebih susah diukur: metadata GC ikut memenuhi cache CPU, jadi data logika bisnismu terdepak ke RAM yang latensinya jauh lebih tinggi. Ini bukan angka yang keluar dari halaman dokumentasi mana pun, tapi masuk akal, dan Instagram sendiri nyebut soal naiknya *cache hit ratio* sebagai salah satu alasan mereka [mematikan GC di Python-nya](https:\u002F\u002Finstagram-engineering.com\u002Fdismissing-python-garbage-collection-at-instagram-4dca40b29172).\n\n## Kapan GC beneran jadi masalah?\n\nDi sinilah keputusannya bisa dipertanggungjawabkan, dan jawabannya bergantung pada seberapa ketat tenggat waktumu.\n\n- Web API dan *microservice* biasa. Bukan masalah. Jeda setengah milidetik di *request* yang latensi jaringannya 30–50 ms nggak akan terasa siapa pun, dan sebagai gantinya kamu dapat bahasa yang bebas dari satu kelas *bug* paling mahal. Microsoft sendiri [bilang sekitar 70% *CVE*](https:\u002F\u002Fwww.microsoft.com\u002Fen-us\u002Fmsrc\u002Fblog\u002F2019\u002F07\u002Fa-proactive-approach-to-more-secure-code) yang mereka perbaiki tiap tahun itu masalah *memory safety*, dan itu di kode C dan C++.\n- Game yang ngejar 60 FPS atau lebih. Coba bayangin deh, di 60 FPS satu *frame* cuma punya 16,6 ms, dan di 144 FPS sisanya tinggal 6,9 ms. Jeda GC 10 ms aja udah cukup bikin *frame*-nya patah-patah.\n- Kernel, *driver*, dan sistem *hard real-time*. Di sini yang penting bukan kecepatan rata-rata, tapi determinisme. Sistem yang cuma boleh telat mikrodetik nggak bisa nyerahin jadwalnya ke GC.\n- *High-frequency trading*. Yang diperdagangkan di sini mikrodetik. Distribusi jeda yang nggak bisa ditebak sama mahalnya dengan jedanya sendiri.\n\nLihat polanya: yang bikin GC jadi masalah bukan \"GC lambat\", tapi \"GC nggak bisa dijadwalkan\". Selama tenggat aplikasimu longgar, tuduhan itu jatuh dengan sendirinya.\n\n## Jadi, GC itu masalah atau bukan?\n\nBuat sebagian besar software yang kamu bangun, jawabannya: bukan. GC menukar sedikit RAM dan sedikit CPU dengan hilangnya satu kelas *bug* paling mahal yang pernah ada di dunia C—dan itu Microsoft sendiri yang bilang, bukan penggemar Go.\n\nInstagram malah bisa mematikan *cyclic collector* di Python-nya dan langsung [jalan 10% lebih efisien](https:\u002F\u002Finstagram-engineering.com\u002Fdismissing-python-garbage-collection-at-instagram-4dca40b29172) tanpa pindah bahasa. Tapi itu cuma masuk akal karena prosesnya berumur pendek dan sering di-*restart*.\n\nJadi yang perlu kita lakukan bukan menghindari GC, tapi tahu kapan dia mulai kebebanan. Kalau grafik *latency*-mu punya *spike* rapi tiap beberapa menit, tersangkanya mungkin GC, dan kamu bahkan bisa nebak dari durasi *spike*-nya. Tapi buktikan dulu pakai *profiler*, jangan cuma dari perasaan.\n\nSelamat membedah grafik *latency*-mu, dan semoga tersangkanya bukan yang salah tangkap. 👋\n","Garbage Collector modern memicu dirinya sendiri lewat ambang alokasi, bukan timer, dan buat sebagian besar aplikasi cara itu justru menguntungkan.\n- Jeda GC di runtime modern seperti Go dan ZGC sudah sub-milidetik dan nggak tumbuh seiring ukuran heap, jadi tuduhan \"GC bikin lemot\" cuma benar di sistem yang tenggat waktunya mikrodetik.\n- Harga memori dari GC itu nyata tapi bisa diputar: GOGC yang tinggi menghemat CPU dengan tambahan RAM, sementara GOMEMLIMIT yang terlalu ketat justru berujung thrashing.\n- Yang bikin GC jadi masalah bukan kecepatannya, tapi ketidakmampuan menjadwalkan jedanya, jadi selama tenggat aplikasimu longgar tersangkanya salah tangkap.\n- Kasus Instagram menunjukkan sebagian masalah GC bisa dibereskan lewat konfigurasi, dan itu pun cuma masuk akal kalau prosesnya memang berumur pendek.","\u003Cp>Kalau kamu pernah mampir ke forum pemrograman, kamu pasti pernah ketemu kalimat ini: "mau aplikasi kencang? Jauhi bahasa ber-\u003Cem>GC\u003C\u002Fem> kayak Java, Go, C#, Python, atau \u003Cem>JavaScript\u003C\u002Fem>, pakai C, C++, atau Rust aja." Anggapan itu berumur panjang, dan di baliknya ada satu gambaran soal cara kerja GC yang perlu kita periksa.\u003C\u002Fp>\n\u003Cp>Ada benarnya, sih: GC emang beneran makan sumber daya, dan itu bukan hal yang bisa dibantah. Cuma, dua hal yang sering dianggap pasti soal GC—dia jalan tiap beberapa detik, dan dia selalu bikin lemot—lebih baik kamu lihat sendiri mekanismenya. Di \u003Ca href=\"https:\u002F\u002Finvasikode.com\u002Fp\u002Faplikasimu-lambat-dan-kamu-udah-kepikiran-ganti-bahasa-tunggu-dulu\">artikel sebelumnya\u003C\u002Fa> kita udah lihat Discord dan Cloudflare menghadapi batasan ini dengan mengukur dulu, bukan menebak. Sekarang waktunya ngintip batasan itu dari dalam, yuk. 🙂\u003C\u002Fp>\n\u003Ch2 id=\"gc-jalan-pakai-timer\">GC jalan pakai timer?\u003C\u002Fh2>\n\u003Cp>Sketsa paling gampang buat mbayangin cara kerja GC itu kira-kira begini:\u003C\u002Fp>\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\u002F40 inline-block\">\u003C\u002Fspan>\n      \u003Cspan class=\"w-3 h-3 rounded-full bg-[#ffbd2e] border border-black\u002F40 inline-block\">\u003C\u002Fspan>\n      \u003Cspan class=\"w-3 h-3 rounded-full bg-[#27c93f] border border-black\u002F40 inline-block\">\u003C\u002Fspan>\n      \u003Cspan class=\"ml-2 font-mono font-bold text-xs uppercase tracking-wider text-gray-300\">TEXT\u003C\u002Fspan>\n    \u003C\u002Fdiv>\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=\"while%20true%3A%0A%20%20%20%20sleep(5)%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%23%20tunggu%205%20detik%0A%20%20%20%20cari_objek_yang_udah_nggak_dipakai()\" 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\u002Fpath>\n      \u003C\u002Fsvg>\n      \u003Cspan class=\"copy-text\">Copy\u003C\u002Fspan>\n    \u003C\u002Fbutton>\n  \u003C\u002Fdiv>\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\">\u003Ccode>while true:\n    sleep(5)                        # tunggu 5 detik\n    cari_objek_yang_udah_nggak_dipakai()\u003C\u002Fcode>\u003C\u002Fpre>\n  \u003C\u002Fdiv>\n\u003C\u002Fdiv>\u003Cp>Tapi bentuk aslinya tuh nggak kayak gitu. Kalau benar ada \u003Cem>timer\u003C\u002Fem> di situ, servermu yang nganggur di tengah malam bakal tetap sibuk memindai memori tiap lima detik: CPU-nya kebakar, tagihan \u003Cem>cloud\u003C\u002Fem>-nya naik, dan yang dibersihkan cuma kekosongan. Untungnya, GC modern nggak sedungu itu. 😅\u003C\u002Fp>\n\u003Cp>Yang dipakai hampir semua \u003Cem>runtime\u003C\u002Fem> modern sekarang adalah \u003Cstrong>ambang alokasi\u003C\u002Fstrong>, bukan jam. GC cuma bangun kalau memori yang dialokasikan aplikasi nyentuh batas tertentu. Di Go, batas itu diatur lewat \u003Cem>environment variable\u003C\u002Fem> \u003Ccode>GOGC\u003C\u002Fcode>, yang default-nya 100.\u003C\u002Fp>\n\u003Cp>Angka 100 itu artinya begini: GC membiarkan \u003Cem>heap\u003C\u002Fem> tumbuh sampai sekitar dua kali lipat memori hidup. Contohnya nih, kalau setelah satu siklus selesai memori yang masih hidup tinggal 10 MB, GC baru jalan lagi saat heap menyentuh 20 MB. Selama aplikasimu main di bawah angka itu, GC tidur nyenyak. Masuk akal kan?\u003C\u002Fp>\n\u003Cp>Angka 100-nya sendiri bisa kamu putar. Turunin ke 50, targetnya jadi sekitar 15 MB—GC lebih sering jalan, tapi RAM lebih hemat. Naikin ke 200, targetnya jadi sekitar 30 MB—GC lebih jarang jalan, tapi RAM lebih boros. Rumus lengkapnya ada di \u003Ca href=\"https:\u002F\u002Fgo.dev\u002Fdoc\u002Fgc-guide\">panduan resmi GC Go\u003C\u002Fa> kalau kamu mau ngitung sendiri, tapi intinya cuma itu.\u003C\u002Fp>\n\u003Cp>Jadi jawabannya: nggak. GC nggak dijalankan pakai timer.\u003C\u002Fp>\n\u003Ch3 id=\"tapi-ada-juga-yang-memang-berbasis-waktu\">Tapi ada juga yang memang berbasis waktu\u003C\u002Fh3>\n\u003Cp>Di sinilah pertanyaannya jadi lebih menarik: beberapa \u003Cem>runtime\u003C\u002Fem> memang punya pemicu berbasis waktu. Go salah satunya. Dia \u003Cstrong>memaksa GC jalan minimal tiap 2 menit\u003C\u002Fstrong>, terlepas dari seberapa lambat \u003Cem>heap\u003C\u002Fem>-nya tumbuh. Bukan gosip forum, itu ada sebagai \u003Ca href=\"https:\u002F\u002Fgo.googlesource.com\u002Fgo\u002F+\u002Frefs\u002Fheads\u002Fmaster\u002Fsrc\u002Fruntime\u002Fproc.go\">komentar di kode sumber Go\u003C\u002Fa>: kalau sudah 2 menit nggak ada koleksi, satu siklus dipaksa jalan.\u003C\u002Fp>\n\u003Cp>Kenapa sampai perlu? Karena ambang \u003Ccode>GOGC\u003C\u002Fcode> cuma berguna kalau aplikasimu rajin mengalokasi. Kalau \u003Cem>live heap\u003C\u002Fem>-nya besar tapi alokasinya lambat—persis seperti Read States di Discord—ambang itu nggak pernah kesentuh, dan timer 2 menit inilah yang akhirnya ambil alih. Setiap kali dia jalan, GC harus memindai seluruh \u003Cem>LRU cache\u003C\u002Fem> yang isinya jutaan \u003Cem>user\u003C\u002Fem>. Dari situ \u003Ca href=\"https:\u002F\u002Fdiscord.com\u002Fblog\u002Fwhy-discord-is-switching-from-go-to-rust\">blog Discord\u003C\u002Fa> sendiri nyimpulin kenapa grafik mereka punya \u003Cem>spike\u003C\u002Fem> yang datang rapi tiap sekitar 2 menit, dan kenapa usaha nge-\u003Cem>tuning\u003C\u002Fem> \u003Ccode>GC percent\u003C\u002Fcode> gagal total.\u003C\u002Fp>\n\u003Cp>Go bukan satu-satunya. V8 di Chrome punya \u003Ca href=\"https:\u002F\u002Fv8.dev\u002Fblog\u002Ffree-garbage-collection\">\u003Cem>idle-time\u003C\u002Fem> GC\u003C\u002Fa>: kerja bersih-bersihnya dititipkan ke \u003Cem>idle task\u003C\u002Fem> yang dijadwalkan browser, bukan ke jadwal tetap. HotSpot malah menyediakan opsi \u003Ca href=\"https:\u002F\u002Fopenjdk.org\u002Fjeps\u002F346\">\u003Ccode>G1PeriodicGCInterval\u003C\u002Fcode>\u003C\u002Fa> yang memicu siklus GC berkala saat aplikasinya menganggur, biasanya buat balikin memori ke sistem operasi.\u003C\u002Fp>\n\u003Cp>Satu catatan jujur sebelum lanjut: kasus Discord itu terjadi di 2020, waktu Go masih di seri 1.8–1.10, dan cara kerja GC-nya sudah banyak berubah sejak itu. Yang nggak berubah: selama heap-mu gede dan isinya banyak \u003Cem>pointer\u003C\u002Fem>, memindainya tetap kerja yang harus dibayar. Perubahan itulah yang mendorong Go 1.19 menambah \u003Ccode>GOMEMLIMIT\u003C\u002Fcode>, supaya kamu bisa nentuin batas memori absolut, bukan cuma rasio.\u003C\u002Fp>\n\u003Cp>Jadi kalau selama ini kamu mbayangin GC punya jadwal rutin, tebakanmu nggak ngawur. Yang bikin beda cuma porsinya: pemicu berbasis waktu itu jaring pengaman atau kerja sampingan, bukan mesin utamanya.\u003C\u002Fp>\n\u003Ch2 id=\"gc-itu-sebenarnya-ngapain-di-dalam\">GC itu sebenarnya ngapain di dalam?\u003C\u002Fh2>\n\u003Cp>GC tuh ibarat tukang bersih-bersih yang nggak keliling tiap jam: dia baru bergerak kalau ada yang memanggilnya. Dan hampir semua GC modern ikut keluarga \u003Cstrong>tracing\u003C\u002Fstrong>, dengan pola dasar yang sama: \u003Cem>mark\u003C\u002Fem>, lalu \u003Cem>sweep\u003C\u002Fem>. Biar kebayang, kita bedah dua fase itu satu-satu.\u003C\u002Fp>\n\u003Ch3 id=\"gimana-gc-tahu-objek-mana-yang-masih-hidup\">Gimana GC tahu objek mana yang masih hidup?\u003C\u002Fh3>\n\u003Cp>GC nggak baca memori dari alamat nol secara buta. Dia mulai dari \u003Cstrong>GC roots\u003C\u002Fstrong>: variabel lokal di \u003Cem>stack\u003C\u002Fem>, variabel global, dan register CPU. Dari situ dia jalan ngikutin \u003Cem>pointer\u003C\u002Fem> seperti menelusuri pohon. Objek yang kejangkau ditandai hidup. Setelah penelusuran selesai, heap disapu dan semua yang nggak ketandai dikembalikan ke daftar bebas, siap dipakai ulang tanpa minta alokasi baru ke sistem operasi.\u003C\u002Fp>\n\u003Cp>Satu detail yang sering kelewat: GC Go itu \u003Cem>non-moving\u003C\u002Fem>. Objeknya nggak digeser-geser di memori. Bahasa lain ada yang menggeser objeknya (\u003Cem>compacting\u003C\u002Fem>) supaya memori lebih rapat, tapi harganya semua \u003Cem>pointer\u003C\u002Fem> harus ikut diperbarui. Java dan V8 memilih jalan tengah dengan \u003Cstrong>generational\u003C\u002Fstrong> \u003Cem>collector\u003C\u002Fem>, yang nebak bahwa objek muda lebih cepat mati, jadi nggak semua objek perlu diperiksa sama sering.\u003C\u002Fp>\n\u003Ch3 id=\"tracing-vs-menghitung-referensi\">Tracing vs menghitung referensi\u003C\u002Fh3>\n\u003Cp>Ada dua keluarga besar di sini. \u003Cem>Tracing\u003C\u002Fem> dipakai Go, Java, dan V8. \u003Cem>Reference counting\u003C\u002Fem> dipakai Python dan Swift, dengan cara yang beda: tiap objek nyimpen jumlah referensinya, dan begitu angkanya nol, memori langsung dibebaskan. Python bahkan pakai dua-duanya sekaligus, karena \u003Cem>refcount\u003C\u002Fem> sendirian nggak bisa ngurus objek yang saling tunjuk membentuk lingkaran.\u003C\u002Fp>\n\u003Cp>Pembagian ini penting buat diingat, soalnya dari sini kebijakan buat nge-\u003Cem>tune\u003C\u002Fem> GC jadi beda-beda: mulai dari \u003Ccode>GOGC\u003C\u002Fcode> dan \u003Ccode>GOMEMLIMIT\u003C\u002Fcode> di Go, pilihan \u003Cem>collector\u003C\u002Fem> G1 sampai ZGC di JVM, sampai pilihan buat mematikan sebagian GC di Python.\u003C\u002Fp>\n\u003Ch2 id=\"terus-biaya-performanya-di-mana\">Terus biaya performanya di mana?\u003C\u002Fh2>\n\u003Cp>Kalau algoritmanya cuma jalanin \u003Cem>pointer\u003C\u002Fem>, apa yang sebenarnya kita bayar? Tiga hal ini:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Jeda singkat di peralihan fase. Di Go, aplikasi cuma benar-benar berhenti (\u003Cem>stop-the-world\u003C\u002Fem>) sebentar aja di transisi antara \u003Cem>mark\u003C\u002Fem> dan \u003Cem>sweep\u003C\u002Fem>, dan panjangnya sengaja dibikin nggak tumbuh seiring ukuran \u003Cem>heap\u003C\u002Fem>. Di JVM, \u003Ca href=\"https:\u002F\u002Fwiki.openjdk.org\u002Fdisplay\u002Fzgc\u002FMain\">ZGC\u003C\u002Fa> malah sudah jadi fitur produksi sejak JDK 15 dengan jeda sub-milidetik, bahkan di heap yang ukurannya bukan main.\u003C\u002Fli>\n\u003Cli>Porsi CPU yang disedot GC. Fase \u003Cem>mark\u003C\u002Fem> ngambil sekitar 25% CPU, dan itu artinya \u003Cem>thread\u003C\u002Fem> aplikasimu rebutan prosesor. Yang paling bikin kesel: kalau alokasimu cepat, goroutine-mu sendiri ikut ditarik buat bantu GC (\u003Cem>GC assist\u003C\u002Fem>).\u003C\u002Fli>\n\u003Cli>Overhead memori. \u003Ccode>GOGC=100\u003C\u002Fcode> artinya kamu nyiapin ruang sekitar dua kali lipat memori hidup. Naikin \u003Ccode>GOGC\u003C\u002Fcode>, GC jadi jarang jalan dan CPU lebih lega, tapi RAM lebih boros. Pasang \u003Ccode>GOMEMLIMIT\u003C\u002Fcode> terlalu ketat, kamu dapat masalah baru bernama \u003Cem>thrashing\u003C\u002Fem>: GC jalan terus-terusan, dan aplikasi bisa melambat sampai dua kali lipat.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>Ada juga efek samping yang lebih susah diukur: metadata GC ikut memenuhi cache CPU, jadi data logika bisnismu terdepak ke RAM yang latensinya jauh lebih tinggi. Ini bukan angka yang keluar dari halaman dokumentasi mana pun, tapi masuk akal, dan Instagram sendiri nyebut soal naiknya \u003Cem>cache hit ratio\u003C\u002Fem> sebagai salah satu alasan mereka \u003Ca href=\"https:\u002F\u002Finstagram-engineering.com\u002Fdismissing-python-garbage-collection-at-instagram-4dca40b29172\">mematikan GC di Python-nya\u003C\u002Fa>.\u003C\u002Fp>\n\u003Ch2 id=\"kapan-gc-beneran-jadi-masalah\">Kapan GC beneran jadi masalah?\u003C\u002Fh2>\n\u003Cp>Di sinilah keputusannya bisa dipertanggungjawabkan, dan jawabannya bergantung pada seberapa ketat tenggat waktumu.\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Web API dan \u003Cem>microservice\u003C\u002Fem> biasa. Bukan masalah. Jeda setengah milidetik di \u003Cem>request\u003C\u002Fem> yang latensi jaringannya 30–50 ms nggak akan terasa siapa pun, dan sebagai gantinya kamu dapat bahasa yang bebas dari satu kelas \u003Cem>bug\u003C\u002Fem> paling mahal. Microsoft sendiri \u003Ca href=\"https:\u002F\u002Fwww.microsoft.com\u002Fen-us\u002Fmsrc\u002Fblog\u002F2019\u002F07\u002Fa-proactive-approach-to-more-secure-code\">bilang sekitar 70% \u003Cem>CVE\u003C\u002Fem>\u003C\u002Fa> yang mereka perbaiki tiap tahun itu masalah \u003Cem>memory safety\u003C\u002Fem>, dan itu di kode C dan C++.\u003C\u002Fli>\n\u003Cli>Game yang ngejar 60 FPS atau lebih. Coba bayangin deh, di 60 FPS satu \u003Cem>frame\u003C\u002Fem> cuma punya 16,6 ms, dan di 144 FPS sisanya tinggal 6,9 ms. Jeda GC 10 ms aja udah cukup bikin \u003Cem>frame\u003C\u002Fem>-nya patah-patah.\u003C\u002Fli>\n\u003Cli>Kernel, \u003Cem>driver\u003C\u002Fem>, dan sistem \u003Cem>hard real-time\u003C\u002Fem>. Di sini yang penting bukan kecepatan rata-rata, tapi determinisme. Sistem yang cuma boleh telat mikrodetik nggak bisa nyerahin jadwalnya ke GC.\u003C\u002Fli>\n\u003Cli>\u003Cem>High-frequency trading\u003C\u002Fem>. Yang diperdagangkan di sini mikrodetik. Distribusi jeda yang nggak bisa ditebak sama mahalnya dengan jedanya sendiri.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>Lihat polanya: yang bikin GC jadi masalah bukan "GC lambat", tapi "GC nggak bisa dijadwalkan". Selama tenggat aplikasimu longgar, tuduhan itu jatuh dengan sendirinya.\u003C\u002Fp>\n\u003Ch2 id=\"jadi-gc-itu-masalah-atau-bukan\">Jadi, GC itu masalah atau bukan?\u003C\u002Fh2>\n\u003Cp>Buat sebagian besar software yang kamu bangun, jawabannya: bukan. GC menukar sedikit RAM dan sedikit CPU dengan hilangnya satu kelas \u003Cem>bug\u003C\u002Fem> paling mahal yang pernah ada di dunia C—dan itu Microsoft sendiri yang bilang, bukan penggemar Go.\u003C\u002Fp>\n\u003Cp>Instagram malah bisa mematikan \u003Cem>cyclic collector\u003C\u002Fem> di Python-nya dan langsung \u003Ca href=\"https:\u002F\u002Finstagram-engineering.com\u002Fdismissing-python-garbage-collection-at-instagram-4dca40b29172\">jalan 10% lebih efisien\u003C\u002Fa> tanpa pindah bahasa. Tapi itu cuma masuk akal karena prosesnya berumur pendek dan sering di-\u003Cem>restart\u003C\u002Fem>.\u003C\u002Fp>\n\u003Cp>Jadi yang perlu kita lakukan bukan menghindari GC, tapi tahu kapan dia mulai kebebanan. Kalau grafik \u003Cem>latency\u003C\u002Fem>-mu punya \u003Cem>spike\u003C\u002Fem> rapi tiap beberapa menit, tersangkanya mungkin GC, dan kamu bahkan bisa nebak dari durasi \u003Cem>spike\u003C\u002Fem>-nya. Tapi buktikan dulu pakai \u003Cem>profiler\u003C\u002Fem>, jangan cuma dari perasaan.\u003C\u002Fp>\n\u003Cp>Selamat membedah grafik \u003Cem>latency\u003C\u002Fem>-mu, dan semoga tersangkanya bukan yang salah tangkap. 👋\u003C\u002Fp>\n","\u003Cp>Garbage Collector modern memicu dirinya sendiri lewat ambang alokasi, bukan timer, dan buat sebagian besar aplikasi cara itu justru menguntungkan.\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Jeda GC di runtime modern seperti Go dan ZGC sudah sub-milidetik dan nggak tumbuh seiring ukuran heap, jadi tuduhan "GC bikin lemot" cuma benar di sistem yang tenggat waktunya mikrodetik.\u003C\u002Fli>\n\u003Cli>Harga memori dari GC itu nyata tapi bisa diputar: GOGC yang tinggi menghemat CPU dengan tambahan RAM, sementara GOMEMLIMIT yang terlalu ketat justru berujung thrashing.\u003C\u002Fli>\n\u003Cli>Yang bikin GC jadi masalah bukan kecepatannya, tapi ketidakmampuan menjadwalkan jedanya, jadi selama tenggat aplikasimu longgar tersangkanya salah tangkap.\u003C\u002Fli>\n\u003Cli>Kasus Instagram menunjukkan sebagian masalah GC bisa dibereskan lewat konfigurasi, dan itu pun cuma masuk akal kalau prosesnya memang berumur pendek.\u003C\u002Fli>\n\u003C\u002Ful>\n",[708,725,738,751,764,784],{"id":709,"title":710,"title_en":21,"slug":711,"excerpt":712,"excerpt_en":21,"has_translation":15,"published_at":713,"reading_time":634,"hidden_from_listing":15,"tags":714,"thumbnail_image":21,"og_image":716,"series":717,"authors":722},133,"Python Strings: the Badge That Only Worked for One Name","python-strings","The badge script printed the right name for the person who wrote it and the wrong name for everybody else. Slicing counts characters, and a name is words.","2026-10-28T13:00:00.000Z",[261,715],"string","\u002Fog\u002Fpython-strings.png",{"id":718,"title":719,"title_en":720,"slug":721},30,"Koleksi dan String","Collections and Strings","python-collections",[723],{"authors_id":724},{"id":308,"name":309,"slug":310,"role":272,"profile_picture":21},{"id":726,"title":727,"title_en":21,"slug":728,"excerpt":729,"excerpt_en":21,"has_translation":15,"published_at":730,"reading_time":634,"hidden_from_listing":15,"tags":731,"thumbnail_image":21,"og_image":733,"series":734,"authors":735},132,"Python Tuples: Why All Three Points Are the Same Point","python-tuples","Three points walk into a loop and come out identical. The list was never copied three times; the name was. A tuple makes that bug impossible.","2026-10-28T12:00:00.000Z",[261,732],"tuple","\u002Fog\u002Fpython-tuples.png",{"id":718,"title":719,"title_en":720,"slug":721},[736],{"authors_id":737},{"id":308,"name":309,"slug":310,"role":272,"profile_picture":21},{"id":739,"title":740,"title_en":21,"slug":741,"excerpt":742,"excerpt_en":21,"has_translation":15,"published_at":743,"reading_time":634,"hidden_from_listing":15,"tags":744,"thumbnail_image":21,"og_image":746,"series":747,"authors":748},131,"Python Sets: the Duplicate That Keeps Coming Back","python-sets","A de-duplication loop that works on clean data leaves four tags where there should be two. The bug is case, and the fix is a `set`.","2026-10-28T11:00:00.000Z",[261,745],"set","\u002Fog\u002Fpython-sets.png",{"id":718,"title":719,"title_en":720,"slug":721},[749],{"authors_id":750},{"id":308,"name":309,"slug":310,"role":272,"profile_picture":21},{"id":752,"title":753,"title_en":21,"slug":754,"excerpt":755,"excerpt_en":21,"has_translation":15,"published_at":756,"reading_time":634,"hidden_from_listing":15,"tags":757,"thumbnail_image":21,"og_image":759,"series":760,"authors":761},130,"Python Dictionaries: the Key That Isn't There","python-dictionary","A word counter dies the first time it meets a word twice. The fix is one line; what takes longer is knowing which of a dict's three lookups to reach for.","2026-10-28T10:00:00.000Z",[261,758],"dictionary","\u002Fog\u002Fpython-dictionary.png",{"id":718,"title":719,"title_en":720,"slug":721},[762],{"authors_id":763},{"id":308,"name":309,"slug":310,"role":272,"profile_picture":21},{"id":765,"title":766,"title_en":767,"slug":768,"excerpt":769,"excerpt_en":770,"has_translation":12,"published_at":771,"reading_time":14,"hidden_from_listing":15,"tags":772,"thumbnail_image":21,"og_image":779,"series":780,"authors":781},129,"Biar RAG nggak kena 504: pisahin jalur query dan ingestion","So Your RAG Stops Hitting 504: Split the Query Path From Ingestion","rag-pisah-jalur-query-dan-ingestion","Satu service RAG yang merangkap parsing dan menjawab kueri bakal tumbang pas ada yang upload PDF 200 halaman. Obatnya dua jalur dan satu queue.","One RAG service that both parses uploads and answers queries will fall over the moment someone uploads a 200-page PDF. The cure is two paths and one queue.","2026-10-22T01:30:00.000Z",[773,774,775,776,777,778],"rag","cloud-run","cloud-tasks","gcp","serverless","arsitektur","\u002Fog\u002Frag-pisah-jalur-query-dan-ingestion.png",{"id":694,"title":35,"title_en":36,"slug":37},[782],{"authors_id":783},{"id":308,"name":309,"slug":310,"role":272,"profile_picture":21},{"id":785,"title":786,"title_en":787,"slug":788,"excerpt":789,"excerpt_en":790,"has_translation":12,"published_at":791,"reading_time":634,"hidden_from_listing":15,"tags":792,"thumbnail_image":21,"og_image":799,"series":800,"authors":801},128,"Linear atau graf: cara mengatur banyak agent tanpa loop abadi","Linear or Graph: How to Run Many Agents Without an Eternal Loop","multi-agen-linear-atau-grafik","Satu agent dengan dua puluh tool gampang kacau. Begitu beberapa agent saling revisi, kamu butuh graf yang mendukung cycle dan angka yang membuatnya berhenti.","One agent with twenty tools gets messy fast. Once several agents revise each other, you need a graph that allows cycles and a number that makes it stop.","2026-10-21T16:05:00.000Z",[793,794,795,796,797,798],"multi-agent","langgraph","autogen","orkestrasi","checkpoint","llm","\u002Fog\u002Fmulti-agen-linear-atau-grafik.png",{"id":694,"title":35,"title_en":36,"slug":37},[802],{"authors_id":803},{"id":308,"name":309,"slug":310,"role":272,"profile_picture":21},[805,808,812,815,818,821,824,827],{"text":806,"depth":269,"id":807},"GC jalan pakai timer?","gc-jalan-pakai-timer",{"text":809,"depth":810,"id":811},"Tapi ada juga yang memang berbasis waktu",3,"tapi-ada-juga-yang-memang-berbasis-waktu",{"text":813,"depth":269,"id":814},"GC itu sebenarnya ngapain di dalam?","gc-itu-sebenarnya-ngapain-di-dalam",{"text":816,"depth":810,"id":817},"Gimana GC tahu objek mana yang masih hidup?","gimana-gc-tahu-objek-mana-yang-masih-hidup",{"text":819,"depth":810,"id":820},"Tracing vs menghitung referensi","tracing-vs-menghitung-referensi",{"text":822,"depth":269,"id":823},"Terus biaya performanya di mana?","terus-biaya-performanya-di-mana",{"text":825,"depth":269,"id":826},"Kapan GC beneran jadi masalah?","kapan-gc-beneran-jadi-masalah",{"text":828,"depth":269,"id":829},"Jadi, GC itu masalah atau bukan?","jadi-gc-itu-masalah-atau-bukan",1793295834109]