[{"data":1,"prerenderedAt":455},["ShallowReactive",2],{"site-header":3,"site-footer-license":37,"article-menyelami-distributed-tracing-melacak-jejak-request-microservices-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":413,"renderedTakeaway":414,"latestArticles":415,"toc":438},{"id":43,"title":44,"slug":45,"excerpt":46,"published_at":47,"thumbnail_image":48,"tags":50,"reading_time":58,"takeway":59,"body":60,"authors":61,"series":67},"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!","2026-08-31T02:33:31.602Z",{"id":49},"1ace92fa-b89c-4cef-ab75-4e4cd67a089c",[51,52,53,54,55,56,57],"backend","distributed-systems","observability","open-telemetry","microservices","architecture","tracing",null,"- Distributed Tracing jadi kunci buat memetakan alur request lintas service, sesuatu yang centralized logging tradisional nggak bisa pecahin sendiri.\n- Struktur dasarnya cuma dua: *trace* yang mewakili seluruh perjalanan request, dan *span* yang mencatat unit kerja spesifik di tiap service atau database.\n- Context propagation lewat *trace context* W3C—*header* `traceparent`—bikin correlation ID tetap nyambung antar-layanan.\n- OpenTelemetry jadi standar vendor-agnostic buat instrumentasi backend, gampang disambungin ke visualizer kayak Jaeger atau Grafana Tempo.","Waktu *backend* kalian masih monolit sederhana, urusan *debugging* terasa damai banget. Ada *request* lambat? Tinggal intip *log* server. Atau pasang *profiler* lokal. Semuanya jalan di satu proses, satu memori, dan satu *log file* yang teratur.\n\nBegitu arsitektur dipecah jadi belasan *microservice*, kondisinya berubah drastis, lho. Ada Auth Service. Ada Order Service. Ada Payment Gateway. Sampai Notification Service dan Inventory Service. Satu klik tombol \"Checkout\" bisa memicu puluhan *network call* asinkron antar-*service*.\n\nNah, pas pengguna ngeluh *checkout*-nya makan 8 detik lalu *timeout* 500, gimana kita tahu service mana yang bikin lambat? Query *database* di Inventory Service-nya? Atau ada antrean di *payment worker*? 🤔\n\nDi sinilah *Distributed Tracing* **hadir jadi penyelamat**.\n\n## Kenapa Centralized Logging Aja Nggak Cukup?\n\nBanyak *developer* ngira cukup pasang *centralized log aggregator*. Kayak Elasticsearch, Loki, atau Datadog. Padahal itu **belum cukup** buat beresin masalah di *microservices*.\n\nSaat ratusan ribu request masuk per detik, log dari berbagai service bercampur jadi lautan teks raksasa. Nyari keterkaitan antara log di Service A sama log di Service D jadi mimpi buruk. Soalnya nggak ada benang merah yang ngikatnya.\n\n*Centralized logging* ngasih tahu kita apa yang terjadi di dalam satu service. Distributed tracing ngasih tahu kita gimana request mengalir melintasi seluruh ekosistem. Itu dua hal yang **beda banget**.\n\n## Anatomi Distributed Tracing: Trace vs Span\n\nBuat paham distributed tracing, ada dua konsep fundamental yang wajib kita kuasai.\n\n*Trace* itu seluruh perjalanan sebuah transaksi atau request, dari awal sampai akhir. Bayangin trace kayak satu tiket perjalanan penumpang. Dari stasiun keberangkatan sampai tiba di tujuan akhir. Tiap trace punya ID unik global namanya `Trace ID`.\n\n*Span* adalah segmen atau unit kerja tunggal di dalam sebuah trace, nih. Satu trace terdiri dari satu atau banyak span. Semuanya membentuk struktur pohon (*directed acyclic graph*). Tiap span nyatet:\n\n- Nama operasi (misalnya `POST /orders`, `SELECT * FROM users`, atau `Publish to RabbitMQ`)\n- Waktu mulai dan durasi eksekusi\n- Metadata tambahan berupa *tags*/*attributes* (misalnya `http.status_code: 200`, `db.system: postgresql`, `user.id: 1042`)\n- Log peristiwa (*events*/*logs*) plus status *error*\n\nDengan visualisasi span, kita bisa lihat service mana yang paling lama. Itulah si *critical path*. Kita juga langsung tahu di titik mana error pertama meledak.\n\n## Cara Kerja Context Propagation\n\nPertanyaan terbesarnya: gimana Service B tahu request yang dia terima itu kelanjutan dari Service A?\n\nJawabannya *context propagation*. Pas Service A manggil Service B lewat HTTP, Service A nyisipin *Trace ID* dan *Parent Span ID* ke dalam *header request*. Begitu juga kalau lewat *message queue*.\n\nStandar industri modern yang paling banyak dipakai sekarang adalah *W3C Trace Context*. *Header* yang dikirim bentuknya `traceparent`:\n\n```http\ntraceparent: 00-4bf92f3577b34da6a3ce929d0e0e4736-00f067aa0ba902b7-01\n```\n\nHeader ini terdiri dari 4 bagian:\n1. `version`: versi spesifikasi W3C (saat ini `00`).\n2. `trace-id`: ID unik 16-byte buat keseluruhan trace (`4bf92f3577b34da6a3ce929d0e0e4736`).\n3. `parent-id` / `span-id`: ID unik 8-byte buat span pemanggil (`00f067aa0ba902b7`).\n4. `trace-flags`: opsi *flag*. Nilai `01` nandain span ini direkam atau *sampled*.\n\nBegitu Service B nerima request, *library tracing*-nya baca header itu. Dia ngekstrak Trace ID, lalu bikin *child span* baru di bawah *Parent ID* yang sesuai. Rantainya pun nyambung terus.\n\n## Implementasi Modern dengan OpenTelemetry\n\nDulu kita mungkin bingung milih. Ada OpenTracing, OpenCensus, *Jaeger client*, sampai *Zipkin client*. Untungnya industri udah sepakat pada satu standar terbuka. Namanya [OpenTelemetry](https://opentelemetry.io/) (OTel). Proyek *open source* ini di bawah naungan Cloud Native Computing Foundation (CNCF).\n\nOpenTelemetry nyediain SDK buat berbagai bahasa. Ada Python, Go, Node.js, dan Java. Ada juga *Collector* terpusat buat memproses dan neruskan data *telemetry*. Data itu lalu dikirim ke backend visualisasi kayak Jaeger, *Grafana Tempo*, atau Datadog.\n\nContoh sederhana instrumentasi otomatis di FastAPI pakai Python:\n\n```python\nfrom fastapi import FastAPI\nfrom opentelemetry import trace\nfrom opentelemetry.instrumentation.fastapi import FastAPIInstrumentor\nfrom opentelemetry.sdk.trace import TracerProvider\nfrom opentelemetry.sdk.trace.export import BatchSpanProcessor\nfrom opentelemetry.exporter.otlp.proto.grpc.trace_exporter import OTLPSpanExporter\n\n# 1. Setup Provider & Exporter ke OpenTelemetry Collector / Jaeger\nprovider = TracerProvider()\nprocessor = BatchSpanProcessor(OTLPSpanExporter(endpoint=\"localhost:4317\", insecure=True))\nprovider.add_span_processor(processor)\ntrace.set_tracer_provider(provider)\n\n# 2. Inisialisasi FastAPI\napp = FastAPI(title=\"Order Service\")\n\n# 3. Instrumentasi otomatis FastAPI\nFastAPIInstrumentor.instrument_app(app)\n\n@app.get(\"/checkout\")\nasync def checkout():\n    tracer = trace.get_tracer(__name__)\n    with tracer.start_as_current_span(\"process_payment_logic\") as span:\n        span.set_attribute(\"payment.method\", \"credit_card\")\n        # Logika pemrosesan pembayaran...\n        return {\"status\": \"success\", \"message\": \"Order processed\"}\n```\n\nDengan beberapa baris konfigurasi aja, setiap request HTTP ke *endpoint* `/checkout` bakal otomatis ngasilin span. *Status code* ke-*capture*, latensi kehitung, dan *context*-nya diteruskan ke *downstream service*. Nggak perlu ngoprek satu-satu, deh. 😎\n\n## Kapan Sistem Kalian Beneran Butuh Ini?\n\nKalau backend kalian masih monolit dan semua jalan di satu proses, *tracing* bisa jadi kelebihan beban. Tapi begitu jumlah service independen lewat dari dua, mulailah butuh. Apalagi kalau ada banyak *background worker* asinkron.\n\nBangun microservices tanpa distributed tracing itu kayak nyetir di jalan tol berkabut tebal tanpa lampu depan. Kita tahu mobilnya bergerak. Tapi kita nggak tahu **kapan bakal nabrak lubang**. 😅\n\nMulai aja dari instrumentasi *HTTP gateway* dulu. Sambungin ke [Jaeger](https://www.jaegertracing.io/) lokal lewat Docker. Nikmatin gimana akar masalah performa ketemu cuma dalam hitungan detik.\n\nSelamat ber-*observability* ria, dan semoga trace kalian selalu nyambung dari ujung ke ujung! 👋",[62],{"authors_id":63},{"name":64,"slug":65,"role":66,"profile_picture":58},"Inva","inva","Writer",{"id":68,"title":8,"slug":9,"articles":69,"parent_series":58},"9",[70,85,97,109,120,132,144,155,167,178,189,199,209,220,229,240,251,261,269,280,291,302,310,319,328,341,350,361,372,382,391,400,410],{"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",[51,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",[51,84,93,94,95,56,96],"rate-limiting","redis","api-gateway","traffict-management",{"id":98,"title":99,"slug":100,"excerpt":101,"thumbnail_image":102,"tags":104},"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":103},"798b60f1-9ef5-4f73-8d43-85825fd86acc",[105,106,107,108],"javascript","nodejs","express","typescript",{"id":110,"title":111,"slug":112,"excerpt":113,"thumbnail_image":114,"tags":116},"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":115},"9c05d0ae-e829-4f1b-b9f7-a84f3e0439d3",[117,118,119],"pemrograman","concurrency","tips-coding",{"id":121,"title":122,"slug":123,"excerpt":124,"thumbnail_image":125,"tags":127},"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":126},"f6620f79-b3b2-4f9c-8104-283a335e06c4",[128,129,51,55,130,131],"rabbitmq","message-broker","async","queue",{"id":133,"title":134,"slug":135,"excerpt":136,"thumbnail_image":137,"tags":139},"34","Kenapa Backend Butuh Database Connection Pooling?","kenapa-backend-butuh-database-connection-pooling","Pernah kena error Too many connections padahal CPU server masih santai di angka 30%? Masalahnya bukan di query kalian, tapi di cara aplikasi ngobrol sama database. Yuk, kenalan sama Connection Pooling!",{"id":138},"6f7a2d8c-2a37-4901-a522-50df8d9c0a20",[51,140,141,142,84,143],"database","postgresql","connection-pooling","performance",{"id":145,"title":146,"slug":147,"excerpt":148,"thumbnail_image":149,"tags":151},"27","Background Worker & Task Queue: Jangan Jalankan Proses Berat di Request HTTP!","background-worker-task-queue-jangan-jalankan-proses-berat-di-http","Pernah nggak sih kalian klik Daftar Akun lalu halaman loading muter sampai 15 detik tanpa kepastian? Penyebabnya klasik banget. Yuk, kita bahas kenapa proses berat nggak boleh dijalanin di request HTTP!",{"id":150},"e119c6ad-fc37-4b92-abdc-3eb20f8e34b4",[51,152,153,154,128,94,130],"task-queue","celery","fastapi",{"id":156,"title":157,"slug":158,"excerpt":159,"thumbnail_image":160,"tags":162},"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":161},"34b94e14-3e9a-4778-9f1f-6df5898915fb",[140,163,164,165,166,143,51],"sql","orm","sqlalchemy","django",{"id":168,"title":169,"slug":170,"excerpt":171,"thumbnail_image":172,"tags":174},"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":173},"a368631c-f331-4c50-8322-1d0fc44927aa",[175,176,51,118,177,84],"golang","go","goroutine",{"id":179,"title":180,"slug":181,"excerpt":182,"thumbnail_image":183,"tags":185},"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":184},"ae27713e-5025-4d13-88b6-efb4860cc5b3",[186,187,188],"linux","windows","foss",{"id":190,"title":191,"slug":192,"excerpt":193,"thumbnail_image":194,"tags":196},"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":195},"18df5262-d813-43d1-b1f7-5595a7f53602",[105,197,198],"web","news",{"id":200,"title":201,"slug":202,"excerpt":203,"thumbnail_image":204,"tags":206},"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":205},"c5a8262b-43db-4479-8f6c-5a6a0d61653b",[207,187,208],"shell","powershell",{"id":210,"title":211,"slug":212,"excerpt":213,"thumbnail_image":214,"tags":216},"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":215},"99b01cc2-11ac-4449-9927-a1a7116347df",[217,218,219],"howto","java","editor",{"id":221,"title":222,"slug":223,"excerpt":224,"thumbnail_image":225,"tags":227},"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":226},"b5352a4b-f274-4489-aca9-36814947d514",[186,228],"distro",{"id":230,"title":231,"slug":232,"excerpt":233,"thumbnail_image":234,"tags":236},"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":235},"ff111270-80c2-4ccb-83d7-d5ab8c021201",[237,238,239],"web-development","frontend","framework",{"id":241,"title":242,"slug":243,"excerpt":244,"thumbnail_image":245,"tags":247},"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":246},"98e85e76-9e7b-42d1-b989-7c75e7f49abc",[248,249,250],"programming","types","comparison",{"id":252,"title":253,"slug":254,"excerpt":255,"thumbnail_image":256,"tags":258},"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":257},"d5e879fa-5cd0-4015-a155-b0cc69ff12fb",[259,260,237],"tailwind-css","css-framework",{"id":262,"title":263,"slug":264,"excerpt":265,"thumbnail_image":266,"tags":268},"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":267},"f615bb1f-8e36-4d6c-9c2c-f1629407173c",[108,105,237],{"id":270,"title":271,"slug":272,"excerpt":273,"thumbnail_image":274,"tags":276},"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":275},"8444bdbc-f60c-4d8b-8593-1b49400e8659",[277,278,279],"nuxt-3","vue-3","frontend-framework",{"id":281,"title":282,"slug":283,"excerpt":284,"thumbnail_image":285,"tags":287},"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":286},"84847c9e-70ab-4dcc-bed7-7be50165f7f4",[154,288,51,289,290],"python","asgi","pydantic",{"id":292,"title":293,"slug":294,"excerpt":295,"thumbnail_image":296,"tags":298},"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":297},"487500a0-9e09-469d-8736-1583c5ea83aa",[51,299,300,55,301,84],"grpc","rest-api","protobuf",{"id":303,"title":304,"slug":305,"excerpt":306,"thumbnail_image":307,"tags":309},"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":308},"21ab769d-6f82-4a22-be11-17ac16e9fb6b",[51,140,118,141,84,56,163],{"id":311,"title":312,"slug":313,"excerpt":314,"thumbnail_image":315,"tags":317},"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":316},"1401f9e5-6359-404a-8d80-273ddee9a372",[51,93,84,318,94,154],"api",{"id":320,"title":321,"slug":322,"excerpt":323,"thumbnail_image":324,"tags":326},"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":325},"d9e76018-fbcc-4c69-ad42-8f75ff229ecd",[51,84,327,129,56],"event-queue",{"id":329,"title":330,"slug":331,"excerpt":332,"thumbnail_image":333,"tags":335},"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":334},"1942a5c9-c1f6-476d-9913-768f78d9d8eb",[336,337,338,339,340],"system-programming","rust","zig","c","memory-safety",{"id":342,"title":343,"slug":344,"excerpt":345,"thumbnail_image":346,"tags":348},"29","Memahami Database Indexing: Rahasia Query Super Cepat","memahami-database-indexing-rahasia-query-super-cepat","Query kalian mulai lelet padahal data baru nembus jutaan baris? Sebelum buru-buru *upgrade* server, yuk cek dulu *index*-nya. Yuk, kita bedah gimana *database indexing* sebenernya kerja!",{"id":347},"b123036f-1779-478c-a545-cf5f189b5fe9",[140,163,141,349,143,51],"indexing",{"id":351,"title":352,"slug":353,"excerpt":354,"thumbnail_image":355,"tags":357},"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":356},"9595b7d7-60e0-48f5-a715-f3cf60f34e1d",[94,51,358,359,360,288],"cache","nosql","in-memory",{"id":362,"title":363,"slug":364,"excerpt":365,"thumbnail_image":366,"tags":368},"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":367},"f4c08f1b-e0d0-410c-b091-c3618944fb3e",[369,370,83,371,51],"docker","docker-compose","containers",{"id":373,"title":374,"slug":375,"excerpt":376,"thumbnail_image":377,"tags":379},"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":378},"724cb83a-3ce5-4ee2-b0d7-533e3a0fc7df",[51,318,380,84,381,154,94],"idempotency","payment",{"id":383,"title":384,"slug":385,"excerpt":386,"thumbnail_image":387,"tags":389},"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":388},"c2e8e37f-8f9a-423f-a09d-74613b3c2924",[51,55,390,84,56],"circuit-breaker",{"id":392,"title":393,"slug":394,"excerpt":395,"thumbnail_image":396,"tags":398},"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":397},"251a54a7-1d24-47fd-8cbc-a46fd42cbb6f",[51,83,154,369,399,84,56],"kubernetes",{"id":401,"title":402,"slug":403,"excerpt":404,"thumbnail_image":405,"tags":407},"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":406},"08ef5fe5-d935-47b3-bbbc-d976948b2a9e",[51,140,141,84,56,408,409],"sharding","scaling",{"id":43,"title":44,"slug":45,"excerpt":46,"thumbnail_image":411,"tags":412},{"id":49},[51,52,53,54,55,56,57],"\u003Cp>Waktu \u003Cem>backend\u003C/em> kalian masih monolit sederhana, urusan \u003Cem>debugging\u003C/em> terasa damai banget. Ada \u003Cem>request\u003C/em> lambat? Tinggal intip \u003Cem>log\u003C/em> server. Atau pasang \u003Cem>profiler\u003C/em> lokal. Semuanya jalan di satu proses, satu memori, dan satu \u003Cem>log file\u003C/em> yang teratur.\u003C/p>\n\u003Cp>Begitu arsitektur dipecah jadi belasan \u003Cem>microservice\u003C/em>, kondisinya berubah drastis, lho. Ada Auth Service. Ada Order Service. Ada Payment Gateway. Sampai Notification Service dan Inventory Service. Satu klik tombol "Checkout" bisa memicu puluhan \u003Cem>network call\u003C/em> asinkron antar-\u003Cem>service\u003C/em>.\u003C/p>\n\u003Cp>Nah, pas pengguna ngeluh \u003Cem>checkout\u003C/em>-nya makan 8 detik lalu \u003Cem>timeout\u003C/em> 500, gimana kita tahu service mana yang bikin lambat? Query \u003Cem>database\u003C/em> di Inventory Service-nya? Atau ada antrean di \u003Cem>payment worker\u003C/em>? 🤔\u003C/p>\n\u003Cp>Di sinilah \u003Cem>Distributed Tracing\u003C/em> \u003Cstrong>hadir jadi penyelamat\u003C/strong>.\u003C/p>\n\u003Ch2 id=\"kenapa-centralized-logging-aja-nggak-cukup\">Kenapa Centralized Logging Aja Nggak Cukup?\u003C/h2>\n\u003Cp>Banyak \u003Cem>developer\u003C/em> ngira cukup pasang \u003Cem>centralized log aggregator\u003C/em>. Kayak Elasticsearch, Loki, atau Datadog. Padahal itu \u003Cstrong>belum cukup\u003C/strong> buat beresin masalah di \u003Cem>microservices\u003C/em>.\u003C/p>\n\u003Cp>Saat ratusan ribu request masuk per detik, log dari berbagai service bercampur jadi lautan teks raksasa. Nyari keterkaitan antara log di Service A sama log di Service D jadi mimpi buruk. Soalnya nggak ada benang merah yang ngikatnya.\u003C/p>\n\u003Cp>\u003Cem>Centralized logging\u003C/em> ngasih tahu kita apa yang terjadi di dalam satu service. Distributed tracing ngasih tahu kita gimana request mengalir melintasi seluruh ekosistem. Itu dua hal yang \u003Cstrong>beda banget\u003C/strong>.\u003C/p>\n\u003Ch2 id=\"anatomi-distributed-tracing-trace-vs-span\">Anatomi Distributed Tracing: Trace vs Span\u003C/h2>\n\u003Cp>Buat paham distributed tracing, ada dua konsep fundamental yang wajib kita kuasai.\u003C/p>\n\u003Cp>\u003Cem>Trace\u003C/em> itu seluruh perjalanan sebuah transaksi atau request, dari awal sampai akhir. Bayangin trace kayak satu tiket perjalanan penumpang. Dari stasiun keberangkatan sampai tiba di tujuan akhir. Tiap trace punya ID unik global namanya \u003Ccode>Trace ID\u003C/code>.\u003C/p>\n\u003Cp>\u003Cem>Span\u003C/em> adalah segmen atau unit kerja tunggal di dalam sebuah trace, nih. Satu trace terdiri dari satu atau banyak span. Semuanya membentuk struktur pohon (\u003Cem>directed acyclic graph\u003C/em>). Tiap span nyatet:\u003C/p>\n\u003Cul>\n\u003Cli>Nama operasi (misalnya \u003Ccode>POST /orders\u003C/code>, \u003Ccode>SELECT * FROM users\u003C/code>, atau \u003Ccode>Publish to RabbitMQ\u003C/code>)\u003C/li>\n\u003Cli>Waktu mulai dan durasi eksekusi\u003C/li>\n\u003Cli>Metadata tambahan berupa \u003Cem>tags\u003C/em>/\u003Cem>attributes\u003C/em> (misalnya \u003Ccode>http.status_code: 200\u003C/code>, \u003Ccode>db.system: postgresql\u003C/code>, \u003Ccode>user.id: 1042\u003C/code>)\u003C/li>\n\u003Cli>Log peristiwa (\u003Cem>events\u003C/em>/\u003Cem>logs\u003C/em>) plus status \u003Cem>error\u003C/em>\u003C/li>\n\u003C/ul>\n\u003Cp>Dengan visualisasi span, kita bisa lihat service mana yang paling lama. Itulah si \u003Cem>critical path\u003C/em>. Kita juga langsung tahu di titik mana error pertama meledak.\u003C/p>\n\u003Ch2 id=\"cara-kerja-context-propagation\">Cara Kerja Context Propagation\u003C/h2>\n\u003Cp>Pertanyaan terbesarnya: gimana Service B tahu request yang dia terima itu kelanjutan dari Service A?\u003C/p>\n\u003Cp>Jawabannya \u003Cem>context propagation\u003C/em>. Pas Service A manggil Service B lewat HTTP, Service A nyisipin \u003Cem>Trace ID\u003C/em> dan \u003Cem>Parent Span ID\u003C/em> ke dalam \u003Cem>header request\u003C/em>. Begitu juga kalau lewat \u003Cem>message queue\u003C/em>.\u003C/p>\n\u003Cp>Standar industri modern yang paling banyak dipakai sekarang adalah \u003Cem>W3C Trace Context\u003C/em>. \u003Cem>Header\u003C/em> yang dikirim bentuknya \u003Ccode>traceparent\u003C/code>:\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\">HTTP\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=\"traceparent%3A%2000-4bf92f3577b34da6a3ce929d0e0e4736-00f067aa0ba902b7-01\" 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\">\u003Ccode>traceparent: 00-4bf92f3577b34da6a3ce929d0e0e4736-00f067aa0ba902b7-01\u003C/code>\u003C/pre>\n  \u003C/div>\n\u003C/div>\u003Cp>Header ini terdiri dari 4 bagian:\u003C/p>\n\u003Col>\n\u003Cli>\u003Ccode>version\u003C/code>: versi spesifikasi W3C (saat ini \u003Ccode>00\u003C/code>).\u003C/li>\n\u003Cli>\u003Ccode>trace-id\u003C/code>: ID unik 16-byte buat keseluruhan trace (\u003Ccode>4bf92f3577b34da6a3ce929d0e0e4736\u003C/code>).\u003C/li>\n\u003Cli>\u003Ccode>parent-id\u003C/code> / \u003Ccode>span-id\u003C/code>: ID unik 8-byte buat span pemanggil (\u003Ccode>00f067aa0ba902b7\u003C/code>).\u003C/li>\n\u003Cli>\u003Ccode>trace-flags\u003C/code>: opsi \u003Cem>flag\u003C/em>. Nilai \u003Ccode>01\u003C/code> nandain span ini direkam atau \u003Cem>sampled\u003C/em>.\u003C/li>\n\u003C/ol>\n\u003Cp>Begitu Service B nerima request, \u003Cem>library tracing\u003C/em>-nya baca header itu. Dia ngekstrak Trace ID, lalu bikin \u003Cem>child span\u003C/em> baru di bawah \u003Cem>Parent ID\u003C/em> yang sesuai. Rantainya pun nyambung terus.\u003C/p>\n\u003Ch2 id=\"implementasi-modern-dengan-opentelemetry\">Implementasi Modern dengan OpenTelemetry\u003C/h2>\n\u003Cp>Dulu kita mungkin bingung milih. Ada OpenTracing, OpenCensus, \u003Cem>Jaeger client\u003C/em>, sampai \u003Cem>Zipkin client\u003C/em>. Untungnya industri udah sepakat pada satu standar terbuka. Namanya \u003Ca href=\"https://opentelemetry.io/\">OpenTelemetry\u003C/a> (OTel). Proyek \u003Cem>open source\u003C/em> ini di bawah naungan Cloud Native Computing Foundation (CNCF).\u003C/p>\n\u003Cp>OpenTelemetry nyediain SDK buat berbagai bahasa. Ada Python, Go, Node.js, dan Java. Ada juga \u003Cem>Collector\u003C/em> terpusat buat memproses dan neruskan data \u003Cem>telemetry\u003C/em>. Data itu lalu dikirim ke backend visualisasi kayak Jaeger, \u003Cem>Grafana Tempo\u003C/em>, atau Datadog.\u003C/p>\n\u003Cp>Contoh sederhana instrumentasi otomatis di FastAPI pakai Python:\u003C/p>\n\n\u003Cdiv class=\"code-block-wrapper my-6 not-prose rounded-xl border-2 border-black dark:border-gray-600 shadow-neo overflow-hidden bg-[#24292e] text-[#e1e4e8] transition-all\">\n  \u003Cdiv class=\"code-block-header flex items-center justify-between px-4 py-2.5 bg-[#1f2428] border-b-2 border-black dark:border-gray-600 font-mono text-xs font-bold text-gray-300 select-none\">\n    \u003Cdiv class=\"flex items-center gap-2\">\n      \u003Cspan class=\"w-3 h-3 rounded-full bg-[#ff5f56] border border-black/40 inline-block\">\u003C/span>\n      \u003Cspan class=\"w-3 h-3 rounded-full bg-[#ffbd2e] border border-black/40 inline-block\">\u003C/span>\n      \u003Cspan class=\"w-3 h-3 rounded-full bg-[#27c93f] border border-black/40 inline-block\">\u003C/span>\n      \u003Cspan class=\"ml-2 font-mono font-bold text-xs uppercase tracking-wider text-gray-300\">PYTHON\u003C/span>\n    \u003C/div>\n    \u003Cbutton type=\"button\" class=\"copy-code-btn flex items-center gap-1.5 px-3 py-1 text-xs font-bold bg-[#2f363d] text-gray-200 border-2 border-black dark:border-gray-500 rounded-lg shadow-neo-sm hover:translate-x-0.5 hover:translate-y-0.5 hover:shadow-none hover:bg-gray-700 transition-all cursor-pointer\" data-code=\"from%20fastapi%20import%20FastAPI%0Afrom%20opentelemetry%20import%20trace%0Afrom%20opentelemetry.instrumentation.fastapi%20import%20FastAPIInstrumentor%0Afrom%20opentelemetry.sdk.trace%20import%20TracerProvider%0Afrom%20opentelemetry.sdk.trace.export%20import%20BatchSpanProcessor%0Afrom%20opentelemetry.exporter.otlp.proto.grpc.trace_exporter%20import%20OTLPSpanExporter%0A%0A%23%201.%20Setup%20Provider%20%26%20Exporter%20ke%20OpenTelemetry%20Collector%20%2F%20Jaeger%0Aprovider%20%3D%20TracerProvider()%0Aprocessor%20%3D%20BatchSpanProcessor(OTLPSpanExporter(endpoint%3D%22localhost%3A4317%22%2C%20insecure%3DTrue))%0Aprovider.add_span_processor(processor)%0Atrace.set_tracer_provider(provider)%0A%0A%23%202.%20Inisialisasi%20FastAPI%0Aapp%20%3D%20FastAPI(title%3D%22Order%20Service%22)%0A%0A%23%203.%20Instrumentasi%20otomatis%20FastAPI%0AFastAPIInstrumentor.instrument_app(app)%0A%0A%40app.get(%22%2Fcheckout%22)%0Aasync%20def%20checkout()%3A%0A%20%20%20%20tracer%20%3D%20trace.get_tracer(__name__)%0A%20%20%20%20with%20tracer.start_as_current_span(%22process_payment_logic%22)%20as%20span%3A%0A%20%20%20%20%20%20%20%20span.set_attribute(%22payment.method%22%2C%20%22credit_card%22)%0A%20%20%20%20%20%20%20%20%23%20Logika%20pemrosesan%20pembayaran...%0A%20%20%20%20%20%20%20%20return%20%7B%22status%22%3A%20%22success%22%2C%20%22message%22%3A%20%22Order%20processed%22%7D\" title=\"Salin kode\">\n      \u003Csvg class=\"w-3.5 h-3.5 copy-icon-svg\" fill=\"none\" stroke=\"currentColor\" viewBox=\"0 0 24 24\">\n        \u003Cpath stroke-linecap=\"round\" stroke-linejoin=\"round\" stroke-width=\"2\" d=\"M8 16H6a2 2 0 01-2-2V6a2 2 0 012-2h8a2 2 0 012 2v2m-6 12h8a2 2 0 002-2v-8a2 2 0 00-2-2h-8a2 2 0 00-2 2v8a2 2 0 002 2z\">\u003C/path>\n      \u003C/svg>\n      \u003Cspan class=\"copy-text\">Copy\u003C/span>\n    \u003C/button>\n  \u003C/div>\n  \u003Cdiv class=\"code-block-content p-4 overflow-x-auto text-sm font-mono leading-relaxed bg-[#24292e]\">\n    \u003Cpre class=\"shiki github-dark\" style=\"background-color:#24292e;color:#e1e4e8\" tabindex=\"0\">\u003Ccode>\u003Cspan class=\"line\">\u003Cspan style=\"color:#F97583\">from\u003C/span>\u003Cspan style=\"color:#E1E4E8\"> fastapi \u003C/span>\u003Cspan style=\"color:#F97583\">import\u003C/span>\u003Cspan style=\"color:#E1E4E8\"> FastAPI\u003C/span>\u003C/span>\n\u003Cspan class=\"line\">\u003Cspan style=\"color:#F97583\">from\u003C/span>\u003Cspan style=\"color:#E1E4E8\"> opentelemetry \u003C/span>\u003Cspan style=\"color:#F97583\">import\u003C/span>\u003Cspan style=\"color:#E1E4E8\"> trace\u003C/span>\u003C/span>\n\u003Cspan class=\"line\">\u003Cspan style=\"color:#F97583\">from\u003C/span>\u003Cspan style=\"color:#E1E4E8\"> opentelemetry.instrumentation.fastapi \u003C/span>\u003Cspan style=\"color:#F97583\">import\u003C/span>\u003Cspan style=\"color:#E1E4E8\"> FastAPIInstrumentor\u003C/span>\u003C/span>\n\u003Cspan class=\"line\">\u003Cspan style=\"color:#F97583\">from\u003C/span>\u003Cspan style=\"color:#E1E4E8\"> opentelemetry.sdk.trace \u003C/span>\u003Cspan style=\"color:#F97583\">import\u003C/span>\u003Cspan style=\"color:#E1E4E8\"> TracerProvider\u003C/span>\u003C/span>\n\u003Cspan class=\"line\">\u003Cspan style=\"color:#F97583\">from\u003C/span>\u003Cspan style=\"color:#E1E4E8\"> opentelemetry.sdk.trace.export \u003C/span>\u003Cspan style=\"color:#F97583\">import\u003C/span>\u003Cspan style=\"color:#E1E4E8\"> BatchSpanProcessor\u003C/span>\u003C/span>\n\u003Cspan class=\"line\">\u003Cspan style=\"color:#F97583\">from\u003C/span>\u003Cspan style=\"color:#E1E4E8\"> opentelemetry.exporter.otlp.proto.grpc.trace_exporter \u003C/span>\u003Cspan style=\"color:#F97583\">import\u003C/span>\u003Cspan style=\"color:#E1E4E8\"> OTLPSpanExporter\u003C/span>\u003C/span>\n\u003Cspan class=\"line\">\u003C/span>\n\u003Cspan class=\"line\">\u003Cspan style=\"color:#6A737D\"># 1. Setup Provider & Exporter ke OpenTelemetry Collector / Jaeger\u003C/span>\u003C/span>\n\u003Cspan class=\"line\">\u003Cspan style=\"color:#E1E4E8\">provider \u003C/span>\u003Cspan style=\"color:#F97583\">=\u003C/span>\u003Cspan style=\"color:#E1E4E8\"> TracerProvider()\u003C/span>\u003C/span>\n\u003Cspan class=\"line\">\u003Cspan style=\"color:#E1E4E8\">processor \u003C/span>\u003Cspan style=\"color:#F97583\">=\u003C/span>\u003Cspan style=\"color:#E1E4E8\"> BatchSpanProcessor(OTLPSpanExporter(\u003C/span>\u003Cspan style=\"color:#FFAB70\">endpoint\u003C/span>\u003Cspan style=\"color:#F97583\">=\u003C/span>\u003Cspan style=\"color:#9ECBFF\">\"localhost:4317\"\u003C/span>\u003Cspan style=\"color:#E1E4E8\">, \u003C/span>\u003Cspan style=\"color:#FFAB70\">insecure\u003C/span>\u003Cspan style=\"color:#F97583\">=\u003C/span>\u003Cspan style=\"color:#79B8FF\">True\u003C/span>\u003Cspan style=\"color:#E1E4E8\">))\u003C/span>\u003C/span>\n\u003Cspan class=\"line\">\u003Cspan style=\"color:#E1E4E8\">provider.add_span_processor(processor)\u003C/span>\u003C/span>\n\u003Cspan class=\"line\">\u003Cspan style=\"color:#E1E4E8\">trace.set_tracer_provider(provider)\u003C/span>\u003C/span>\n\u003Cspan class=\"line\">\u003C/span>\n\u003Cspan class=\"line\">\u003Cspan style=\"color:#6A737D\"># 2. Inisialisasi FastAPI\u003C/span>\u003C/span>\n\u003Cspan class=\"line\">\u003Cspan style=\"color:#E1E4E8\">app \u003C/span>\u003Cspan style=\"color:#F97583\">=\u003C/span>\u003Cspan style=\"color:#E1E4E8\"> FastAPI(\u003C/span>\u003Cspan style=\"color:#FFAB70\">title\u003C/span>\u003Cspan style=\"color:#F97583\">=\u003C/span>\u003Cspan style=\"color:#9ECBFF\">\"Order Service\"\u003C/span>\u003Cspan style=\"color:#E1E4E8\">)\u003C/span>\u003C/span>\n\u003Cspan class=\"line\">\u003C/span>\n\u003Cspan class=\"line\">\u003Cspan style=\"color:#6A737D\"># 3. Instrumentasi otomatis FastAPI\u003C/span>\u003C/span>\n\u003Cspan class=\"line\">\u003Cspan style=\"color:#E1E4E8\">FastAPIInstrumentor.instrument_app(app)\u003C/span>\u003C/span>\n\u003Cspan class=\"line\">\u003C/span>\n\u003Cspan class=\"line\">\u003Cspan style=\"color:#B392F0\">@app.get\u003C/span>\u003Cspan style=\"color:#E1E4E8\">(\u003C/span>\u003Cspan style=\"color:#9ECBFF\">\"/checkout\"\u003C/span>\u003Cspan style=\"color:#E1E4E8\">)\u003C/span>\u003C/span>\n\u003Cspan class=\"line\">\u003Cspan style=\"color:#F97583\">async\u003C/span>\u003Cspan style=\"color:#F97583\"> def\u003C/span>\u003Cspan style=\"color:#B392F0\"> checkout\u003C/span>\u003Cspan style=\"color:#E1E4E8\">():\u003C/span>\u003C/span>\n\u003Cspan class=\"line\">\u003Cspan style=\"color:#E1E4E8\">    tracer \u003C/span>\u003Cspan style=\"color:#F97583\">=\u003C/span>\u003Cspan style=\"color:#E1E4E8\"> trace.get_tracer(\u003C/span>\u003Cspan style=\"color:#79B8FF\">__name__\u003C/span>\u003Cspan style=\"color:#E1E4E8\">)\u003C/span>\u003C/span>\n\u003Cspan class=\"line\">\u003Cspan style=\"color:#F97583\">    with\u003C/span>\u003Cspan style=\"color:#E1E4E8\"> tracer.start_as_current_span(\u003C/span>\u003Cspan style=\"color:#9ECBFF\">\"process_payment_logic\"\u003C/span>\u003Cspan style=\"color:#E1E4E8\">) \u003C/span>\u003Cspan style=\"color:#F97583\">as\u003C/span>\u003Cspan style=\"color:#E1E4E8\"> span:\u003C/span>\u003C/span>\n\u003Cspan class=\"line\">\u003Cspan style=\"color:#E1E4E8\">        span.set_attribute(\u003C/span>\u003Cspan style=\"color:#9ECBFF\">\"payment.method\"\u003C/span>\u003Cspan style=\"color:#E1E4E8\">, \u003C/span>\u003Cspan style=\"color:#9ECBFF\">\"credit_card\"\u003C/span>\u003Cspan style=\"color:#E1E4E8\">)\u003C/span>\u003C/span>\n\u003Cspan class=\"line\">\u003Cspan style=\"color:#6A737D\">        # Logika pemrosesan pembayaran...\u003C/span>\u003C/span>\n\u003Cspan class=\"line\">\u003Cspan style=\"color:#F97583\">        return\u003C/span>\u003Cspan style=\"color:#E1E4E8\"> {\u003C/span>\u003Cspan style=\"color:#9ECBFF\">\"status\"\u003C/span>\u003Cspan style=\"color:#E1E4E8\">: \u003C/span>\u003Cspan style=\"color:#9ECBFF\">\"success\"\u003C/span>\u003Cspan style=\"color:#E1E4E8\">, \u003C/span>\u003Cspan style=\"color:#9ECBFF\">\"message\"\u003C/span>\u003Cspan style=\"color:#E1E4E8\">: \u003C/span>\u003Cspan style=\"color:#9ECBFF\">\"Order processed\"\u003C/span>\u003Cspan style=\"color:#E1E4E8\">}\u003C/span>\u003C/span>\u003C/code>\u003C/pre>\n  \u003C/div>\n\u003C/div>\u003Cp>Dengan beberapa baris konfigurasi aja, setiap request HTTP ke \u003Cem>endpoint\u003C/em> \u003Ccode>/checkout\u003C/code> bakal otomatis ngasilin span. \u003Cem>Status code\u003C/em> ke-\u003Cem>capture\u003C/em>, latensi kehitung, dan \u003Cem>context\u003C/em>-nya diteruskan ke \u003Cem>downstream service\u003C/em>. Nggak perlu ngoprek satu-satu, deh. 😎\u003C/p>\n\u003Ch2 id=\"kapan-sistem-kalian-beneran-butuh-ini\">Kapan Sistem Kalian Beneran Butuh Ini?\u003C/h2>\n\u003Cp>Kalau backend kalian masih monolit dan semua jalan di satu proses, \u003Cem>tracing\u003C/em> bisa jadi kelebihan beban. Tapi begitu jumlah service independen lewat dari dua, mulailah butuh. Apalagi kalau ada banyak \u003Cem>background worker\u003C/em> asinkron.\u003C/p>\n\u003Cp>Bangun microservices tanpa distributed tracing itu kayak nyetir di jalan tol berkabut tebal tanpa lampu depan. Kita tahu mobilnya bergerak. Tapi kita nggak tahu \u003Cstrong>kapan bakal nabrak lubang\u003C/strong>. 😅\u003C/p>\n\u003Cp>Mulai aja dari instrumentasi \u003Cem>HTTP gateway\u003C/em> dulu. Sambungin ke \u003Ca href=\"https://www.jaegertracing.io/\">Jaeger\u003C/a> lokal lewat Docker. Nikmatin gimana akar masalah performa ketemu cuma dalam hitungan detik.\u003C/p>\n\u003Cp>Selamat ber-\u003Cem>observability\u003C/em> ria, dan semoga trace kalian selalu nyambung dari ujung ke ujung! 👋\u003C/p>\n","\u003Cul>\n\u003Cli>Distributed Tracing jadi kunci buat memetakan alur request lintas service, sesuatu yang centralized logging tradisional nggak bisa pecahin sendiri.\u003C/li>\n\u003Cli>Struktur dasarnya cuma dua: \u003Cem>trace\u003C/em> yang mewakili seluruh perjalanan request, dan \u003Cem>span\u003C/em> yang mencatat unit kerja spesifik di tiap service atau database.\u003C/li>\n\u003Cli>Context propagation lewat \u003Cem>trace context\u003C/em> W3C—\u003Cem>header\u003C/em> \u003Ccode>traceparent\u003C/code>—bikin correlation ID tetap nyambung antar-layanan.\u003C/li>\n\u003Cli>OpenTelemetry jadi standar vendor-agnostic buat instrumentasi backend, gampang disambungin ke visualizer kayak Jaeger atau Grafana Tempo.\u003C/li>\n\u003C/ul>\n",[416,419,422,430],{"id":329,"title":330,"slug":331,"excerpt":332,"thumbnail_image":417,"tags":418},{"id":334},[336,337,338,339,340],{"id":86,"title":87,"slug":88,"excerpt":89,"thumbnail_image":420,"tags":421},{"id":91},[51,84,93,94,95,56,96],{"id":423,"title":424,"slug":425,"excerpt":426,"thumbnail_image":427,"tags":429},"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":428},"e3c617fd-1486-4b82-b937-94fbec846c77",[51,55,56,140,129,84,141],{"id":431,"title":432,"slug":433,"excerpt":434,"thumbnail_image":435,"tags":437},"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":436},"6c0a7ead-4841-4073-b29e-df7ae0f2aa3c",[128,129,51,56,55,130,288],[439,443,446,449,452],{"text":440,"depth":441,"id":442},"Kenapa Centralized Logging Aja Nggak Cukup?",2,"kenapa-centralized-logging-aja-nggak-cukup",{"text":444,"depth":441,"id":445},"Anatomi Distributed Tracing: Trace vs Span","anatomi-distributed-tracing-trace-vs-span",{"text":447,"depth":441,"id":448},"Cara Kerja Context Propagation","cara-kerja-context-propagation",{"text":450,"depth":441,"id":451},"Implementasi Modern dengan OpenTelemetry","implementasi-modern-dengan-opentelemetry",{"text":453,"depth":441,"id":454},"Kapan Sistem Kalian Beneran Butuh Ini?","kapan-sistem-kalian-beneran-butuh-ini",1791045071507]