Node.js uygulamalar\u0131n\u0131zda b\u00fcy\u00fck veri k\u00fcmeleriyle \u00e7al\u0131\u015f\u0131rken performans sorunlar\u0131 m\u0131 ya\u015f\u0131yorsunuz? Bellek t\u00fcketimini optimize etmek ve G\/\u00c7 (Input\/Output) i\u015flemlerini daha verimli hale getirmek i\u00e7in Stream ve Buffer kavramlar\u0131 kritik \u00f6neme sahiptir. Bu makale, Node.js’in bu g\u00fc\u00e7l\u00fc ara\u00e7lar\u0131n\u0131 temelden ileri seviyeye kadar ke\u015ffederek, uygulamalar\u0131n\u0131zda veri ak\u0131\u015f\u0131n\u0131 nas\u0131l ustal\u0131kla y\u00f6netece\u011finizi ad\u0131m ad\u0131m a\u00e7\u0131klayacakt\u0131r.<\/p>\n
Modern web uygulamalar\u0131, g\u00fcn\u00fcm\u00fczde giderek artan miktarda veriyle ba\u015fa \u00e7\u0131kmak zorunda kal\u0131yor. B\u00fcy\u00fck dosyalar\u0131 indirme, y\u00fckleme, i\u015fleme veya ger\u00e7ek zamanl\u0131 veri ak\u0131\u015flar\u0131n\u0131 y\u00f6netme gibi senaryolar, geleneksel y\u00f6ntemlerle ele al\u0131nd\u0131\u011f\u0131nda ciddi performans darbo\u011fazlar\u0131na yol a\u00e7abilir. \u00d6rne\u011fin, birka\u00e7 gigabaytl\u0131k bir dosyay\u0131 diske tamamen okuyup ard\u0131ndan i\u015flemek, uygulaman\u0131z\u0131n belle\u011fini h\u0131zla t\u00fcketebilir ve \u00e7\u00f6kmesine neden olabilir. Peki, bu t\u00fcr zorluklar\u0131n \u00fcstesinden gelmek ve Node.js uygulamalar\u0131n\u0131z\u0131n hem h\u0131zl\u0131 hem de bellek dostu olmas\u0131n\u0131 sa\u011flamak m\u00fcmk\u00fcn m\u00fc? \u0130\u015fte bu noktada Node.js Stream ve Buffer mekanizmalar\u0131 devreye girer. Bu iki temel bile\u015fen, \u00f6zellikle b\u00fcy\u00fck veri k\u00fcmeleriyle \u00e7al\u0131\u015f\u0131rken, veriyi k\u00fc\u00e7\u00fck par\u00e7alar halinde i\u015fleyerek bellek kullan\u0131m\u0131n\u0131 minimize etmenizi ve sistem kaynaklar\u0131n\u0131 daha verimli kullanman\u0131z\u0131 sa\u011flar. Bu b\u00f6l\u00fcmde, neden bu kavramlara ihtiya\u00e7 duydu\u011fumuzu ve uygulamalar\u0131n\u0131zda kar\u015f\u0131la\u015ft\u0131\u011f\u0131n\u0131z performans sorunlar\u0131n\u0131 nas\u0131l \u00e7\u00f6zeceklerini detayl\u0131ca inceleyece\u011fiz. Geleneksel yakla\u015f\u0131mlar\u0131n s\u0131n\u0131rl\u0131l\u0131klar\u0131n\u0131 anlayarak, Stream ve Buffer’\u0131n sundu\u011fu avantajlar\u0131n fark\u0131na varacak ve bu g\u00fc\u00e7l\u00fc ara\u00e7lar\u0131n potansiyelini ke\u015ffetmeye ba\u015flayaca\u011f\u0131z. \u00d6zellikle I\/O yo\u011fun uygulamalarda, asenkron yap\u0131s\u0131yla \u00f6ne \u00e7\u0131kan Node.js’in bu mekanizmalar\u0131 sayesinde, uygulaman\u0131z\u0131n yan\u0131t s\u00fcrelerini \u00f6nemli \u00f6l\u00e7\u00fcde iyile\u015ftirebilirsiniz. Bu, sadece kullan\u0131c\u0131 deneyimini art\u0131rmakla kalmaz, ayn\u0131 zamanda sunucu maliyetlerinizi d\u00fc\u015f\u00fcrmenize de yard\u0131mc\u0131 olur. Unutmay\u0131n, verimli veri i\u015fleme, \u00f6l\u00e7eklenebilir ve sa\u011flam Node.js uygulamalar\u0131n\u0131n temel ta\u015f\u0131d\u0131r.<\/p>\n
Veri ak\u0131\u015f\u0131 y\u00f6netimi, \u00f6zellikle dosya sunucular\u0131, ger\u00e7ek zamanl\u0131 analiz sistemleri veya API a\u011f ge\u00e7itleri gibi y\u00fcksek trafikli uygulamalar i\u00e7in vazge\u00e7ilmezdir. E\u011fer t\u00fcm veriyi belle\u011fe y\u00fckleyip \u00f6yle i\u015flemeye kalk\u0131\u015f\u0131rsan\u0131z, uygulaman\u0131z h\u0131zla kilitlenebilir veya hizmet d\u0131\u015f\u0131 kalabilir. Bu durum, \u00f6zellikle k\u0131s\u0131tl\u0131 sunucu kaynaklar\u0131na sahip ortamlarda b\u00fcy\u00fck bir risk te\u015fkil eder. Node.js Stream ve Buffer, bu riski ortadan kald\u0131rarak, verinin “par\u00e7a par\u00e7a” i\u015flenmesini sa\u011flar. \u00d6rne\u011fin, bir kullan\u0131c\u0131n\u0131n b\u00fcy\u00fck bir video dosyas\u0131n\u0131 y\u00fckledi\u011fini d\u00fc\u015f\u00fcnelim. Bu dosyay\u0131 tamamen belle\u011fe almak yerine, Stream’ler sayesinde dosyan\u0131n ilk k\u0131sm\u0131n\u0131 al\u0131r, i\u015fler ve disk yazmaya ba\u015flarken, ayn\u0131 anda dosyan\u0131n di\u011fer k\u0131s\u0131mlar\u0131n\u0131 okumaya devam edersiniz. Bu paralel ve e\u015fzamanl\u0131 \u00e7al\u0131\u015fma, uygulaman\u0131z\u0131n kesintisiz bir \u015fekilde hizmet vermesini sa\u011flar. Ayr\u0131ca, Stream’ler aras\u0131nda veri “pipe” etme yetene\u011fi, karma\u015f\u0131k veri i\u015fleme boru hatlar\u0131 olu\u015fturman\u0131z\u0131 kolayla\u015ft\u0131r\u0131r. Veriyi bir kaynaktan okuyup (Readable Stream), \u00fczerinde bir d\u00f6n\u00fc\u015f\u00fcm uygulay\u0131p (Transform Stream) ve son olarak bir hedefe yazma (Writable Stream) i\u015flemleri tek bir ak\u0131\u015fta sorunsuz bir \u015fekilde ger\u00e7ekle\u015ftirilebilir. Bu esneklik, geli\u015ftiricilere g\u00fc\u00e7l\u00fc ve mod\u00fcler \u00e7\u00f6z\u00fcmler olu\u015fturma imkan\u0131 tan\u0131r. K\u0131sacas\u0131, Node.js Stream ve Buffer, modern veri i\u015fleme ihtiya\u00e7lar\u0131 i\u00e7in olmazsa olmaz ara\u00e7lard\u0131r.<\/p>\n
Node.js ortam\u0131nda JavaScript’in strings ve numbers gibi tan\u0131d\u0131k veri t\u00fcrleri, \u00e7o\u011fu senaryo i\u00e7in yeterli olsa da, ikili (binary) veriyle do\u011frudan \u00e7al\u0131\u015fman\u0131z gerekti\u011finde yetersiz kal\u0131rlar. A\u011f protokolleri, dosya sistemleri, \u015fifreleme algoritmalar\u0131 veya s\u0131k\u0131\u015ft\u0131rma i\u015flemleri gibi d\u00fc\u015f\u00fck seviyeli i\u015flemler genellikle salt ikili veriye do\u011frudan eri\u015fim gerektirir. \u0130\u015fte tam bu noktada Node.js Buffer s\u0131n\u0131f\u0131 devreye girer. Buffer, ham ikili veriyi do\u011frudan ele almak i\u00e7in tasarlanm\u0131\u015f global bir objedir ve bellekte sabit boyutlu bir yer kaplar. ECMAScript standartlar\u0131n\u0131n bir par\u00e7as\u0131 olmayan Buffer, Node.js’in V8 motorunun C++ katman\u0131nda (libuv arac\u0131l\u0131\u011f\u0131yla) uygulanm\u0131\u015ft\u0131r. Bu, Buffer’\u0131n performans a\u00e7\u0131s\u0131ndan olduk\u00e7a verimli oldu\u011fu ve do\u011frudan sistem belle\u011fiyle etkile\u015fime girdi\u011fini g\u00f6sterir.<\/p>\n
Buffer’lar, temel olarak bir dizi tamsay\u0131dan (her biri 0 ile 255 aras\u0131nda bir byte’\u0131 temsil eder) olu\u015fur. JavaScript’teki dizilerden fark\u0131, boyutunun olu\u015fturuldu\u011fu anda sabitlenmesi ve yaln\u0131zca byte’lar (sekiz bitlik veri birimi) tutabilmesidir. Bu \u00f6zellik, \u00f6zellikle dosya okuma\/yazma, HTTP istek ve yan\u0131t g\u00f6vdelerini i\u015fleme veya TCP soketleri \u00fczerinden veri al\u0131\u015fveri\u015fi gibi G\/\u00c7 yo\u011fun i\u015flemlerinde b\u00fcy\u00fck \u00f6nem ta\u015f\u0131r. \u00d6rne\u011fin, bir resim dosyas\u0131n\u0131 okudu\u011funuzda, bu dosya i\u00e7eri\u011fi bir Buffer nesnesi olarak temsil edilir. Ayn\u0131 \u015fekilde, bir sunucuya g\u00f6nderdi\u011finiz bir HTTP POST iste\u011finin g\u00f6vdesi de Buffer’a d\u00f6n\u00fc\u015ft\u00fcr\u00fclerek g\u00f6nderilir. Bu, Node.js’in di\u011fer dillerle (Python, Java, C#) a\u011f \u00fczerinden ikili veri al\u0131\u015fveri\u015fi yapmas\u0131n\u0131 m\u00fcmk\u00fcn k\u0131lar.<\/p>\n
Buffer olu\u015fturmak ve manip\u00fcle etmek olduk\u00e7a basittir. \u0130\u015fte birka\u00e7 \u00f6rnek:<\/p>\n
\n \/\/ 1. 10 byte'l\u0131k bo\u015f bir Buffer olu\u015fturma (i\u00e7erik rastgele olabilir)\n const buf1 = Buffer.alloc(10);\n console.log(buf1); \/\/ \n\n \/\/ 2. Bir string'den Buffer olu\u015fturma\n const buf2 = Buffer.from('Merhaba D\u00fcnya', 'utf8');\n console.log(buf2); \/\/ \n console.log(buf2.toString('utf8')); \/\/ Merhaba D\u00fcnya\n\n \/\/ 3. Bir array'den Buffer olu\u015fturma\n const buf3 = Buffer.from([1, 2, 3, 4, 5]);\n console.log(buf3); \/\/ \n\n \/\/ 4. Buffer'a veri yazma\n const buf4 = Buffer.alloc(5);\n buf4.write('abc');\n console.log(buf4.toString()); \/\/ abc\n\n \/\/ 5. Buffer'dan belirli bir indexteki byte'\u0131 okuma\n console.log(buf2[0]); \/\/ 77 (ASCII 'M')\n <\/pre>\n<\/code><\/p>\n
Buffer'lar ayn\u0131 zamanda \u00e7e\u015fitli encoding t\u00fcrlerini (UTF-8, UCS2, Base64, Hex, ASCII gibi) destekler. Bu, farkl\u0131 sistemler aras\u0131nda veri transferi yaparken veya belirli veri formatlar\u0131n\u0131 i\u015flerken b\u00fcy\u00fck kolayl\u0131k sa\u011flar. \u00d6rne\u011fin, Base64 encoding, ikili veriyi metin tabanl\u0131 bir formata d\u00f6n\u00fc\u015ft\u00fcrerek HTTP ba\u015fl\u0131klar\u0131nda veya JSON dosyalar\u0131nda ta\u015f\u0131nabilir hale getirmek i\u00e7in s\u0131k\u00e7a kullan\u0131l\u0131r. Sonu\u00e7 olarak, Buffer'lar Node.js'te ikili veri i\u015flemenin temelini olu\u015fturur. Bellek verimlili\u011fi, do\u011frudan sistem belle\u011fi eri\u015fimi ve \u00e7e\u015fitli encoding deste\u011fi sayesinde, Node.js uygulamalar\u0131n\u0131z\u0131n d\u00fc\u015f\u00fck seviyeli G\/\u00c7 i\u015flemlerinde \u00fcst\u00fcn performans sergilemesini sa\u011flarlar. Stream'ler ile birlikte kullan\u0131ld\u0131klar\u0131nda, b\u00fcy\u00fck veri k\u00fcmelerini ak\u0131\u015f halinde i\u015fleyerek uygulaman\u0131z\u0131n bellek ayak izini minimumda tutman\u0131za olanak tan\u0131r.<\/p>\n
Node.js Stream Kavram\u0131na Derinlemesine Bak\u0131\u015f: Veri Ak\u0131\u015f\u0131n\u0131 Y\u00f6netmek<\/h2>\n
Node.js'te Stream'ler, b\u00fcy\u00fck veri k\u00fcmelerini k\u00fc\u00e7\u00fck, y\u00f6netilebilir par\u00e7alar halinde i\u015flememizi sa\u011flayan soyut aray\u00fczlerdir. Geleneksel olarak, bir dosyan\u0131n tamam\u0131n\u0131 belle\u011fe y\u00fckleyip \u00f6yle i\u015flemek, dosya boyutu b\u00fcy\u00fcd\u00fck\u00e7e uygulaman\u0131n belle\u011fini a\u015f\u0131r\u0131 derecede t\u00fcketir ve performans\u0131 olumsuz etkiler. Stream'ler bu sorunu \u00e7\u00f6zmek i\u00e7in bir \u00e7\u00f6z\u00fcm sunar: veriyi bir kaynaktan par\u00e7a par\u00e7a okur, i\u015fler ve bir hedefe par\u00e7a par\u00e7a yazar. Bunu bir su borusu hatt\u0131na benzetebiliriz; su (veri) s\u00fcrekli olarak bir taraftan akar ve borudan ge\u00e7erken i\u015flenebilir, filtrelebilir veya ba\u015fka bir y\u00f6ne y\u00f6nlendirilebilir. T\u00fcm suyun bir depoda toplanmas\u0131n\u0131 beklemek yerine, ak\u0131\u015f halinde i\u015flem yapmak, \u00f6zellikle zaman ve bellek a\u00e7\u0131s\u0131ndan ciddi avantajlar sa\u011flar.<\/p>\n
Stream'lerin temel prensibi, Node.js'in olay g\u00fcd\u00fcml\u00fc mimarisiyle m\u00fckemmel bir uyum i\u00e7indedir. Veri ak\u0131\u015f\u0131 s\u0131ras\u0131nda \u00e7e\u015fitli olaylar tetiklenir (\u00f6rne\u011fin, 'data' geldi\u011finde, 'end' olay\u0131 tamamland\u0131\u011f\u0131nda, 'error' oldu\u011funda), bu da geli\u015ftiricilere ak\u0131\u015f \u00fczerindeki kontrol\u00fc art\u0131r\u0131r. Node.js'te d\u00f6rt ana Stream t\u00fcr\u00fc bulunur:<\/p>\n
\n- Readable Stream (Okunabilir Ak\u0131\u015f):<\/strong> Veri okumak i\u00e7in kullan\u0131l\u0131r. \u00d6rne\u011fin, bir dosyadan veri okuma veya bir HTTP sunucusundan gelen iste\u011fin g\u00f6vdesini okuma. Bu Stream'ler veriyi 'data' olaylar\u0131 arac\u0131l\u0131\u011f\u0131yla yayar.<\/li>\n
- Writable Stream (Yaz\u0131labilir Ak\u0131\u015f):<\/strong> Veri yazmak i\u00e7in kullan\u0131l\u0131r. \u00d6rne\u011fin, bir dosyaya veri yazma veya bir HTTP yan\u0131t\u0131 g\u00f6nderme. Bu Stream'ler, veriyi yazma i\u015flemini tamamlad\u0131\u011f\u0131nda 'finish' olay\u0131n\u0131 tetikler.<\/li>\n
- Duplex Stream (\u00c7ift Y\u00f6nl\u00fc Ak\u0131\u015f):<\/strong> Hem okunabilir hem de yaz\u0131labilir olan Stream'lerdir. \u00d6rne\u011fin, TCP soketleri hem veri alabilir hem de veri g\u00f6nderebilir.<\/li>\n
- Transform Stream (D\u00f6n\u00fc\u015ft\u00fcr\u00fclebilir Ak\u0131\u015f):<\/strong> Duplex Stream'lerin \u00f6zel bir t\u00fcr\u00fcd\u00fcr. Veriyi okur, \u00fczerinde bir d\u00f6n\u00fc\u015f\u00fcm i\u015flemi yapar ve d\u00f6n\u00fc\u015ft\u00fcr\u00fclm\u00fc\u015f veriyi yazar. \u00d6rne\u011fin, veriyi s\u0131k\u0131\u015ft\u0131rma, \u015fifreleme veya bi\u00e7imlendirme i\u015flemleri i\u00e7in kullan\u0131l\u0131r.<\/li>\n<\/ol>\n
Stream'lerin en g\u00fc\u00e7l\u00fc \u00f6zelliklerinden biri, .pipe()<\/code> metodudur. Bu metod, bir okunabilir Stream'in \u00e7\u0131kt\u0131s\u0131n\u0131 do\u011frudan bir yaz\u0131labilir Stream'in girdisine ba\u011flaman\u0131n kolay ve verimli bir yolunu sunar. Bu, karma\u015f\u0131k veri i\u015fleme boru hatlar\u0131 olu\u015fturmak i\u00e7in son derece faydal\u0131d\u0131r ve \"backpressure\" (geri bas\u0131n\u00e7) y\u00f6netimini otomatik olarak ele al\u0131r. Backpressure, bir yaz\u0131labilir Stream'in okunabilir Stream'e g\u00f6re daha yava\u015f veri i\u015fledi\u011fi durumlarda olu\u015fur. E\u011fer y\u00f6netilmezse, bu durum belle\u011fin a\u015f\u0131r\u0131 y\u00fcklenmesine yol a\u00e7abilir. .pipe()<\/code> metodu, yaz\u0131labilir Stream yava\u015f kald\u0131\u011f\u0131nda okunabilir Stream'i otomatik olarak duraklat\u0131r ('pause') ve haz\u0131r oldu\u011funda tekrar ba\u015flat\u0131r ('resume').<\/p>\n\n const fs = require('fs');\n\n const readableStream = fs.createReadStream('buyuk_dosya.txt');\n const writableStream = fs.createWriteStream('yeni_buyuk_dosya.txt');\n\n \/\/ readableStream'den okunan veriyi writableStream'e do\u011frudan pipe etme\n readableStream.pipe(writableStream);\n\n readableStream.on('end', () => {\n console.log('Dosya kopyalama tamamland\u0131.');\n });\n\n readableStream.on('error', (err) => {\n console.error('Okuma hatas\u0131:', err);\n });\n\n writableStream.on('error', (err) => {\n console.error('Yazma hatas\u0131:', err);\n });\n <\/pre>\n<\/code><\/p>\n
Bu \u00f6rnek, b\u00fcy\u00fck bir dosyay\u0131 okuyup ba\u015fka bir dosyaya yazarken bellek kullan\u0131m\u0131n\u0131 optimize etmenin ne kadar kolay oldu\u011funu g\u00f6steriyor. Stream'ler, Node.js uygulamalar\u0131n\u0131n sadece b\u00fcy\u00fck veri k\u00fcmeleriyle ba\u015fa \u00e7\u0131kmas\u0131n\u0131 sa\u011flamakla kalmaz, ayn\u0131 zamanda daha mod\u00fcler, yeniden kullan\u0131labilir ve test edilebilir kod yazmaya da yard\u0131mc\u0131 olur. Her Stream tipi belirli bir sorumlulu\u011fu \u00fcstlenir ve bu, uygulaman\u0131z\u0131n genel mimarisini basitle\u015ftirir. Bu sayede geli\u015ftiriciler, veri ak\u0131\u015f\u0131n\u0131 daha etkin bir \u015fekilde kontrol edebilir ve uygulaman\u0131n genel performans\u0131n\u0131 art\u0131rabilirler.<\/p>\n
\nUzman \u0130pucu: .pipe()<\/code> metodu, hata y\u00f6netimini otomatik olarak aktarmaz. Bu nedenle, her Stream i\u00e7in ayr\u0131 ayr\u0131 hata dinleyicileri ('error' olay\u0131) eklemek, uygulaman\u0131z\u0131n sa\u011flaml\u0131\u011f\u0131n\u0131 art\u0131r\u0131r.<\/p>\n<\/p><\/div>\nDosya \u0130\u015flemleriyle Stream ve Buffer Kullan\u0131m\u0131 Nas\u0131l Yap\u0131l\u0131r?<\/h2>\n
Node.js'te dosya i\u015flemleri, uygulamalar\u0131n temel ihtiya\u00e7lar\u0131ndan biridir. \u00d6zellikle b\u00fcy\u00fck boyutlu dosyalar\u0131 okuma veya yazma s\u00f6z konusu oldu\u011funda, Stream ve Buffer'lar performans ve bellek y\u00f6netimi a\u00e7\u0131s\u0131ndan hayati bir rol oynar. Dosyan\u0131n tamam\u0131n\u0131 belle\u011fe y\u00fcklemek yerine, Stream'ler veriyi k\u00fc\u00e7\u00fck, y\u00f6netilebilir par\u00e7alar (Buffer'lar) halinde okur ve i\u015fler. Bu yakla\u015f\u0131m, gigabaytlarca b\u00fcy\u00fckl\u00fc\u011f\u00fcndeki dosyalarla bile sorunsuz \u00e7al\u0131\u015fman\u0131z\u0131 sa\u011flar.<\/p>\n
B\u00fcy\u00fck Dosyalar\u0131 Okuma: Readable Stream Kullan\u0131m\u0131<\/h3>\n
Bir dosyadan veri okumak i\u00e7in fs.createReadStream()<\/code> fonksiyonunu kullan\u0131r\u0131z. Bu, bir Readable Stream nesnesi d\u00f6nd\u00fcr\u00fcr. Bu Stream, veriyi okuduk\u00e7a 'data' olay\u0131n\u0131 tetikler ve her 'data' olay\u0131, okunan bir Buffer par\u00e7as\u0131n\u0131 i\u00e7erir. Dosyan\u0131n sonuna gelindi\u011finde 'end' olay\u0131, bir hata olu\u015ftu\u011funda ise 'error' olay\u0131 tetiklenir.<\/p>\n\n const fs = require('fs');\n const path = require('path');\n\n const filePath = path.join(__dirname, 'ornek_buyuk_dosya.txt'); \/\/ B\u00fcy\u00fck bir test dosyas\u0131 olu\u015fturmal\u0131s\u0131n\u0131z\n\n \/\/ Dosya okuma ak\u0131\u015f\u0131n\u0131 olu\u015ftur\n const readStream = fs.createReadStream(filePath, { encoding: 'utf8', highWaterMark: 16 * 1024 }); \/\/ 16KB par\u00e7alar halinde oku\n\n let totalData = '';\n let chunkCount = 0;\n\n readStream.on('data', (chunk) => {\n \/\/ Her chunk bir Buffer nesnesidir. encoding 'utf8' belirtildi\u011fi i\u00e7in otomatik string'e d\u00f6ner.\n chunkCount++;\n totalData += chunk;\n console.log(Par\u00e7a ${chunkCount} okundu, boyut: ${chunk.length} byte.<\/code>);\n \/\/ \u00d6rne\u011fin, burada veriyi i\u015fleyebilir veya ba\u015fka bir yere yazabilirsiniz.\n });\n\n readStream.on('end', () => {\n console.log(\\nT\u00fcm dosya okundu. Toplam ${chunkCount} par\u00e7a i\u015flendi.<\/code>);\n \/\/ console.log('T\u00fcm Veri:', totalData.substring(0, 100) + '...'); \/\/ \u0130lk 100 karakteri g\u00f6ster\n });\n\n readStream.on('error', (err) => {\n console.error('Dosya okuma hatas\u0131:', err);\n });\n <\/pre>\n<\/code><\/p>\n
Yukar\u0131daki \u00f6rnekte, highWaterMark<\/code> se\u00e7ene\u011fi, ak\u0131\u015f\u0131n tek seferde ka\u00e7 byte veri okuyaca\u011f\u0131n\u0131 belirler. Bu de\u011fer, Node.js'in dahili Buffer boyutunu kontrol eder ve performans\u0131 etkileyebilir. Genellikle varsay\u0131lan de\u011ferler iyi \u00e7al\u0131\u015fsa da, \u00f6zel senaryolarda ayarlanabilir.<\/p>\nB\u00fcy\u00fck Dosyalar\u0131 Yazma: Writable Stream Kullan\u0131m\u0131<\/h3>\n
Bir dosyaya veri yazmak i\u00e7in fs.createWriteStream()<\/code> kullan\u0131l\u0131r. Bu, bir Writable Stream nesnesi d\u00f6nd\u00fcr\u00fcr. Veriyi write()<\/code> metodu ile bu ak\u0131\u015fa g\u00f6ndeririz. T\u00fcm veriler yaz\u0131ld\u0131ktan sonra end()<\/code> metodu \u00e7a\u011fr\u0131lmal\u0131d\u0131r.<\/p>\n\n const fs = require('fs');\n const path = require('path');\n\n const outputFilePath = path.join(__dirname, 'yazilacak_dosya.txt');\n\n const writeStream = fs.createWriteStream(outputFilePath, { encoding: 'utf8' });\n\n for (let i = 0; i < 10000; i++) {\n \/\/ writeStream.write() true d\u00f6nerse devam et, false d\u00f6nerse durakla\n const canWrite = writeStream.write(Bu, ${i + 1}. sat\u0131rdaki \u00f6rnek veridir.\\n<\/code>);\n if (!canWrite) {\n \/\/ Ak\u0131\u015f\u0131n dahili belle\u011fi doldu, 'drain' olay\u0131n\u0131 bekle\n console.log('Yazma ak\u0131\u015f\u0131 dolu, bekleniyor...');\n writeStream.once('drain', () => {\n console.log('Yazma ak\u0131\u015f\u0131 bo\u015fald\u0131, devam ediliyor...');\n });\n }\n }\n\n \/\/ T\u00fcm veriler yaz\u0131ld\u0131ktan sonra ak\u0131\u015f\u0131 sonland\u0131r\n writeStream.end('T\u00fcm veriler yaz\u0131ld\u0131.');\n\n writeStream.on('finish', () => {\n console.log('Dosya yazma i\u015flemi tamamland\u0131.');\n });\n\n writeStream.on('error', (err) => {\n console.error('Dosya yazma hatas\u0131:', err);\n });\n <\/pre>\n<\/code><\/p>\n
Bu \u00f6rnekte, writeStream.write()<\/code> metodunun d\u00f6n\u00fc\u015f de\u011feri kontrol edilerek \"backpressure\" (geri bas\u0131n\u00e7) y\u00f6netimi manuel olarak g\u00f6sterilmi\u015ftir. E\u011fer write()<\/code> false<\/code> d\u00f6nd\u00fcr\u00fcrse, bu, ak\u0131\u015f\u0131n dahili Buffer'\u0131n\u0131n doldu\u011funu ve daha fazla yazmadan \u00f6nce 'drain'<\/code> olay\u0131n\u0131n tetiklenmesini beklemeniz gerekti\u011fini g\u00f6sterir. Bu, bellek ta\u015fmas\u0131n\u0131 \u00f6nlemek i\u00e7in kritik \u00f6neme sahiptir.<\/p>\nVaka Analizi: B\u00fcy\u00fck Bir Dosyay\u0131 Kopyalama<\/h3>\n
En yayg\u0131n Stream kullan\u0131m senaryolar\u0131ndan biri, b\u00fcy\u00fck bir dosyay\u0131 bir konumdan di\u011ferine kopyalamakt\u0131r. Bunu .pipe()<\/code> metodunu kullanarak kolayca ve bellek dostu bir \u015fekilde yapabiliriz.<\/p>\n\n const fs = require('fs');\n const path = require('path');\n\n const sourcePath = path.join(__dirname, 'kaynak_dosya.mp4'); \/\/ \u00d6rne\u011fin 1GB'l\u0131k bir video dosyas\u0131\n const destinationPath = path.join(__dirname, 'kopya_dosya.mp4');\n\n console.log('Dosya kopyalama i\u015flemi ba\u015fl\u0131yor...');\n\n const readStream = fs.createReadStream(sourcePath);\n const writeStream = fs.createWriteStream(destinationPath);\n\n readStream.pipe(writeStream); \/\/ Veriyi do\u011frudan bir ak\u0131\u015ftan di\u011ferine y\u00f6nlendir\n\n readStream.on('error', (err) => {\n console.error('Okuma ak\u0131\u015f\u0131nda hata:', err);\n process.exit(1); \/\/ Uygulamay\u0131 sonland\u0131r\n });\n\n writeStream.on('error', (err) => {\n console.error('Yazma ak\u0131\u015f\u0131nda hata:', err);\n process.exit(1); \/\/ Uygulamay\u0131 sonland\u0131r\n });\n\n writeStream.on('finish', () => {\n console.log('Dosya kopyalama ba\u015far\u0131yla tamamland\u0131!');\n });\n <\/pre>\n<\/code><\/p>\n
Bu basit \u00f6rnek, .pipe()<\/code> metodunun g\u00fcc\u00fcn\u00fc ve verimlili\u011fini g\u00f6zler \u00f6n\u00fcne seriyor. Bu y\u00f6ntemle, kaynak dosyay\u0131 tamamen belle\u011fe y\u00fcklemek zorunda kalmadan, veriyi par\u00e7a par\u00e7a okuyup ayn\u0131 anda hedef dosyaya yazarak bellek kullan\u0131m\u0131n\u0131 minimumda tutabilirsiniz. Bu sayede, uygulaman\u0131z \u00e7ok b\u00fcy\u00fck dosyalar\u0131 bile etkili bir \u015fekilde i\u015fleyebilir. Dosya i\u015flemleri, Node.js Stream ve Buffer'\u0131n temel uygulama alanlar\u0131ndan biridir ve bu kavramlar\u0131n anla\u015f\u0131lmas\u0131, \u00f6l\u00e7eklenebilir ve performansl\u0131 Node.js uygulamalar\u0131 geli\u015ftirmek i\u00e7in vazge\u00e7ilmezdir. Dolay\u0131s\u0131yla, bu konuda pratik yapmak, yeteneklerinizi geli\u015ftirmenize b\u00fcy\u00fck katk\u0131 sa\u011flayacakt\u0131r.<\/p>\nA\u011f \u0130leti\u015fiminde Stream ve Buffer'lar\u0131n Rol\u00fc Nedir?<\/h2>\n
Node.js, a\u011f uygulamalar\u0131 geli\u015ftirmek i\u00e7in tasarlanm\u0131\u015f bir \u00e7al\u0131\u015fma zaman\u0131d\u0131r ve Stream ile Buffer mekanizmalar\u0131, a\u011f ileti\u015fimi ba\u011flam\u0131nda da merkezi bir rol oynar. HTTP, TCP veya UDP gibi a\u011f protokolleri \u00fczerinden g\u00f6nderilen ve al\u0131nan t\u00fcm veriler, arka planda Buffer'lar ve Stream'ler arac\u0131l\u0131\u011f\u0131yla i\u015flenir. Bu sayede, b\u00fcy\u00fck boyutlu veri transferleri veya ger\u00e7ek zamanl\u0131 ileti\u015fim, bellek a\u00e7\u0131s\u0131ndan verimli ve performansl\u0131 bir \u015fekilde ger\u00e7ekle\u015ftirilir.<\/p>\n
HTTP \u0130stek ve Yan\u0131tlar\u0131nda Stream'ler<\/h3>\n
Node.js'in http<\/code> mod\u00fcl\u00fc, HTTP istekleri ve yan\u0131tlar\u0131n\u0131 birer Stream nesnesi olarak ele al\u0131r. Bir sunucuya gelen HTTP iste\u011fi (IncomingMessage<\/code>) bir Readable Stream'dir ve istemciye g\u00f6nderilen HTTP yan\u0131t\u0131 (ServerResponse<\/code>) bir Writable Stream'dir.<\/p>\n\n const http = require('http');\n const fs = require('fs');\n const path = require('path');\n\n const server = http.createServer((req, res) => {\n if (req.url === '\/') {\n res.writeHead(200, { 'Content-Type': 'text\/html; charset=utf-8' });\n res.end('B\u00fcy\u00fck bir dosya indirmek i\u00e7in \/download adresine gidin.<\/h1>');\n } else if (req.url === '\/download') {\n const filePath = path.join(__dirname, 'ornek_buyuk_dosya.zip'); \/\/ \u00d6rne\u011fin 500MB'l\u0131k bir dosya\n fs.access(filePath, fs.constants.F_OK, (err) => {\n if (err) {\n res.writeHead(404, { 'Content-Type': 'text\/plain' });\n res.end('Dosya bulunamad\u0131.');\n return;\n }\n\n const stat = fs.statSync(filePath); \/\/ Dosya boyutunu almak i\u00e7in\n res.writeHead(200, {\n 'Content-Type': 'application\/zip',\n 'Content-Length': stat.size,\n 'Content-Disposition': 'attachment; filename=\"buyuk_dosya.zip\"' \/\/ Taray\u0131c\u0131n\u0131n dosyay\u0131 indirmesini sa\u011flar\n });\n\n const readStream = fs.createReadStream(filePath);\n readStream.pipe(res); \/\/ Dosyay\u0131 do\u011frudan HTTP yan\u0131t\u0131na ak\u0131t\n\n readStream.on('error', (streamErr) => {\n console.error('Dosya okuma hatas\u0131:', streamErr);\n res.end('Dosya okunurken bir hata olu\u015ftu.');\n });\n\n \/\/ Taray\u0131c\u0131 ba\u011flant\u0131y\u0131 erken kapat\u0131rsa, stream'i sonland\u0131r\n req.on('close', () => {\n readStream.destroy();\n });\n\n });\n } else if (req.url === '\/upload' && req.method === 'POST') {\n let receivedDataSize = 0;\n const uploadFilePath = path.join(__dirname, 'yuklenen_dosya.txt');\n const writeStream = fs.createWriteStream(uploadFilePath);\n\n req.on('data', (chunk) => {\n \/\/ Her chunk bir Buffer'd\u0131r\n receivedDataSize += chunk.length;\n console.log(Y\u00fcklenen veri: ${receivedDataSize} byte<\/code>);\n writeStream.write(chunk); \/\/ Gelen veriyi dosyaya yaz\n });\n\n req.on('end', () => {\n writeStream.end(); \/\/ Yazma ak\u0131\u015f\u0131n\u0131 sonland\u0131r\n res.writeHead(200, { 'Content-Type': 'text\/plain' });\n res.end(Dosya ba\u015far\u0131yla y\u00fcklendi! Toplam ${receivedDataSize} byte.<\/code>);\n });\n\n req.on('error', (err) => {\n console.error('Y\u00fckleme hatas\u0131:', err);\n writeStream.destroy();\n res.writeHead(500, { 'Content-Type': 'text\/plain' });\n res.end('Dosya y\u00fcklenirken bir hata olu\u015ftu.');\n });\n\n } else {\n res.writeHead(404, { 'Content-Type': 'text\/plain' });\n res.end('Sayfa bulunamad\u0131.');\n }\n });\n\n server.listen(3000, () => {\n console.log('Sunucu http:\/\/localhost:3000 adresinde \u00e7al\u0131\u015f\u0131yor.');\n });\n <\/pre>\n<\/code><\/p>\n
Bu \u00f6rnek, HTTP sunucusunun b\u00fcy\u00fck bir dosyay\u0131 nas\u0131l Stream'ler arac\u0131l\u0131\u011f\u0131yla indirilebilir hale getirdi\u011fini (\/download<\/code> yolu) ve bir dosya y\u00fckleme (\/upload<\/code> yolu) i\u015flemini nas\u0131l y\u00f6netti\u011fini g\u00f6sterir. req<\/code> (istek) bir Readable Stream oldu\u011fundan, 'data'<\/code> olaylar\u0131n\u0131 dinleyerek gelen veriyi Buffer par\u00e7alar\u0131 halinde alabilir ve do\u011frudan bir dosyaya yazabilirsiniz. Benzer \u015fekilde, res<\/code> (yan\u0131t) bir Writable Stream oldu\u011fundan, bir dosya okuma ak\u0131\u015f\u0131n\u0131 (fs.createReadStream<\/code>) do\u011frudan HTTP yan\u0131t\u0131na pipe()<\/code> edebilirsiniz. Bu, sunucunun dosyay\u0131 tamamen belle\u011fe y\u00fcklemeden istemciye g\u00f6ndermesini sa\u011flar, bu da hem bellek t\u00fcketimini azalt\u0131r hem de yan\u0131t s\u00fcresini iyile\u015ftirir.<\/p>\nVaka Analizi: B\u00fcy\u00fck Bir Dosya Y\u00fckleme Sunucusu<\/h3>\n
Yukar\u0131daki \u00f6rnekte g\u00f6sterildi\u011fi gibi, b\u00fcy\u00fck dosyalar\u0131n sunucuya y\u00fcklenmesi de Stream'ler sayesinde verimli bir \u015fekilde y\u00f6netilebilir. \u0130stemciden gelen istek g\u00f6vdesi (req<\/code> nesnesi), Readable Stream olarak davran\u0131r. Bu, istemcinin g\u00f6nderdi\u011fi veriyi par\u00e7a par\u00e7a alabilece\u011finiz anlam\u0131na gelir. Her bir veri par\u00e7as\u0131 bir Buffer nesnesidir ve bu Buffer'lar\u0131 do\u011frudan bir fs.createWriteStream()<\/code> ile bir dosyaya yazabilirsiniz.<\/p>\n\nUzman \u0130pucu: \u00c7ok b\u00fcy\u00fck dosyalar\u0131 y\u00fcklerken, y\u00fckleme ilerlemesini kullan\u0131c\u0131ya bildirmek i\u00e7in req.on('data')<\/code> i\u00e7inde toplam y\u00fcklenen boyutu takip edebilir ve bu bilgiyi istemciye WebSockets gibi ger\u00e7ek zamanl\u0131 teknolojilerle iletebilirsiniz.<\/p>\n<\/p><\/div>\nA\u011f ileti\u015fiminde Stream ve Buffer kullan\u0131m\u0131, Node.js'in y\u00fcksek performansl\u0131, \u00f6l\u00e7eklenebilir a\u011f uygulamalar\u0131 olu\u015fturma yetene\u011finin temelinde yatar. \u0130kili verinin do\u011frudan manip\u00fclasyonu i\u00e7in Buffer'lar ve bu verinin ak\u0131\u015f halinde i\u015flenmesi i\u00e7in Stream'ler, Node.js geli\u015ftiricilerine a\u011f tabanl\u0131 sistemlerde \u00fcst\u00fcn kontrol ve verimlilik sa\u011flar. Bu sayede, dosya sunucular\u0131ndan medya ak\u0131\u015f hizmetlerine, API a\u011f ge\u00e7itlerinden ger\u00e7ek zamanl\u0131 mesajla\u015fma sistemlerine kadar geni\u015f bir yelpazede uygulamalar geli\u015ftirmek m\u00fcmk\u00fcn hale gelir.<\/p>\n
Transform Stream'ler ile Veri D\u00f6n\u00fc\u015f\u00fcm\u00fc Nas\u0131l Yap\u0131l\u0131r?<\/h2>\n
Node.js'te Transform Stream'ler, veri ak\u0131\u015f\u0131 s\u0131ras\u0131nda veriyi okuyup, \u00fczerinde bir i\u015flem yap\u0131p (d\u00f6n\u00fc\u015ft\u00fcr\u00fcp) ve ard\u0131ndan d\u00f6n\u00fc\u015ft\u00fcr\u00fclm\u00fc\u015f veriyi yazan \u00f6zel bir Duplex Stream t\u00fcr\u00fcd\u00fcr. Yani, hem Readable hem de Writable \u00f6zelliklere sahiptirler. Bu, \u00f6zellikle veri s\u0131k\u0131\u015ft\u0131rma, \u015fifreleme, format d\u00f6n\u00fc\u015ft\u00fcrme veya metin i\u015fleme gibi senaryolarda \u00e7ok kullan\u0131\u015fl\u0131d\u0131r. Bir Transform Stream, girdiyi al\u0131r, \u00e7\u0131kt\u0131y\u0131 \u00fcretir ve bu i\u015flemi tamamen ak\u0131\u015f halinde ger\u00e7ekle\u015ftirir, b\u00f6ylece t\u00fcm verinin belle\u011fe y\u00fcklenmesi gerekmez.<\/p>\n
Neden Transform Stream Kullanmal\u0131y\u0131z?<\/h3>\n\n- Bellek Verimlili\u011fi:<\/strong> B\u00fcy\u00fck veri k\u00fcmelerini d\u00f6n\u00fc\u015ft\u00fcr\u00fcrken, t\u00fcm veriyi belle\u011fe almak yerine par\u00e7a par\u00e7a i\u015fler, bu da bellek t\u00fcketimini \u00f6nemli \u00f6l\u00e7\u00fcde azalt\u0131r.<\/li>\n
- Mod\u00fclerlik:<\/strong> Her d\u00f6n\u00fc\u015f\u00fcm i\u015flemini ayr\u0131 bir Transform Stream olarak tan\u0131mlayarak kodunuzu daha mod\u00fcler ve yeniden kullan\u0131labilir hale getirebilirsiniz.<\/li>\n
- Esneklik:<\/strong>
.pipe()<\/code> metodu ile birden fazla Transform Stream'i art arda ba\u011flayarak karma\u015f\u0131k veri i\u015fleme boru hatlar\u0131 olu\u015fturabilirsiniz.<\/li>\n<\/ul>\nCustom Transform Stream Olu\u015fturma<\/h3>\n
Kendi Transform Stream'imizi olu\u015fturmak i\u00e7in Node.js'in stream<\/code> mod\u00fcl\u00fcndeki Transform<\/code> s\u0131n\u0131f\u0131n\u0131 geni\u015fletmemiz gerekir. Temel olarak, _transform()<\/code> metodunu uygulamam\u0131z gerekecek. Bu metod, gelen her veri par\u00e7as\u0131n\u0131 (chunk) d\u00f6n\u00fc\u015ft\u00fcrmek ve d\u00f6n\u00fc\u015ft\u00fcr\u00fclm\u00fc\u015f veriyi ak\u0131\u015fa yazmak i\u00e7in kullan\u0131l\u0131r.<\/p>\n\n const { Transform } = require('stream');\n\n \/\/ B\u00fcy\u00fck harfe d\u00f6n\u00fc\u015ft\u00fcren \u00f6zel bir Transform Stream\n class UppercaseTransform extends Transform {\n constructor(options) {\n super(options);\n }\n\n _transform(chunk, encoding, callback) {\n \/\/ Gelen Buffer'\u0131 string'e \u00e7evir, b\u00fcy\u00fck harfe d\u00f6n\u00fc\u015ft\u00fcr ve tekrar Buffer'a \u00e7evir\n const transformedChunk = chunk.toString().toUpperCase();\n this.push(transformedChunk); \/\/ D\u00f6n\u00fc\u015ft\u00fcr\u00fclm\u00fc\u015f veriyi ak\u0131\u015fa yaz\n callback(); \/\/ \u0130\u015flemin tamamland\u0131\u011f\u0131n\u0131 bildir\n }\n\n _flush(callback) {\n \/\/ Ak\u0131\u015f kapanmadan \u00f6nce son i\u015flemleri yapmak i\u00e7in (iste\u011fe ba\u011fl\u0131)\n console.log('Uppercase d\u00f6n\u00fc\u015f\u00fcm\u00fc tamamland\u0131.');\n callback();\n }\n }\n\n \/\/ Kullan\u0131m \u00f6rne\u011fi:\n const fs = require('fs');\n const path = require('path');\n\n const inputFile = path.join(__dirname, 'input.txt');\n const outputFile = path.join(__dirname, 'output_uppercase.txt');\n\n \/\/ Test i\u00e7in input.txt dosyas\u0131na k\u00fc\u00e7\u00fck harfli metin yazal\u0131m\n fs.writeFileSync(inputFile, 'Merhaba d\u00fcnya, bu bir test metnidir.');\n\n console.log('Metin d\u00f6n\u00fc\u015ft\u00fcrme i\u015flemi ba\u015fl\u0131yor...');\n\n const readStream = fs.createReadStream(inputFile, { encoding: 'utf8' });\n const uppercaseTransform = new UppercaseTransform();\n const writeStream = fs.createWriteStream(outputFile, { encoding: 'utf8' });\n\n readStream\n .pipe(uppercaseTransform) \/\/ Okunan veriyi b\u00fcy\u00fck harfe d\u00f6n\u00fc\u015ft\u00fcr\n .pipe(writeStream) \/\/ D\u00f6n\u00fc\u015ft\u00fcr\u00fclm\u00fc\u015f veriyi dosyaya yaz\n .on('finish', () => {\n console.log('D\u00f6n\u00fc\u015ft\u00fcrme ve yazma i\u015flemi tamamland\u0131.');\n \/\/ Okuyucuya d\u00f6n\u00fc\u015ft\u00fcr\u00fclen dosyan\u0131n i\u00e7eri\u011fini g\u00f6stermek i\u00e7in\n fs.readFile(outputFile, 'utf8', (err, data) => {\n if (err) console.error(err);\n console.log('D\u00f6n\u00fc\u015ft\u00fcr\u00fclm\u00fc\u015f \u0130\u00e7erik:\\n', data);\n });\n })\n .on('error', (err) => {\n console.error('Ak\u0131\u015f hatas\u0131:', err);\n });\n <\/pre>\n<\/code><\/p>\n
_transform(chunk, encoding, callback)<\/code> metodu, her veri par\u00e7as\u0131 geldi\u011finde \u00e7a\u011fr\u0131l\u0131r. chunk<\/code> bir Buffer nesnesidir, encoding<\/code> string olarak chunk'\u0131n kodlamas\u0131n\u0131 belirtir ve callback<\/code> ise d\u00f6n\u00fc\u015f\u00fcm i\u015fleminin tamamland\u0131\u011f\u0131n\u0131 Node.js'e bildirmek i\u00e7in \u00e7a\u011fr\u0131l\u0131r. this.push(data)<\/code> ile d\u00f6n\u00fc\u015ft\u00fcr\u00fclm\u00fc\u015f veriyi \u00e7\u0131kt\u0131 ak\u0131\u015f\u0131na g\u00f6ndeririz. _flush()<\/code> metodu ise, t\u00fcm girdi Stream'i okunduktan ve t\u00fcm chunk'lar d\u00f6n\u00fc\u015ft\u00fcr\u00fcld\u00fckten sonra, \u00e7\u0131kt\u0131 ak\u0131\u015f\u0131na yazmadan \u00f6nce son verileri i\u015flemek i\u00e7in kullan\u0131l\u0131r.<\/p>\nVaka Analizi: Veriyi S\u0131k\u0131\u015ft\u0131rma (Gzip)<\/h3>\n
Node.js'in dahili zlib<\/code> mod\u00fcl\u00fc, Transform Stream'ler kullanarak s\u0131k\u0131\u015ft\u0131rma (gzip) ve a\u00e7ma (gunzip) i\u015flemleri yapmam\u0131z\u0131 sa\u011flar. Bu, b\u00fcy\u00fck dosyalar\u0131 aktar\u0131rken veya depolarken bant geni\u015fli\u011fini ve depolama alan\u0131n\u0131 optimize etmek i\u00e7in harikad\u0131r.<\/p>\n\n const fs = require('fs');\n const path = require('path');\n const zlib = require('zlib'); \/\/ Zlib mod\u00fcl\u00fcn\u00fc dahil et\n\n const inputFile = path.join(__dirname, 'input.txt');\n const compressedFile = path.join(__dirname, 'input.txt.gz');\n const decompressedFile = path.join(__dirname, 'decompressed_input.txt');\n\n \/\/ Test i\u00e7in b\u00fcy\u00fck bir input dosyas\u0131 olu\u015ftural\u0131m\n fs.writeFileSync(inputFile, 'Bu, s\u0131k\u0131\u015ft\u0131r\u0131lacak \u00e7ok b\u00fcy\u00fck bir metin dosyas\u0131d\u0131r. '.repeat(1000));\n\n console.log('Dosya s\u0131k\u0131\u015ft\u0131rma i\u015flemi ba\u015fl\u0131yor...');\n\n \/\/ Dosyay\u0131 s\u0131k\u0131\u015ft\u0131rma\n fs.createReadStream(inputFile)\n .pipe(zlib.createGzip()) \/\/ Gzip Transform Stream'i\n .pipe(fs.createWriteStream(compressedFile))\n .on('finish', () => {\n console.log('Dosya ba\u015far\u0131yla s\u0131k\u0131\u015ft\u0131r\u0131ld\u0131: input.txt.gz');\n\n console.log('Dosya a\u00e7ma i\u015flemi ba\u015fl\u0131yor...');\n \/\/ S\u0131k\u0131\u015ft\u0131r\u0131lm\u0131\u015f dosyay\u0131 a\u00e7ma\n fs.createReadStream(compressedFile)\n .pipe(zlib.createGunzip()) \/\/ Gunzip Transform Stream'i\n .pipe(fs.createWriteStream(decompressedFile))\n .on('finish', () => {\n console.log('Dosya ba\u015far\u0131yla a\u00e7\u0131ld\u0131: decompressed_input.txt');\n \/\/ Orijinal ve a\u00e7\u0131lm\u0131\u015f dosyan\u0131n boyutlar\u0131n\u0131 kar\u015f\u0131la\u015ft\u0131rabiliriz\n const originalSize = fs.statSync(inputFile).size;\n const compressedSize = fs.statSync(compressedFile).size;\n const decompressedSize = fs.statSync(decompressedFile).size;\n\n console.log(Orijinal boyut: ${originalSize} byte<\/code>);\n console.log(S\u0131k\u0131\u015ft\u0131r\u0131lm\u0131\u015f boyut: ${compressedSize} byte<\/code>);\n console.log(A\u00e7\u0131lm\u0131\u015f boyut: ${decompressedSize} byte<\/code>);\n })\n .on('error', (err) => console.error('A\u00e7ma hatas\u0131:', err));\n })\n .on('error', (err) => console.error('S\u0131k\u0131\u015ft\u0131rma hatas\u0131:', err));\n <\/pre>\n<\/code><\/p>\n
Bu \u00f6rnekte, zlib.createGzip()<\/code> ve zlib.createGunzip()<\/code> fonksiyonlar\u0131, do\u011frudan kullan\u0131labilecek Transform Stream'ler olu\u015fturur. Bu Stream'leri .pipe()<\/code> ile birle\u015ftirerek, dosya s\u0131k\u0131\u015ft\u0131rma ve a\u00e7ma i\u015flemlerini \u00e7ok az bellek kullanarak kolayca ger\u00e7ekle\u015ftirebiliriz. Transform Stream'ler, Node.js'te veri i\u015fleme boru hatlar\u0131n\u0131n omurgas\u0131n\u0131 olu\u015fturur ve veri d\u00f6n\u00fc\u015f\u00fcm\u00fc gerektiren herhangi bir senaryoda g\u00fc\u00e7l\u00fc, verimli ve esnek \u00e7\u00f6z\u00fcmler sunar.<\/p>\nBackpressure ve Ak\u0131\u015f Kontrol\u00fc: Performans\u0131 Nas\u0131l Maksimize Ederiz?<\/h2>\n
Node.js Stream'leri kullan\u0131rken kar\u015f\u0131la\u015f\u0131labilecek en \u00f6nemli kavramlardan biri \"backpressure\" (geri bas\u0131n\u00e7) y\u00f6netimidir. Backpressure, bir Readable Stream'in veriyi bir Writable Stream'den daha h\u0131zl\u0131 \u00fcretti\u011fi durumda ortaya \u00e7\u0131kar. E\u011fer bu durum do\u011fru \u015fekilde y\u00f6netilmezse, Writable Stream'in i\u015fleme h\u0131z\u0131na yeti\u015femeyen veri, sistemin belle\u011finde birikmeye ba\u015flar ve sonunda belle\u011fin a\u015f\u0131r\u0131 y\u00fcklenerek uygulaman\u0131n \u00e7\u00f6kmesine yol a\u00e7abilir. Bu, su borusu hatt\u0131 benzetmesinde, muslu\u011fun borunun tahliye kapasitesinden daha fazla su ak\u0131tmas\u0131 gibidir; boru t\u0131kan\u0131r ve su ta\u015fmaya ba\u015flar.<\/p>\n
Backpressure Neden \u00d6nemlidir?<\/h3>\n\n- Bellek S\u0131z\u0131nt\u0131lar\u0131n\u0131 \u00d6nler:<\/strong> Kontrols\u00fcz veri birikimi, uygulaman\u0131n bellek t\u00fcketimini art\u0131r\u0131r ve uzun vadede bellek s\u0131z\u0131nt\u0131lar\u0131na yol a\u00e7abilir.<\/li>\n
- Sistem Kararl\u0131l\u0131\u011f\u0131 Sa\u011flar:<\/strong> Uygulaman\u0131n y\u00fcksek y\u00fck alt\u0131nda bile kararl\u0131 bir \u015fekilde \u00e7al\u0131\u015fmas\u0131n\u0131 garanti eder.<\/li>\n
- Performans Optimizasyonu:<\/strong> Kaynaklar\u0131n do\u011fru zamanda ve do\u011fru miktarda kullan\u0131lmas\u0131n\u0131 sa\u011flayarak genel sistem performans\u0131n\u0131 art\u0131r\u0131r.<\/li>\n<\/ul>\n
Node.js Stream'lerinde Backpressure Y\u00f6netimi<\/h3>\n
Node.js'in Stream API'si, backpressure'\u0131 y\u00f6netmek i\u00e7in yerle\u015fik mekanizmalara sahiptir, ancak geli\u015ftiricinin bu mekanizmalar\u0131 do\u011fru bir \u015fekilde kullanmas\u0131 gerekir. En temel y\u00f6netim arac\u0131 .pipe()<\/code> metodudur. .pipe()<\/code>, okunabilir ve yaz\u0131labilir Stream'ler aras\u0131ndaki ak\u0131\u015f kontrol\u00fcn\u00fc otomatik olarak ele al\u0131r. Yaz\u0131labilir Stream'in dahili Buffer'\u0131 dolmaya ba\u015flad\u0131\u011f\u0131nda, okunabilir Stream'i otomatik olarak duraklat\u0131r (pause()<\/code>). Yaz\u0131labilir Stream yeterince veri i\u015fleyip Buffer'\u0131n\u0131 bo\u015faltt\u0131\u011f\u0131nda ('drain' olay\u0131), okunabilir Stream'i tekrar ba\u015flat\u0131r (resume()<\/code>).<\/p>\n\n const fs = require('fs');\n const path = require('path');\n const { Writable } = require('stream');\n\n const sourceFile = path.join(__dirname, 'buyuk_veri.txt');\n const destinationFile = path.join(__dirname, 'islenmis_veri.txt');\n\n \/\/ Test i\u00e7in b\u00fcy\u00fck bir dosya olu\u015ftural\u0131m\n let largeContent = '';\n for (let i = 0; i < 100000; i++) {\n largeContent += Bu, ${i + 1}. sat\u0131rda yaz\u0131lan bir \u00f6rnek veridir. Bu veri yava\u015f\u00e7a i\u015flenecektir.\\n<\/code>;\n }\n fs.writeFileSync(sourceFile, largeContent);\n\n \/\/ Veriyi yava\u015f i\u015fleyen \u00f6zel bir yaz\u0131labilir ak\u0131\u015f olu\u015ftural\u0131m\n class SlowWriteStream extends Writable {\n constructor(options) {\n super(options);\n this.destination = fs.createWriteStream(destinationFile);\n }\n\n _write(chunk, encoding, callback) {\n \/\/ Yava\u015f i\u015fleme sim\u00fclasyonu\n setTimeout(() => {\n this.destination.write(chunk, encoding, callback);\n \/\/ console.log(Yava\u015f yaz\u0131ld\u0131: ${chunk.length} byte<\/code>);\n }, 50); \/\/ Her par\u00e7ay\u0131 yazmadan \u00f6nce 50ms bekle\n }\n\n _final(callback) {\n this.destination.end(callback);\n console.log('Yava\u015f yazma ak\u0131\u015f\u0131 tamamland\u0131.');\n }\n\n _destroy(err, callback) {\n this.destination.destroy(err);\n callback(err);\n }\n }\n\n console.log('Backpressure testi ba\u015fl\u0131yor...');\n\n const readable = fs.createReadStream(sourceFile);\n const slowWritable = new SlowWriteStream({ highWaterMark: 16 * 1024 }); \/\/ D\u00fc\u015f\u00fck highWaterMark ile daha s\u0131k duraklama\n\n readable.pipe(slowWritable)\n .on('finish', () => {\n console.log('T\u00fcm veriler ba\u015far\u0131yla i\u015flendi ve yaz\u0131ld\u0131.');\n })\n .on('error', (err) => {\n console.error('Ak\u0131\u015f hatas\u0131:', err);\n });\n\n readable.on('pause', () => {\n console.log('Okunabilir ak\u0131\u015f duraklat\u0131ld\u0131 (backpressure devrede).');\n });\n\n readable.on('resume', () => {\n console.log('Okunabilir ak\u0131\u015f devam etti.');\n });\n <\/pre>\n<\/code><\/p>\n
Yukar\u0131daki \u00f6rnekte, SlowWriteStream<\/code>, her veri par\u00e7as\u0131n\u0131 yazmadan \u00f6nce 50 milisaniye bekleyerek yapay bir yava\u015flama yarat\u0131r. Bu, readable.pipe(slowWritable)<\/code> hatt\u0131nda backpressure'\u0131n nas\u0131l \u00e7al\u0131\u015ft\u0131\u011f\u0131n\u0131 g\u00f6zlemlememizi sa\u011flar. readable.on('pause')<\/code> ve readable.on('resume')<\/code> olay dinleyicileri, .pipe()<\/code> metodunun dahili olarak ak\u0131\u015f kontrol\u00fcn\u00fc nas\u0131l y\u00f6netti\u011fini g\u00f6sterir. Okunabilir ak\u0131\u015f\u0131n highWaterMark<\/code> de\u011feri, okunabilir ak\u0131\u015f\u0131n dahili Buffer'\u0131n\u0131n ne kadar doldu\u011funu ifade eder ve writable<\/code> Stream'in highWaterMark<\/code> de\u011feri de ne zaman false<\/code> d\u00f6nece\u011fini belirler. Bu de\u011ferler, backpressure y\u00f6netimini do\u011frudan etkiler.<\/p>\n\nUzman \u0130pucu: Manuel backpressure y\u00f6netimi (write()<\/code> d\u00f6n\u00fc\u015f de\u011ferini kontrol edip 'drain'<\/code> olay\u0131n\u0131 beklemek), .pipe()<\/code> metodunu kullanmad\u0131\u011f\u0131n\u0131z veya custom Stream'ler yazd\u0131\u011f\u0131n\u0131z karma\u015f\u0131k senaryolarda kritik \u00f6neme sahiptir.<\/p>\n<\/p><\/div>\nStream'lerin highWaterMark<\/code> se\u00e7ene\u011fi, Stream'in dahili Buffer'\u0131n\u0131n maksimum boyutunu belirler. Bu de\u011fer, performans ve bellek kullan\u0131m\u0131 aras\u0131nda bir denge kurmak i\u00e7in \u00f6nemlidir. Daha y\u00fcksek bir highWaterMark<\/code>, daha az duraklama\/ba\u015flatma (pause\/resume) olay\u0131 anlam\u0131na gelir, ancak ayn\u0131 zamanda bellekte daha fazla veri tutulmas\u0131na neden olur. Tersine, daha d\u00fc\u015f\u00fck bir de\u011fer, daha s\u0131k ak\u0131\u015f kontrol\u00fc ve daha az bellek kullan\u0131m\u0131 anlam\u0131na gelir. Backpressure y\u00f6netimi, \u00f6zellikle y\u00fcksek hacimli veri ak\u0131\u015flar\u0131n\u0131 i\u00e7eren Node.js uygulamalar\u0131nda performans\u0131 ve kararl\u0131l\u0131\u011f\u0131 sa\u011flamak i\u00e7in vazge\u00e7ilmez bir konsepttir. .pipe()<\/code> kullan\u0131m\u0131 en basit ve etkili y\u00f6ntem olsa da, \u00f6zel durumlar i\u00e7in Stream olaylar\u0131n\u0131 ve metodlar\u0131n\u0131 manuel olarak y\u00f6netme becerisi, geli\u015ftiricinin Stream API'sindeki ustal\u0131\u011f\u0131n\u0131 g\u00f6sterir.<\/p>\nNode.js'te Stream ve Buffer Kullan\u0131m\u0131n\u0131n Temel Faydalar\u0131 Nelerdir?<\/h2>\n
Bu makalede Node.js Stream ve Buffer kavramlar\u0131n\u0131 derinlemesine inceledik. G\u00f6rd\u00fck ki, bu iki temel yap\u0131 ta\u015f\u0131, Node.js'in b\u00fcy\u00fck \u00f6l\u00e7ekli ve y\u00fcksek performansl\u0131 uygulamalar geli\u015ftirmedeki g\u00fcc\u00fcn\u00fcn arkas\u0131ndaki anahtar bile\u015fenlerdir. \u00d6zetle, Stream'ler ve Buffer'lar, Node.js ekosisteminde veri i\u015fleme yakla\u015f\u0131mlar\u0131m\u0131z\u0131 k\u00f6kten de\u011fi\u015ftirerek, geli\u015ftiricilere daha verimli, \u00f6l\u00e7eklenebilir ve kararl\u0131 \u00e7\u00f6z\u00fcmler sunar. Gelin, Stream ve Buffer kullan\u0131m\u0131n\u0131n temel faydalar\u0131n\u0131 bir kez daha g\u00f6zden ge\u00e7irelim:<\/p>\n
\n- Bellek Verimlili\u011fi:<\/strong> En \u00f6nemli faydas\u0131 budur. Veriyi par\u00e7a par\u00e7a i\u015fleyerek, b\u00fcy\u00fck dosyalar\u0131n veya veri ak\u0131\u015flar\u0131n\u0131n tamam\u0131n\u0131n belle\u011fe y\u00fcklenmesini engeller. Bu, uygulaman\u0131z\u0131n bellek ayak izini minimumda tutar ve olas\u0131 bellek ta\u015fmalar\u0131n\u0131 \u00f6nler.<\/li>\n
- Performans Art\u0131\u015f\u0131:<\/strong> Veri ak\u0131\u015f\u0131n\u0131 e\u015fzamans\u0131z (asenkron) ve s\u00fcrekli bir \u015fekilde i\u015fleyerek G\/\u00c7 (Input\/Output) i\u015flemlerini h\u0131zland\u0131r\u0131r. Bu, \u00f6zellikle dosya okuma\/yazma, a\u011f ileti\u015fimi ve veri d\u00f6n\u00fc\u015ft\u00fcrme gibi G\/\u00c7 yo\u011fun operasyonlarda uygulaman\u0131z\u0131n yan\u0131t verme yetene\u011fini \u00f6nemli \u00f6l\u00e7\u00fcde art\u0131r\u0131r.<\/li>\n
- \u00d6l\u00e7eklenebilirlik:<\/strong> D\u00fc\u015f\u00fck bellek t\u00fcketimi ve y\u00fcksek performans, uygulaman\u0131z\u0131n daha fazla kullan\u0131c\u0131y\u0131 veya daha b\u00fcy\u00fck veri hacimlerini daha az kaynakla i\u015flemesine olanak tan\u0131r. Bu, uygulaman\u0131z\u0131n yatay ve dikey \u00f6l\u00e7eklenebilirli\u011fini do\u011frudan destekler.<\/li>\n
- Esneklik ve Mod\u00fclerlik:<\/strong> Stream'lerin
.pipe()<\/code> metodu ve farkl\u0131 Stream t\u00fcrleri (Readable, Writable, Duplex, Transform) sayesinde, karma\u015f\u0131k veri i\u015fleme boru hatlar\u0131 olu\u015fturmak kolayla\u015f\u0131r. Her Stream, belirli bir g\u00f6revi yerine getiren mod\u00fcler bir birim olarak i\u015flev g\u00f6r\u00fcr, bu da kodun okunabilirli\u011fini ve bak\u0131m\u0131n\u0131 kolayla\u015ft\u0131r\u0131r.<\/li>\n- Backpressure Y\u00f6netimi:<\/strong> Stream'ler, veri ak\u0131\u015f\u0131 h\u0131zlar\u0131 aras\u0131ndaki farklardan kaynaklanan \"backpressure\" sorununu otomatik veya manuel olarak y\u00f6netmek i\u00e7in mekanizmalar sunar. Bu, sistemin a\u015f\u0131r\u0131 y\u00fcklenmesini ve bellek s\u0131z\u0131nt\u0131lar\u0131n\u0131 engeller.<\/li>\n
- \u0130kili Veri \u0130\u015fleme Yetene\u011fi:<\/strong> Buffer'lar, JavaScript'in yerle\u015fik string ve number t\u00fcrlerinin \u00f6tesine ge\u00e7erek ham ikili veriyle (\u00f6rne\u011fin, resimler, videolar, a\u011f paketleri) do\u011frudan ve verimli bir \u015fekilde \u00e7al\u0131\u015fmay\u0131 m\u00fcmk\u00fcn k\u0131lar.<\/li>\n<\/ul>\n
Sonu\u00e7 olarak, Node.js Stream ve Buffer, modern veri i\u015fleme paradigmalar\u0131n\u0131n temel ta\u015flar\u0131d\u0131r. Bu kavramlar\u0131 derinlemesine anlamak ve uygulamalar\u0131n\u0131za entegre etmek, geli\u015ftiricilerin daha sa\u011flam, daha performansl\u0131 ve bellek a\u00e7\u0131s\u0131ndan daha verimli Node.js uygulamalar\u0131 olu\u015fturmas\u0131n\u0131n anahtar\u0131d\u0131r. \u0130ster b\u00fcy\u00fck bir dosya kopyal\u0131yor, ister ger\u00e7ek zamanl\u0131 bir medya ak\u0131\u015f\u0131 sunuyor, ister karma\u015f\u0131k bir veri d\u00f6n\u00fc\u015f\u00fcm\u00fc yap\u0131yorken olun, Stream ve Buffer'lar i\u015finizi \u00e7ok daha kolay ve etkili hale getirecektir. Bu bilgileri uygulamalar\u0131n\u0131za yans\u0131tt\u0131\u011f\u0131n\u0131zda, Node.js projelerinizin bir sonraki seviyeye ta\u015f\u0131nd\u0131\u011f\u0131n\u0131 g\u00f6receksiniz.<\/p>\n
S\u0131k\u00e7a Sorulan Sorular<\/h3>\n\n- \n Buffer nedir ve neden Stream'lerden \u00f6nce \u00f6\u011frenilmelidir?<\/strong><\/p>\n
Buffer, Node.js'te ham ikili veriyi (byte'lar) do\u011frudan bellekte tutan sabit boyutlu bir yap\u0131d\u0131r. Stream'ler ise bu Buffer par\u00e7alar\u0131n\u0131 ak\u0131\u015f halinde i\u015flemek i\u00e7in soyut bir aray\u00fczd\u00fcr. Buffer'lar\u0131 anlamak, Stream'lerin 'data' olaylar\u0131yla gelen veri par\u00e7alar\u0131n\u0131n (chunk'lar\u0131n) asl\u0131nda Buffer nesneleri oldu\u011funu kavramak i\u00e7in temeldir. Yani Buffer, Stream'lerin ta\u015f\u0131d\u0131\u011f\u0131 verinin fiziksel format\u0131d\u0131r, bu y\u00fczden \u00f6ncelikle anla\u015f\u0131lmas\u0131 \u00f6nemlidir.<\/p>\n<\/li>\n
- \n
.pipe()<\/code> metodunun en b\u00fcy\u00fck avantaj\u0131 nedir?<\/strong><\/p>\n.pipe()<\/code> metodunun en b\u00fcy\u00fck avantaj\u0131, bir Readable Stream'in \u00e7\u0131kt\u0131s\u0131n\u0131 do\u011frudan bir Writable Stream'in girdisine ba\u011flarken, backpressure (geri bas\u0131n\u00e7) y\u00f6netimini otomatik olarak ele almas\u0131d\u0131r. Bu, veri ak\u0131\u015f\u0131n\u0131n h\u0131z\u0131n\u0131 dengeleyerek bellek ta\u015fmalar\u0131n\u0131 \u00f6nler ve geli\u015ftiricinin manuel ak\u0131\u015f kontrol\u00fcyle u\u011fra\u015fmas\u0131n\u0131 engeller, b\u00f6ylece daha temiz ve verimli kod yaz\u0131lmas\u0131n\u0131 sa\u011flar.<\/p>\n<\/li>\n- \n Stream'ler sadece dosya i\u015flemleri i\u00e7in mi kullan\u0131l\u0131r?<\/strong><\/p>\n
Hay\u0131r, Stream'ler \u00e7ok daha geni\u015f bir kullan\u0131m alan\u0131na sahiptir. Dosya i\u015flemleri (okuma\/yazma) en yayg\u0131n kullan\u0131m senaryolar\u0131ndan biri olsa da, a\u011f ileti\u015fimi (HTTP istek\/yan\u0131tlar\u0131, TCP soketleri), veri s\u0131k\u0131\u015ft\u0131rma\/\u015fifreleme, ger\u00e7ek zamanl\u0131 veri ak\u0131\u015flar\u0131 (\u00f6rne\u011fin, WebSockets), ve hatta \u00fc\u00e7\u00fcnc\u00fc taraf k\u00fct\u00fcphanelerde (\u00f6rne\u011fin, veritaban\u0131 s\u00fcr\u00fcc\u00fcleri, i\u015fleme boru hatlar\u0131) de yo\u011fun olarak kullan\u0131l\u0131rlar. Stream'ler, herhangi bir veri kayna\u011f\u0131n\u0131n veya hedefinin \"ak\u0131\u015f\" prensibiyle ele al\u0131nabilece\u011fi her yerde de\u011ferlidir.<\/p>\n<\/li>\n
- \n
highWaterMark<\/code> de\u011feri neyi ifade eder ve nas\u0131l ayarlanmal\u0131d\u0131r?<\/strong><\/p>\nhighWaterMark<\/code>, bir Stream'in dahili Buffer'\u0131nda tutabilece\u011fi veri miktar\u0131n\u0131 (byte cinsinden) belirleyen bir e\u015fiktir. Readable Stream'ler i\u00e7in, bu e\u015fik a\u015f\u0131ld\u0131\u011f\u0131nda .read()<\/code> \u00e7a\u011fr\u0131lar\u0131 durdurulur ve false<\/code> d\u00f6ner. Writable Stream'ler i\u00e7in ise, bu e\u015fik a\u015f\u0131ld\u0131\u011f\u0131nda .write()<\/code> \u00e7a\u011fr\u0131lar\u0131 false<\/code> d\u00f6ner ve ak\u0131\u015f duraklat\u0131l\u0131r. Varsay\u0131lan de\u011fer Readable Stream'ler i\u00e7in 16KB, Writable Stream'ler i\u00e7in 16KB'd\u0131r. Performans ve bellek kullan\u0131m\u0131 aras\u0131nda bir denge kurmak i\u00e7in ayarlan\u0131r; daha y\u00fcksek bir de\u011fer, daha az duraklama\/ba\u015flatma anlam\u0131na gelir ancak daha fazla bellek t\u00fcketir, daha d\u00fc\u015f\u00fck bir de\u011fer ise tersini.<\/p>\n<\/li>\n- \n Transform Stream ile Duplex Stream aras\u0131ndaki temel fark nedir?<\/strong><\/p>\n
Duplex Stream'ler hem okunabilir hem de yaz\u0131labilirken, Transform Stream'ler \u00f6zel bir Duplex Stream t\u00fcr\u00fcd\u00fcr. Temel fark, bir Transform Stream'in yaz\u0131lan veriyi d\u00f6n\u00fc\u015ft\u00fcr\u00fcp sonra bu d\u00f6n\u00fc\u015ft\u00fcr\u00fclm\u00fc\u015f veriyi okuma amac\u0131 ta\u015f\u0131mas\u0131d\u0131r. Yani, girdi verisi ile \u00e7\u0131kt\u0131 verisi aras\u0131nda do\u011frudan bir ili\u015fki ve bir d\u00f6n\u00fc\u015f\u00fcm mekanizmas\u0131 bulunur. Duplex Stream'ler ise girdi ve \u00e7\u0131kt\u0131 verisinin ili\u015fkili olmas\u0131 zorunlu olmayan, tamamen ayr\u0131 iki Stream gibi davranabilirler (\u00f6rne\u011fin, bir TCP soketi, gelen ve giden veriyi ba\u011f\u0131ms\u0131z olarak i\u015fleyebilir).<\/p>\n<\/li>\n<\/ul>\n
<\/body><\/p>\n","protected":false},"excerpt":{"rendered":"Node.js uygulamalar\u0131n\u0131zda b\u00fcy\u00fck veri k\u00fcmeleriyle \u00e7al\u0131\u015f\u0131rken performans sorunlar\u0131 m\u0131 ya\u015f\u0131yorsunuz? Bellek t\u00fcketimini optimize etmek ve G\/\u00c7 (Input\/Output) i\u015flemlerini…","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"csco_page_header_type":"","csco_page_load_nextpost":"","csco_page_subscribe_form":"","csco_page_contact_form":"","footnotes":""},"categories":[136],"tags":[],"class_list":{"0":"post-33059","1":"post","2":"type-post","3":"status-publish","4":"format-standard","6":"category-node-js","7":"cs-entry","8":"cs-video-wrap"},"yoast_head":"\n
Node.js Stream ve Buffer: Veri \u0130\u015flemede Ustala\u015f\u0131n<\/title>\n<meta name=\"description\" content=\"Node.js uygulamalar\u0131n\u0131zda b\u00fcy\u00fck veri k\u00fcmeleriyle \u00e7al\u0131\u015f\u0131rken performans sorunlar\u0131 m\u0131 ya\u015f\u0131yorsunuz? Bellek t\u00fcketimini optimize etmek ve G\/\u00c7 (Input\/Output) i\u015flemlerini daha verimli hale getirmek i\u00e7in Stream ve Buffer kavramlar\u0131 kritik \u00f6neme sahiptir. Bu makale, Node.js'in bu g\u00fc\u00e7l\u00fc ara\u00e7lar\u0131n\u0131 temelden ileri seviyeye kadar ke\u015ffederek, uygulamalar\u0131n\u0131zda veri ak\u0131\u015f\u0131n\u0131 nas\u0131l ustal\u0131kla y\u00f6netece\u011finizi ad\u0131m ad\u0131m a\u00e7\u0131klayacakt\u0131r.\" \/>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/fatihsoysal.com\/blog\/node-js-stream-ve-buffer-veri-islemede-ustalasin\/\" \/>\n<meta property=\"og:locale\" content=\"tr_TR\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Node.js Stream ve Buffer: Veri \u0130\u015flemede Ustala\u015f\u0131n\" \/>\n<meta property=\"og:description\" content=\"Node.js uygulamalar\u0131n\u0131zda b\u00fcy\u00fck veri k\u00fcmeleriyle \u00e7al\u0131\u015f\u0131rken performans sorunlar\u0131 m\u0131 ya\u015f\u0131yorsunuz? Bellek t\u00fcketimini optimize etmek ve G\/\u00c7 (Input\/Output) i\u015flemlerini daha verimli hale getirmek i\u00e7in Stream ve Buffer kavramlar\u0131 kritik \u00f6neme sahiptir. Bu makale, Node.js'in bu g\u00fc\u00e7l\u00fc ara\u00e7lar\u0131n\u0131 temelden ileri seviyeye kadar ke\u015ffederek, uygulamalar\u0131n\u0131zda veri ak\u0131\u015f\u0131n\u0131 nas\u0131l ustal\u0131kla y\u00f6netece\u011finizi ad\u0131m ad\u0131m a\u00e7\u0131klayacakt\u0131r.\" \/>\n<meta property=\"og:url\" content=\"https:\/\/fatihsoysal.com\/blog\/node-js-stream-ve-buffer-veri-islemede-ustalasin\/\" \/>\n<meta property=\"og:site_name\" content=\"Kodlar\u0131n Gizemli D\u00fcnyas\u0131\" \/>\n<meta property=\"article:published_time\" content=\"2025-10-29T00:31:23+00:00\" \/>\n<meta name=\"author\" content=\"Fatih Soysal\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:label1\" content=\"Yazan:\" \/>\n\t<meta name=\"twitter:data1\" content=\"Fatih Soysal\" \/>\n\t<meta name=\"twitter:label2\" content=\"Tahmini okuma s\u00fcresi\" \/>\n\t<meta name=\"twitter:data2\" content=\"31 dakika\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\/\/schema.org\",\"@graph\":[{\"@type\":\"Article\",\"@id\":\"https:\/\/fatihsoysal.com\/blog\/node-js-stream-ve-buffer-veri-islemede-ustalasin\/#article\",\"isPartOf\":{\"@id\":\"https:\/\/fatihsoysal.com\/blog\/node-js-stream-ve-buffer-veri-islemede-ustalasin\/\"},\"author\":{\"name\":\"Fatih Soysal\",\"@id\":\"https:\/\/fatihsoysal.com\/blog\/#\/schema\/person\/002a254750921dcfd568a99e48240dd1\"},\"headline\":\"Node.js Stream ve Buffer: Veri \u0130\u015flemede Ustala\u015f\u0131n\",\"datePublished\":\"2025-10-29T00:31:23+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\/\/fatihsoysal.com\/blog\/node-js-stream-ve-buffer-veri-islemede-ustalasin\/\"},\"wordCount\":4702,\"commentCount\":0,\"publisher\":{\"@id\":\"https:\/\/fatihsoysal.com\/blog\/#\/schema\/person\/002a254750921dcfd568a99e48240dd1\"},\"articleSection\":[\"Node.js\"],\"inLanguage\":\"tr\",\"potentialAction\":[{\"@type\":\"CommentAction\",\"name\":\"Comment\",\"target\":[\"https:\/\/fatihsoysal.com\/blog\/node-js-stream-ve-buffer-veri-islemede-ustalasin\/#respond\"]}],\"copyrightYear\":\"2025\",\"copyrightHolder\":{\"@id\":\"https:\/\/fatihsoysal.com\/blog\/#organization\"}},{\"@type\":\"WebPage\",\"@id\":\"https:\/\/fatihsoysal.com\/blog\/node-js-stream-ve-buffer-veri-islemede-ustalasin\/\",\"url\":\"https:\/\/fatihsoysal.com\/blog\/node-js-stream-ve-buffer-veri-islemede-ustalasin\/\",\"name\":\"Node.js Stream ve Buffer: Veri \u0130\u015flemede Ustala\u015f\u0131n\",\"isPartOf\":{\"@id\":\"https:\/\/fatihsoysal.com\/blog\/#website\"},\"datePublished\":\"2025-10-29T00:31:23+00:00\",\"description\":\"Node.js uygulamalar\u0131n\u0131zda b\u00fcy\u00fck veri k\u00fcmeleriyle \u00e7al\u0131\u015f\u0131rken performans sorunlar\u0131 m\u0131 ya\u015f\u0131yorsunuz? Bellek t\u00fcketimini optimize etmek ve G\/\u00c7 (Input\/Output) i\u015flemlerini daha verimli hale getirmek i\u00e7in Stream ve Buffer kavramlar\u0131 kritik \u00f6neme sahiptir. Bu makale, Node.js'in bu g\u00fc\u00e7l\u00fc ara\u00e7lar\u0131n\u0131 temelden ileri seviyeye kadar ke\u015ffederek, uygulamalar\u0131n\u0131zda veri ak\u0131\u015f\u0131n\u0131 nas\u0131l ustal\u0131kla y\u00f6netece\u011finizi ad\u0131m ad\u0131m a\u00e7\u0131klayacakt\u0131r.\",\"breadcrumb\":{\"@id\":\"https:\/\/fatihsoysal.com\/blog\/node-js-stream-ve-buffer-veri-islemede-ustalasin\/#breadcrumb\"},\"inLanguage\":\"tr\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/fatihsoysal.com\/blog\/node-js-stream-ve-buffer-veri-islemede-ustalasin\/\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/fatihsoysal.com\/blog\/node-js-stream-ve-buffer-veri-islemede-ustalasin\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Anasayfa\",\"item\":\"https:\/\/fatihsoysal.com\/blog\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"Node.js Stream ve Buffer: Veri \u0130\u015flemede Ustala\u015f\u0131n\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\/\/fatihsoysal.com\/blog\/#website\",\"url\":\"https:\/\/fatihsoysal.com\/blog\/\",\"name\":\"Fatihsoysal.com\",\"description\":\"Blog - Yaz\u0131l\u0131m D\u00fcnyas\u0131 Tecr\u00fcbelerim\",\"publisher\":{\"@id\":\"https:\/\/fatihsoysal.com\/blog\/#\/schema\/person\/002a254750921dcfd568a99e48240dd1\"},\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\/\/fatihsoysal.com\/blog\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"tr\"},{\"@type\":[\"Person\",\"Organization\"],\"@id\":\"https:\/\/fatihsoysal.com\/blog\/#\/schema\/person\/002a254750921dcfd568a99e48240dd1\",\"name\":\"Fatih Soysal\",\"image\":{\"@type\":\"ImageObject\",\"inLanguage\":\"tr\",\"@id\":\"https:\/\/fatihsoysal.com\/blog\/#\/schema\/person\/image\/\",\"url\":\"https:\/\/fatihsoysal.com\/blog\/wp-content\/uploads\/2024\/04\/cropped-replicate-prediction-3kgg1hgjn5rgp0cf0p5tr0jw7w-1.png\",\"contentUrl\":\"https:\/\/fatihsoysal.com\/blog\/wp-content\/uploads\/2024\/04\/cropped-replicate-prediction-3kgg1hgjn5rgp0cf0p5tr0jw7w-1.png\",\"width\":512,\"height\":512,\"caption\":\"Fatih Soysal\"},\"logo\":{\"@id\":\"https:\/\/fatihsoysal.com\/blog\/#\/schema\/person\/image\/\"},\"description\":\"Kullan\u0131m ve kodlama m\u00fckemmeliyetini odak alan uygulamalar olu\u015fturma deneyimine sahip, profesyonel olarak 15+ y\u0131l \u00fczeri deneyime sahip bir yaz\u0131l\u0131m m\u00fchendisi.\",\"url\":\"https:\/\/fatihsoysal.com\/blog\/author\/fatihsoysal\/\"}]}<\/script>\n<!-- \/ Yoast SEO Premium plugin. -->","yoast_head_json":{"title":"Node.js Stream ve Buffer: Veri \u0130\u015flemede Ustala\u015f\u0131n","description":"Node.js uygulamalar\u0131n\u0131zda b\u00fcy\u00fck veri k\u00fcmeleriyle \u00e7al\u0131\u015f\u0131rken performans sorunlar\u0131 m\u0131 ya\u015f\u0131yorsunuz? Bellek t\u00fcketimini optimize etmek ve G\/\u00c7 (Input\/Output) i\u015flemlerini daha verimli hale getirmek i\u00e7in Stream ve Buffer kavramlar\u0131 kritik \u00f6neme sahiptir. Bu makale, Node.js'in bu g\u00fc\u00e7l\u00fc ara\u00e7lar\u0131n\u0131 temelden ileri seviyeye kadar ke\u015ffederek, uygulamalar\u0131n\u0131zda veri ak\u0131\u015f\u0131n\u0131 nas\u0131l ustal\u0131kla y\u00f6netece\u011finizi ad\u0131m ad\u0131m a\u00e7\u0131klayacakt\u0131r.","robots":{"index":"index","follow":"follow","max-snippet":"max-snippet:-1","max-image-preview":"max-image-preview:large","max-video-preview":"max-video-preview:-1"},"canonical":"https:\/\/fatihsoysal.com\/blog\/node-js-stream-ve-buffer-veri-islemede-ustalasin\/","og_locale":"tr_TR","og_type":"article","og_title":"Node.js Stream ve Buffer: Veri \u0130\u015flemede Ustala\u015f\u0131n","og_description":"Node.js uygulamalar\u0131n\u0131zda b\u00fcy\u00fck veri k\u00fcmeleriyle \u00e7al\u0131\u015f\u0131rken performans sorunlar\u0131 m\u0131 ya\u015f\u0131yorsunuz? Bellek t\u00fcketimini optimize etmek ve G\/\u00c7 (Input\/Output) i\u015flemlerini daha verimli hale getirmek i\u00e7in Stream ve Buffer kavramlar\u0131 kritik \u00f6neme sahiptir. Bu makale, Node.js'in bu g\u00fc\u00e7l\u00fc ara\u00e7lar\u0131n\u0131 temelden ileri seviyeye kadar ke\u015ffederek, uygulamalar\u0131n\u0131zda veri ak\u0131\u015f\u0131n\u0131 nas\u0131l ustal\u0131kla y\u00f6netece\u011finizi ad\u0131m ad\u0131m a\u00e7\u0131klayacakt\u0131r.","og_url":"https:\/\/fatihsoysal.com\/blog\/node-js-stream-ve-buffer-veri-islemede-ustalasin\/","og_site_name":"Kodlar\u0131n Gizemli D\u00fcnyas\u0131","article_published_time":"2025-10-29T00:31:23+00:00","author":"Fatih Soysal","twitter_card":"summary_large_image","twitter_misc":{"Yazan:":"Fatih Soysal","Tahmini okuma s\u00fcresi":"31 dakika"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"Article","@id":"https:\/\/fatihsoysal.com\/blog\/node-js-stream-ve-buffer-veri-islemede-ustalasin\/#article","isPartOf":{"@id":"https:\/\/fatihsoysal.com\/blog\/node-js-stream-ve-buffer-veri-islemede-ustalasin\/"},"author":{"name":"Fatih Soysal","@id":"https:\/\/fatihsoysal.com\/blog\/#\/schema\/person\/002a254750921dcfd568a99e48240dd1"},"headline":"Node.js Stream ve Buffer: Veri \u0130\u015flemede Ustala\u015f\u0131n","datePublished":"2025-10-29T00:31:23+00:00","mainEntityOfPage":{"@id":"https:\/\/fatihsoysal.com\/blog\/node-js-stream-ve-buffer-veri-islemede-ustalasin\/"},"wordCount":4702,"commentCount":0,"publisher":{"@id":"https:\/\/fatihsoysal.com\/blog\/#\/schema\/person\/002a254750921dcfd568a99e48240dd1"},"articleSection":["Node.js"],"inLanguage":"tr","potentialAction":[{"@type":"CommentAction","name":"Comment","target":["https:\/\/fatihsoysal.com\/blog\/node-js-stream-ve-buffer-veri-islemede-ustalasin\/#respond"]}],"copyrightYear":"2025","copyrightHolder":{"@id":"https:\/\/fatihsoysal.com\/blog\/#organization"}},{"@type":"WebPage","@id":"https:\/\/fatihsoysal.com\/blog\/node-js-stream-ve-buffer-veri-islemede-ustalasin\/","url":"https:\/\/fatihsoysal.com\/blog\/node-js-stream-ve-buffer-veri-islemede-ustalasin\/","name":"Node.js Stream ve Buffer: Veri \u0130\u015flemede Ustala\u015f\u0131n","isPartOf":{"@id":"https:\/\/fatihsoysal.com\/blog\/#website"},"datePublished":"2025-10-29T00:31:23+00:00","description":"Node.js uygulamalar\u0131n\u0131zda b\u00fcy\u00fck veri k\u00fcmeleriyle \u00e7al\u0131\u015f\u0131rken performans sorunlar\u0131 m\u0131 ya\u015f\u0131yorsunuz? Bellek t\u00fcketimini optimize etmek ve G\/\u00c7 (Input\/Output) i\u015flemlerini daha verimli hale getirmek i\u00e7in Stream ve Buffer kavramlar\u0131 kritik \u00f6neme sahiptir. Bu makale, Node.js'in bu g\u00fc\u00e7l\u00fc ara\u00e7lar\u0131n\u0131 temelden ileri seviyeye kadar ke\u015ffederek, uygulamalar\u0131n\u0131zda veri ak\u0131\u015f\u0131n\u0131 nas\u0131l ustal\u0131kla y\u00f6netece\u011finizi ad\u0131m ad\u0131m a\u00e7\u0131klayacakt\u0131r.","breadcrumb":{"@id":"https:\/\/fatihsoysal.com\/blog\/node-js-stream-ve-buffer-veri-islemede-ustalasin\/#breadcrumb"},"inLanguage":"tr","potentialAction":[{"@type":"ReadAction","target":["https:\/\/fatihsoysal.com\/blog\/node-js-stream-ve-buffer-veri-islemede-ustalasin\/"]}]},{"@type":"BreadcrumbList","@id":"https:\/\/fatihsoysal.com\/blog\/node-js-stream-ve-buffer-veri-islemede-ustalasin\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Anasayfa","item":"https:\/\/fatihsoysal.com\/blog\/"},{"@type":"ListItem","position":2,"name":"Node.js Stream ve Buffer: Veri \u0130\u015flemede Ustala\u015f\u0131n"}]},{"@type":"WebSite","@id":"https:\/\/fatihsoysal.com\/blog\/#website","url":"https:\/\/fatihsoysal.com\/blog\/","name":"Fatihsoysal.com","description":"Blog - Yaz\u0131l\u0131m D\u00fcnyas\u0131 Tecr\u00fcbelerim","publisher":{"@id":"https:\/\/fatihsoysal.com\/blog\/#\/schema\/person\/002a254750921dcfd568a99e48240dd1"},"potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/fatihsoysal.com\/blog\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"tr"},{"@type":["Person","Organization"],"@id":"https:\/\/fatihsoysal.com\/blog\/#\/schema\/person\/002a254750921dcfd568a99e48240dd1","name":"Fatih Soysal","image":{"@type":"ImageObject","inLanguage":"tr","@id":"https:\/\/fatihsoysal.com\/blog\/#\/schema\/person\/image\/","url":"https:\/\/fatihsoysal.com\/blog\/wp-content\/uploads\/2024\/04\/cropped-replicate-prediction-3kgg1hgjn5rgp0cf0p5tr0jw7w-1.png","contentUrl":"https:\/\/fatihsoysal.com\/blog\/wp-content\/uploads\/2024\/04\/cropped-replicate-prediction-3kgg1hgjn5rgp0cf0p5tr0jw7w-1.png","width":512,"height":512,"caption":"Fatih Soysal"},"logo":{"@id":"https:\/\/fatihsoysal.com\/blog\/#\/schema\/person\/image\/"},"description":"Kullan\u0131m ve kodlama m\u00fckemmeliyetini odak alan uygulamalar olu\u015fturma deneyimine sahip, profesyonel olarak 15+ y\u0131l \u00fczeri deneyime sahip bir yaz\u0131l\u0131m m\u00fchendisi.","url":"https:\/\/fatihsoysal.com\/blog\/author\/fatihsoysal\/"}]}},"yoast_meta":{"yoast_wpseo_title":"","yoast_wpseo_metadesc":"","yoast_wpseo_canonical":""},"amp_enabled":true,"_links":{"self":[{"href":"https:\/\/fatihsoysal.com\/blog\/wp-json\/wp\/v2\/posts\/33059","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/fatihsoysal.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/fatihsoysal.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/fatihsoysal.com\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/fatihsoysal.com\/blog\/wp-json\/wp\/v2\/comments?post=33059"}],"version-history":[{"count":0,"href":"https:\/\/fatihsoysal.com\/blog\/wp-json\/wp\/v2\/posts\/33059\/revisions"}],"wp:attachment":[{"href":"https:\/\/fatihsoysal.com\/blog\/wp-json\/wp\/v2\/media?parent=33059"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/fatihsoysal.com\/blog\/wp-json\/wp\/v2\/categories?post=33059"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/fatihsoysal.com\/blog\/wp-json\/wp\/v2\/tags?post=33059"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}