Go kullanarak mevcut bir veritaban\u0131ndan veya s\u0131f\u0131rdan, saniyeler i\u00e7inde, y\u00fcksek performansl\u0131 ve g\u00fcvenli REST API’lar nas\u0131l olu\u015fturulur? Ad\u0131m ad\u0131m rehberimizle ke\u015ffedin. G\u00fcn\u00fcm\u00fcz\u00fcn rekabet\u00e7i dijital d\u00fcnyas\u0131nda, h\u0131zl\u0131 ve \u00f6l\u00e7eklenebilir web servisleri geli\u015ftirmek, her yaz\u0131l\u0131m projesinin temel ta\u015flar\u0131ndan biridir. Kullan\u0131c\u0131 beklentileri her ge\u00e7en g\u00fcn artarken, geli\u015ftiricilerin \u00fcretim kalitesinde API’lar\u0131 k\u0131sa s\u00fcrede hayata ge\u00e7irmesi kritik \u00f6nem ta\u015f\u0131yor. \u0130\u015fte tam bu noktada Go (Golang), sundu\u011fu \u00fcst\u00fcn performans, e\u015fzamanl\u0131l\u0131k yetenekleri ve basit s\u00f6zdizimi ile \u00f6n plana \u00e7\u0131k\u0131yor. \u00d6zellikle mikroservis mimarileri ve y\u00fcksek trafikli sistemler i\u00e7in ideal bir tercih olan Go, geli\u015ftirme s\u00fcre\u00e7lerini h\u0131zland\u0131r\u0131rken, ayn\u0131 zamanda g\u00fcvenilir ve s\u00fcrd\u00fcr\u00fclebilir \u00e7\u00f6z\u00fcmler sunar.<\/p>\n
Peki, bu kadar iddial\u0131 bir ba\u015fl\u0131\u011f\u0131 nas\u0131l ger\u00e7ekle\u015ftirebiliriz? Mevcut bir veritaban\u0131n\u0131z varsa, bu veritaban\u0131n\u0131n \u00fczerine an\u0131nda bir API katman\u0131 in\u015fa etmek, i\u015f s\u00fcre\u00e7lerinizi otomatize etmek ve yeni uygulamalara g\u00fc\u00e7 vermek i\u00e7in paha bi\u00e7ilmezdir. Ya da tamamen s\u0131f\u0131rdan ba\u015flay\u0131p, g\u00fc\u00e7l\u00fc bir mimariyle gelece\u011fe d\u00f6n\u00fck bir API tasarlamak isteyebilirsiniz. Her iki senaryoda da Go’nun sundu\u011fu ara\u00e7lar ve ekosistem, size inan\u0131lmaz bir h\u0131z ve esneklik sa\u011flar. Geleneksel dillerde haftalar s\u00fcrebilecek bir geli\u015ftirme s\u00fcrecini, do\u011fru ara\u00e7lar ve yakla\u015f\u0131mlarla Go’da birka\u00e7 saat hatta saniyeler i\u00e7inde tamamlaman\u0131n yollar\u0131n\u0131 bu makalede derinlemesine inceleyece\u011fiz. Bu rehber, ister deneyimli bir Go geli\u015ftiricisi olun, ister Go d\u00fcnyas\u0131na yeni ad\u0131m atan biri, herkese de\u011ferli bilgiler sunarak, projelerinizi bir \u00fcst seviyeye ta\u015f\u0131man\u0131za yard\u0131mc\u0131 olmay\u0131 hedefliyor.<\/p>\n
G\u00fcn\u00fcm\u00fczde mobil uygulamalardan web aray\u00fczlerine, IoT cihazlar\u0131ndan arka plan servislerine kadar her yerde veri al\u0131\u015fveri\u015fi REST API’lar \u00fczerinden yap\u0131lmaktad\u0131r. Bu nedenle, geli\u015ftirece\u011fimiz API’lar\u0131n sadece i\u015flevsel olmas\u0131 de\u011fil, ayn\u0131 zamanda y\u00fcksek performansl\u0131, g\u00fcvenli ve kolayca y\u00f6netilebilir olmas\u0131 da gerekir. Go’nun derlenmi\u015f bir dil olmas\u0131, \u00e7al\u0131\u015fma zaman\u0131 performans\u0131n\u0131 art\u0131r\u0131rken, garbage collector’\u0131n\u0131n optimizasyonu ve hafif goroutinleri sayesinde e\u015fzamanl\u0131 i\u015flemleri \u00e7ok daha verimli bir \u015fekilde y\u00f6netmesini sa\u011flar. Bu \u00f6zellikler, \u00f6zellikle anl\u0131k y\u00fcz binlerce iste\u011fi kar\u015f\u0131lamas\u0131 gereken API’lar i\u00e7in Go’yu vazge\u00e7ilmez bir se\u00e7enek haline getirir. Ayr\u0131ca, Go’nun g\u00fc\u00e7l\u00fc standart k\u00fct\u00fcphanesi, harici ba\u011f\u0131ml\u0131l\u0131klara olan ihtiyac\u0131 azaltarak, hem geli\u015ftirme s\u00fcrecini basitle\u015ftirir hem de nihai uygulaman\u0131n boyutunu k\u00fc\u00e7\u00fclt\u00fcr. T\u00fcm bu avantajlar g\u00f6z \u00f6n\u00fcne al\u0131nd\u0131\u011f\u0131nda, Go ile h\u0131zl\u0131 ve \u00fcretim kalitesinde REST API geli\u015ftirme yetene\u011fi, her modern yaz\u0131l\u0131m geli\u015ftiricisi i\u00e7in olmazsa olmaz bir beceridir. Bu makalede ele alaca\u011f\u0131m\u0131z pratik \u00f6rnekler ve derinlemesine teknik analizler sayesinde, siz de bu yetene\u011fi kazanacak ve projelerinizi h\u0131zla hayata ge\u00e7irebileceksiniz.<\/p>\n
REST (Representational State Transfer) API’lar, web servislerinin birbiriyle ileti\u015fim kurmas\u0131n\u0131 sa\u011flayan mimari bir stilidir. Temel olarak, HTTP protokol\u00fc \u00fczerinden veri al\u0131\u015fveri\u015fi yaparak, kaynaklara (\u00f6rne\u011fin kullan\u0131c\u0131lar, \u00fcr\u00fcnler) URI (Uniform Resource Identifier) arac\u0131l\u0131\u011f\u0131yla eri\u015fim sa\u011flar. Bir RESTful API, durum bilgisi olmayan (stateless) yap\u0131s\u0131yla her iste\u011fin ba\u011f\u0131ms\u0131z olarak i\u015flenmesini g\u00fcvence alt\u0131na al\u0131r. Bu da API’lar\u0131n \u00f6l\u00e7eklenebilirli\u011fini art\u0131r\u0131r ve sunucu taraf\u0131nda oturum bilgisi tutma y\u00fck\u00fcn\u00fc azalt\u0131r. Genellikle JSON (JavaScript Object Notation) format\u0131nda veri d\u00f6nerler, bu da onlar\u0131 hem insan hem de makine taraf\u0131ndan kolayca okunabilir ve i\u015flenebilir k\u0131lar. HTTP metodlar\u0131 (GET, POST, PUT, DELETE) kullan\u0131larak CRUD (Create, Read, Update, Delete) i\u015flemleri ger\u00e7ekle\u015ftirilir. \u00d6rne\u011fin, bir kayna\u011f\u0131 almak i\u00e7in GET, yeni bir kaynak olu\u015fturmak i\u00e7in POST, mevcut bir kayna\u011f\u0131 g\u00fcncellemek i\u00e7in PUT ve bir kayna\u011f\u0131 silmek i\u00e7in DELETE metodu kullan\u0131l\u0131r.<\/p>\n
Go (Golang) ise Google taraf\u0131ndan geli\u015ftirilmi\u015f, derlenmi\u015f, statik tipli bir programlama dilidir. Performans, basitlik ve e\u015fzamanl\u0131l\u0131k odakl\u0131 tasar\u0131m\u0131yla dikkat \u00e7eker. Go’nun \u00f6zellikle web servisleri ve a\u011f uygulamalar\u0131 geli\u015ftirmede parlamas\u0131n\u0131n ba\u015fl\u0131ca nedenleri \u015funlard\u0131r:<\/p>\n
REST API geli\u015ftirirken Go kullanmak, y\u00fcksek trafikli uygulamalar i\u00e7in sa\u011flam, h\u0131zl\u0131 ve bak\u0131m\u0131 kolay bir temel olu\u015fturman\u0131z\u0131 sa\u011flar. HTTP paketini kullanarak basit bir web sunucusu kurmak bile olduk\u00e7a kolayd\u0131r:<\/p>\n
\npackage main\n\nimport (\n\t\"fmt\"\n\t\"net\/http\"\n)\n\nfunc helloHandler(w http.ResponseWriter, r *http.Request) {\n\tfmt.Fprintf(w, \"Merhaba, Go API!\")\n}\n\nfunc main() {\n\thttp.HandleFunc(\"\/\", helloHandler)\n\tfmt.Println(\"Sunucu 8080 portunda dinlemede...\")\n\thttp.ListenAndServe(\":8080\", nil)\n}\n <\/pre>\n<\/code><\/p>\n
Bu basit \u00f6rnek, Go'nun standart k\u00fct\u00fcphanesiyle bile bir HTTP sunucusunu ne kadar kolay kurabilece\u011finizi g\u00f6steriyor. \u0130\u015fte bu temelden yola \u00e7\u0131karak, daha karma\u015f\u0131k ve \u00fcretim kalitesinde REST API'lar\u0131 in\u015fa edebiliriz. Bu b\u00f6l\u00fcm, Go'nun ve REST'in temel felsefesini anlaman\u0131z i\u00e7in bir ba\u015flang\u0131\u00e7 noktas\u0131 sunarken, ilerleyen b\u00f6l\u00fcmlerde bu bilgileri pratik uygulamalara d\u00f6n\u00fc\u015ft\u00fcrece\u011fiz. Unutmay\u0131n, iyi bir API tasar\u0131m\u0131, sadece kod yazmakla de\u011fil, ayn\u0131 zamanda prensiplere ba\u011fl\u0131 kalmakla da ilgilidir. Go'nun sa\u011flad\u0131\u011f\u0131 ara\u00e7larla, bu prensipleri kolayca uygulayabilirsiniz.<\/p>\n
S\u0131f\u0131rdan Bir Go REST API'\u0131 Nas\u0131l Olu\u015fturulur? (Vaka Analizi: Basit CRUD Servisi)<\/h2>\n
\u015eimdiye kadar REST API ve Go'nun temel kavramlar\u0131n\u0131 \u00f6\u011frendik. Art\u0131k kollar\u0131m\u0131z\u0131 s\u0131vama ve s\u0131f\u0131rdan, ad\u0131m ad\u0131m bir Go REST API'\u0131 olu\u015fturma zaman\u0131. Bu b\u00f6l\u00fcmde, bir \"\u00dcr\u00fcn Y\u00f6netim Sistemi\" i\u00e7in basit bir CRUD (Create, Read, Update, Delete) servisi geli\u015ftirece\u011fiz. Bu vaka analizi, Go'nun standart k\u00fct\u00fcphanesi ve pop\u00fcler \u00fc\u00e7\u00fcnc\u00fc parti paketlerle nas\u0131l \u00e7al\u0131\u015ft\u0131\u011f\u0131n\u0131 anlaman\u0131za yard\u0131mc\u0131 olacak.<\/p>\n
Temel HTTP Sunucu Kurulumu ve Router Se\u00e7imi<\/h3>\n
Her Go web servisi, temelde bir HTTP sunucusu ile ba\u015flar. Go'nun net\/http<\/code> paketi, bu konuda son derece yeteneklidir. Ancak, daha karma\u015f\u0131k y\u00f6nlendirme (routing) ihtiya\u00e7lar\u0131 i\u00e7in genellikle \u00fc\u00e7\u00fcnc\u00fc taraf bir router k\u00fct\u00fcphanesi kullan\u0131l\u0131r. Piyasadaki pop\u00fcler se\u00e7eneklerden biri olan gorilla\/mux<\/code><\/a>, RESTful API'lar i\u00e7in dinamik URL parametrelerini ve HTTP metodlar\u0131n\u0131 y\u00f6netmede olduk\u00e7a g\u00fc\u00e7l\u00fcd\u00fcr. \u0130lk ad\u0131m olarak projemizi olu\u015ftural\u0131m ve gerekli paketi indirelim:<\/p>\n\nmkdir product-api\ncd product-api\ngo mod init product-api\ngo get github.com\/gorilla\/mux\n <\/pre>\n<\/code><\/p>\n
\u015eimdi main.go<\/code> dosyam\u0131z\u0131 olu\u015ftural\u0131m ve temel sunucu yap\u0131s\u0131n\u0131 kural\u0131m:<\/p>\n\npackage main\n\nimport (\n\t\"encoding\/json\"\n\t\"fmt\"\n\t\"log\"\n\t\"net\/http\"\n\n\t\"github.com\/gorilla\/mux\"\n)\n\n\/\/ Product modelimizi tan\u0131mlayal\u0131m\ntype Product struct {\n\tID string json:\"id\"<\/code>\n\tName string json:\"name\"<\/code>\n\tPrice float64 json:\"price\"<\/code>\n}\n\n\/\/ Basit bir \u00fcr\u00fcn deposu (\u015fimdilik bellek i\u00e7i)\nvar products []Product\n\nfunc main() {\n\t\/\/ Ba\u015flang\u0131\u00e7 verileri\n\tproducts = append(products, Product{ID: \"1\", Name: \"Laptop\", Price: 1200.00})\n\tproducts = append(products, Product{ID: \"2\", Name: \"Mouse\", Price: 25.50})\n\n\trouter := mux.NewRouter()\n\n\t\/\/ API rotalar\u0131m\u0131z\u0131 tan\u0131mlayal\u0131m\n\trouter.HandleFunc(\"\/products\", getProducts).Methods(\"GET\")\n\trouter.HandleFunc(\"\/products\/{id}\", getProduct).Methods(\"GET\")\n\trouter.HandleFunc(\"\/products\", createProduct).Methods(\"POST\")\n\trouter.HandleFunc(\"\/products\/{id}\", updateProduct).Methods(\"PUT\")\n\trouter.HandleFunc(\"\/products\/{id}\", deleteProduct).Methods(\"DELETE\")\n\n\tfmt.Println(\"Sunucu 8000 portunda dinlemede...\")\n\tlog.Fatal(http.ListenAndServe(\":8000\", router))\n}\n <\/pre>\n<\/code><\/p>\n
Yukar\u0131daki kodda Product<\/code> ad\u0131nda bir struct tan\u0131mlad\u0131k ve json:\"...\"<\/code> etiketleriyle JSON marshalling\/unmarshalling i\u015flemlerini kolayla\u015ft\u0131rd\u0131k. Ard\u0131ndan gorilla\/mux<\/code> kullanarak farkl\u0131 HTTP metodlar\u0131 ve URL yollar\u0131 i\u00e7in handler fonksiyonlar\u0131m\u0131z\u0131 belirttik. \u015eimdi bu handler fonksiyonlar\u0131n\u0131 implemente edelim.<\/p>\nHandler Fonksiyonlar\u0131: CRUD \u0130\u015flemleri<\/h3>\n
Her bir HTTP metodu ve yoluna kar\u015f\u0131l\u0131k gelen handler fonksiyonlar\u0131, API'm\u0131z\u0131n i\u015f mant\u0131\u011f\u0131n\u0131 i\u00e7erecek. Bu fonksiyonlar genellikle http.ResponseWriter<\/code> ve *http.Request<\/code> parametrelerini al\u0131r:<\/p>\n\n\/\/ T\u00fcm \u00fcr\u00fcnleri listeler\nfunc getProducts(w http.ResponseWriter, r *http.Request) {\n\tw.Header().Set(\"Content-Type\", \"application\/json\")\n\tjson.NewEncoder(w).Encode(products)\n}\n\n\/\/ Belirli bir \u00fcr\u00fcn\u00fc ID'sine g\u00f6re getirir\nfunc getProduct(w http.ResponseWriter, r *http.Request) {\n\tw.Header().Set(\"Content-Type\", \"application\/json\")\n\tparams := mux.Vars(r) \/\/ URL parametrelerini al\u0131r (\u00f6rn: {id})\n\tfor _, item := range products {\n\t\tif item.ID == params[\"id\"] {\n\t\t\tjson.NewEncoder(w).Encode(item)\n\t\t\treturn\n\t\t}\n\t}\n\thttp.Error(w, \"\u00dcr\u00fcn bulunamad\u0131\", http.StatusNotFound)\n}\n\n\/\/ Yeni bir \u00fcr\u00fcn olu\u015fturur\nfunc createProduct(w http.ResponseWriter, r *http.Request) {\n\tw.Header().Set(\"Content-Type\", \"application\/json\")\n\tvar product Product\n\t_ = json.NewDecoder(r.Body).Decode(&product) \/\/ \u0130stek g\u00f6vdesinden JSON'\u0131 ayr\u0131\u015ft\u0131r\u0131r\n\t\/\/ Basit bir ID atamas\u0131 yapal\u0131m (ger\u00e7ek uygulamada UUID veya veritaban\u0131 ID'si kullan\u0131l\u0131r)\n\tproduct.ID = fmt.Sprintf(\"%d\", len(products)+1) \n\tproducts = append(products, product)\n\tjson.NewEncoder(w).Encode(product)\n\tw.WriteHeader(http.StatusCreated) \/\/ HTTP 201 Created d\u00f6ner\n}\n\n\/\/ Mevcut bir \u00fcr\u00fcn\u00fc g\u00fcnceller\nfunc updateProduct(w http.ResponseWriter, r *http.Request) {\n\tw.Header().Set(\"Content-Type\", \"application\/json\")\n\tparams := mux.Vars(r)\n\tvar updatedProduct Product\n\t_ = json.NewDecoder(r.Body).Decode(&updatedProduct)\n\n\tfor index, item := range products {\n\t\tif item.ID == params[\"id\"] {\n\t\t\tproducts[index] = updatedProduct\n\t\t\tproducts[index].ID = params[\"id\"] \/\/ ID'yi koru\n\t\t\tjson.NewEncoder(w).Encode(products[index])\n\t\t\treturn\n\t\t}\n\t}\n\thttp.Error(w, \"\u00dcr\u00fcn bulunamad\u0131\", http.StatusNotFound)\n}\n\n\/\/ Bir \u00fcr\u00fcn\u00fc siler\nfunc deleteProduct(w http.ResponseWriter, r *http.Request) {\n\tw.Header().Set(\"Content-Type\", \"application\/json\")\n\tparams := mux.Vars(r)\n\tfor index, item := range products {\n\t\tif item.ID == params[\"id\"] {\n\t\t\tproducts = append(products[:index], products[index+1:]...) \/\/ \u00dcr\u00fcn\u00fc dilimden sil\n\t\t\tbreak\n\t\t}\n\t}\n\tw.WriteHeader(http.StatusNoContent) \/\/ HTTP 204 No Content d\u00f6ner\n}\n <\/pre>\n<\/code><\/p>\n
Bu \u00f6rnekte, \u00fcr\u00fcn verilerini bellek i\u00e7i bir dilim (slice) olarak tuttuk. Ger\u00e7ek bir \u00fcretim uygulamas\u0131nda, bu verilerin bir veritaban\u0131nda (PostgreSQL, MySQL, MongoDB vb.) kal\u0131c\u0131 olarak saklanmas\u0131 gerekir. Bir sonraki b\u00f6l\u00fcmde, Go ile veritaban\u0131 entegrasyonuna odaklanaca\u011f\u0131z. Bu bellek i\u00e7i depolama, API mant\u0131\u011f\u0131n\u0131 h\u0131zla test etmek i\u00e7in yeterlidir. API'm\u0131z \u015fu anda basit CRUD i\u015flemlerini yapabilen bir yap\u0131ya sahip. Her bir handler fonksiyonu, HTTP isteklerini i\u015fler, gerekli verileri ayr\u0131\u015ft\u0131r\u0131r ve JSON format\u0131nda yan\u0131t d\u00f6nd\u00fcr\u00fcr. Hata durumlar\u0131nda uygun HTTP durum kodlar\u0131 ile geri bildirim sa\u011flar\u0131z (\u00f6rn: 404 Not Found, 201 Created, 204 No Content).<\/p>\n
Uzman \u0130pucu: Bellek i\u00e7i depolama yerine, testlerinizde veya h\u0131zl\u0131 prototiplemelerde SQLite gibi hafif, dosya tabanl\u0131 bir veritaban\u0131 kullanmak, API'n\u0131z\u0131n kal\u0131c\u0131l\u0131k davran\u0131\u015f\u0131n\u0131 test etmek i\u00e7in daha iyi bir se\u00e7enek olabilir.<\/div>\nBu basit yap\u0131, Go ile REST API geli\u015ftirmenin temelini olu\u015fturur. Ancak, \u00fcretim seviyesinde bir API i\u00e7in daha bir\u00e7ok fakt\u00f6r\u00fc g\u00f6z \u00f6n\u00fcnde bulundurmam\u0131z gerekecek: veritaban\u0131 ba\u011flant\u0131s\u0131, hata y\u00f6netimi, do\u011frulama, kimlik do\u011frulama, yetkilendirme ve performans optimizasyonlar\u0131 gibi. Bu ba\u015flang\u0131\u00e7 noktas\u0131yla, Go'nun ne kadar h\u0131zl\u0131 ve verimli bir \u015fekilde bir API iskeleti olu\u015fturman\u0131za olanak tan\u0131d\u0131\u011f\u0131n\u0131 g\u00f6rm\u00fc\u015f olduk. \u015eimdi bu API'y\u0131 ger\u00e7ek bir veritaban\u0131 ile nas\u0131l entegre edece\u011fimize bakal\u0131m.<\/p>\n
Mevcut Bir Veritaban\u0131n\u0131 Go API'\u0131na Nas\u0131l D\u00f6n\u00fc\u015ft\u00fcr\u00fcrs\u00fcn\u00fcz? (ORM Kullan\u0131m\u0131)<\/h2>\n
\u00d6nceki b\u00f6l\u00fcmde basit bir bellek i\u00e7i CRUD API'\u0131 olu\u015fturduk. Ancak \u00fcretim uygulamalar\u0131nda verilerin kal\u0131c\u0131 olarak depolanmas\u0131 gerekir. Mevcut bir veritaban\u0131n\u0131z varsa, Go API'n\u0131z\u0131 bu veritaban\u0131na ba\u011flamak, h\u0131zl\u0131 bir \u015fekilde bir arka u\u00e7 servisi olu\u015fturman\u0131n en etkili yollar\u0131ndan biridir. Go'da veritabanlar\u0131yla \u00e7al\u0131\u015fmak i\u00e7in \u00e7e\u015fitli yakla\u015f\u0131mlar mevcuttur: standart database\/sql<\/code> paketi do\u011frudan SQL sorgular\u0131 yazman\u0131za olanak tan\u0131rken, ORM (Object-Relational Mapping) k\u00fct\u00fcphaneleri, veritaban\u0131 i\u015flemlerini Go struct'lar\u0131 \u00fczerinden daha nesne odakl\u0131 bir \u015fekilde yapman\u0131z\u0131 sa\u011flar. Bu b\u00f6l\u00fcmde, pop\u00fcler bir Go ORM k\u00fct\u00fcphanesi olan GORM<\/a> kullanarak mevcut bir PostgreSQL veritaban\u0131n\u0131 API'\u0131m\u0131za nas\u0131l entegre edece\u011fimizi inceleyece\u011fiz.<\/p>\nGORM ile Veritaban\u0131 Ba\u011flant\u0131s\u0131 ve Model Tan\u0131mlama<\/h3>\n
\u00d6ncelikle GORM ve PostgreSQL s\u00fcr\u00fcc\u00fcs\u00fcn\u00fc projemize eklememiz gerekiyor:<\/p>\n
\ngo get gorm.io\/gorm\ngo get gorm.io\/driver\/postgres\n <\/pre>\n<\/code><\/p>\n
Varsayal\u0131m ki bir PostgreSQL veritaban\u0131n\u0131zda products<\/code> ad\u0131nda bir tablonuz var. Bu tablo, \u00f6nceki b\u00f6l\u00fcmde tan\u0131mlad\u0131\u011f\u0131m\u0131z Product<\/code> struct'\u0131na benzer s\u00fctunlara sahip olabilir (id<\/code>, name<\/code>, price<\/code>). GORM, bu tabloyu do\u011frudan Go struct'\u0131n\u0131zla e\u015fleyebilir. Ba\u011flant\u0131 ve model tan\u0131mlama i\u015flemini main.go<\/code> dosyam\u0131zda veya ayr\u0131 bir database.go<\/code> dosyas\u0131nda yapabiliriz:<\/p>\n\npackage main\n\nimport (\n\t\"fmt\"\n\t\"log\"\n\t\"net\/http\"\n\t\"os\"\n\n\t\"github.com\/gorilla\/mux\"\n\t\"gorm.io\/driver\/postgres\"\n\t\"gorm.io\/gorm\"\n)\n\n\/\/ Product modelimizi GORM i\u00e7in d\u00fczenleyelim\ntype Product struct {\n\tgorm.Model \/\/ GORM'un ID, CreatedAt, UpdatedAt, DeletedAt gibi alanlar\u0131n\u0131 ekler\n\tName string json:\"name\"<\/code>\n\tPrice float64 json:\"price\"<\/code>\n}\n\nvar DB *gorm.DB \/\/ Veritaban\u0131 ba\u011flant\u0131 nesnesi\n\nfunc initDB() {\n\t\/\/ Veritaban\u0131 ba\u011flant\u0131 dizesi, \u00e7evre de\u011fi\u015fkenlerinden al\u0131nmal\u0131\n\tdsn := os.Getenv(\"DATABASE_URL\")\n\tif dsn == \"\" {\n\t\t\/\/ Varsay\u0131lan ba\u011flant\u0131 dizesi (yerel geli\u015ftirme i\u00e7in)\n\t\tdsn = \"host=localhost user=gouser password=gopass dbname=go_api port=5432 sslmode=disable TimeZone=Europe\/Istanbul\"\n\t}\n\n\tvar err error\n\tDB, err = gorm.Open(postgres.Open(dsn), &gorm.Config{})\n\tif err != nil {\n\t\tlog.Fatalf(\"Veritaban\u0131na ba\u011flan\u0131lamad\u0131: %v\", err)\n\t}\n\n\tfmt.Println(\"Veritaban\u0131 ba\u011flant\u0131s\u0131 ba\u015far\u0131l\u0131!\")\n\n\t\/\/ Tabloyu otomatik olarak migrate et (varsa g\u00fcncelle, yoksa olu\u015ftur)\n\t\/\/ Dikkat: Mevcut veritaban\u0131nda tablo zaten varsa GORM.Model alanlar\u0131n\u0131 ekleyecektir.\n\t\/\/ E\u011fer tablonuzda bu alanlar yoksa, ilk ba\u015fta hata verebilir veya tabloyu de\u011fi\u015ftirebilir.\n\t\/\/ \u00dcretim ortamlar\u0131nda bu ad\u0131m\u0131 dikkatlice y\u00f6netin.\n\terr = DB.AutoMigrate(&Product{})\n\tif err != nil {\n\t\tlog.Fatalf(\"Veritaban\u0131 migration hatas\u0131: %v\", err)\n\t}\n}\n\n\/\/ ... main fonksiyonu ve handler'lar buraya gelecek ...\n <\/pre>\n<\/code><\/p>\n
initDB<\/code> fonksiyonunu main<\/code> fonksiyonumuzdan \u00f6nce \u00e7a\u011f\u0131rarak veritaban\u0131 ba\u011flant\u0131s\u0131n\u0131 kurabiliriz. gorm.Model<\/code>, GORM'un \u00fcr\u00fcn struct'\u0131m\u0131za otomatik olarak ID<\/code>, CreatedAt<\/code>, UpdatedAt<\/code> ve DeletedAt<\/code> alanlar\u0131n\u0131 eklemesini sa\u011flar. AutoMigrate<\/code> fonksiyonu, mevcut veritaban\u0131 \u015femas\u0131n\u0131 Go modelinize g\u00f6re otomatik olarak olu\u015fturur veya g\u00fcnceller. Mevcut bir veritaban\u0131yla \u00e7al\u0131\u015f\u0131rken, AutoMigrate<\/code>'i dikkatli kullanmal\u0131 veya manuel migrasyon dosyalar\u0131 tercih etmelisiniz.<\/p>\nHandler Fonksiyonlar\u0131n\u0131 GORM ile G\u00fcncelleme<\/h3>\n
\u015eimdi \u00f6nceki b\u00f6l\u00fcmde yazd\u0131\u011f\u0131m\u0131z CRUD handler fonksiyonlar\u0131n\u0131, bellek i\u00e7i depolama yerine GORM kullanarak veritaban\u0131 i\u015flemlerini yapacak \u015fekilde g\u00fcncelleyelim:<\/p>\n
\n\/\/ main.go i\u00e7inde, main fonksiyonu:\nfunc main() {\n\tinitDB() \/\/ Veritaban\u0131 ba\u011flant\u0131s\u0131n\u0131 kur\n\n\trouter := mux.NewRouter()\n\n\trouter.HandleFunc(\"\/products\", getProducts).Methods(\"GET\")\n\trouter.HandleFunc(\"\/products\/{id}\", getProduct).Methods(\"GET\")\n\trouter.HandleFunc(\"\/products\", createProduct).Methods(\"POST\")\n\trouter.HandleFunc(\"\/products\/{id}\", updateProduct).Methods(\"PUT\")\n\trouter.HandleFunc(\"\/products\/{id}\", deleteProduct).Methods(\"DELETE\")\n\n\tfmt.Println(\"Sunucu 8000 portunda dinlemede...\")\n\tlog.Fatal(http.ListenAndServe(\":8000\", router))\n}\n\n\/\/ Handler fonksiyonlar\u0131 g\u00fcncellemeleri:\n\n\/\/ T\u00fcm \u00fcr\u00fcnleri listeler\nfunc getProducts(w http.ResponseWriter, r *http.Request) {\n\tw.Header().Set(\"Content-Type\", \"application\/json\")\n\tvar products []Product\n\tDB.Find(&products) \/\/ T\u00fcm \u00fcr\u00fcnleri veritaban\u0131ndan al\n\tjson.NewEncoder(w).Encode(products)\n}\n\n\/\/ Belirli bir \u00fcr\u00fcn\u00fc ID'sine g\u00f6re getirir\nfunc getProduct(w http.ResponseWriter, r *http.Request) {\n\tw.Header().Set(\"Content-Type\", \"application\/json\")\n\tparams := mux.Vars(r)\n\tvar product Product\n\tresult := DB.First(&product, params[\"id\"]) \/\/ ID'ye g\u00f6re \u00fcr\u00fcn\u00fc bul\n\tif result.Error != nil {\n\t\thttp.Error(w, \"\u00dcr\u00fcn bulunamad\u0131\", http.StatusNotFound)\n\t\treturn\n\t}\n\tjson.NewEncoder(w).Encode(product)\n}\n\n\/\/ Yeni bir \u00fcr\u00fcn olu\u015fturur\nfunc createProduct(w http.ResponseWriter, r *http.Request) {\n\tw.Header().Set(\"Content-Type\", \"application\/json\")\n\tvar product Product\n\t_ = json.NewDecoder(r.Body).Decode(&product)\n\tresult := DB.Create(&product) \/\/ Yeni \u00fcr\u00fcn\u00fc veritaban\u0131na kaydet\n\tif result.Error != nil {\n\t\thttp.Error(w, fmt.Sprintf(\"\u00dcr\u00fcn olu\u015fturulurken hata olu\u015ftu: %v\", result.Error), http.StatusInternalServerError)\n\t\treturn\n\t}\n\tjson.NewEncoder(w).Encode(product)\n\tw.WriteHeader(http.StatusCreated)\n}\n\n\/\/ Mevcut bir \u00fcr\u00fcn\u00fc g\u00fcnceller\nfunc updateProduct(w http.ResponseWriter, r *http.Request) {\n\tw.Header().Set(\"Content-Type\", \"application\/json\")\n\tparams := mux.Vars(r)\n\tvar product Product\n\tresult := DB.First(&product, params[\"id\"])\n\tif result.Error != nil {\n\t\thttp.Error(w, \"\u00dcr\u00fcn bulunamad\u0131\", http.StatusNotFound)\n\t\treturn\n\t}\n\n\tvar updatedProduct Product\n\t_ = json.NewDecoder(r.Body).Decode(&updatedProduct)\n\n\t\/\/ Sadece isim ve fiyat alanlar\u0131n\u0131 g\u00fcncelleyelim\n\tproduct.Name = updatedProduct.Name\n\tproduct.Price = updatedProduct.Price\n\n\tDB.Save(&product) \/\/ \u00dcr\u00fcn\u00fc g\u00fcncelle\n\tjson.NewEncoder(w).Encode(product)\n}\n\n\/\/ Bir \u00fcr\u00fcn\u00fc siler\nfunc deleteProduct(w http.ResponseWriter, r *http.Request) {\n\tw.Header().Set(\"Content-Type\", \"application\/json\")\n\tparams := mux.Vars(r)\n\tresult := DB.Delete(&Product{}, params[\"id\"]) \/\/ \u00dcr\u00fcn\u00fc ID'ye g\u00f6re sil\n\tif result.Error != nil {\n\t\thttp.Error(w, fmt.Sprintf(\"\u00dcr\u00fcn silinirken hata olu\u015ftu: %v\", result.Error), http.StatusInternalServerError)\n\t\treturn\n\t}\n\tif result.RowsAffected == 0 {\n\t\thttp.Error(w, \"Silinecek \u00fcr\u00fcn bulunamad\u0131\", http.StatusNotFound)\n\t\treturn\n\t}\n\tw.WriteHeader(http.StatusNoContent)\n}\n <\/pre>\n<\/code><\/p>\n
Art\u0131k API'm\u0131z bellek i\u00e7i depolama yerine PostgreSQL veritaban\u0131m\u0131z\u0131 kullan\u0131yor. GORM, veritaban\u0131 i\u015flemlerini olduk\u00e7a basitle\u015ftirerek SQL sorgular\u0131 yazma ihtiyac\u0131n\u0131 ortadan kald\u0131r\u0131r ve geli\u015ftirme h\u0131z\u0131n\u0131 art\u0131r\u0131r. Bu yakla\u015f\u0131m, mevcut bir veritaban\u0131ndan saniyeler i\u00e7inde API olu\u015fturma hedefine ula\u015fmam\u0131z\u0131 sa\u011fl\u0131yor. \u00d6zellikle karma\u015f\u0131k sorgular veya performans kritik senaryolar i\u00e7in GORM'un geli\u015fmi\u015f \u00f6zelliklerini veya database\/sql<\/code> ile do\u011frudan sorgular\u0131 kullanmay\u0131 d\u00fc\u015f\u00fcnebilirsiniz. Ancak basit CRUD i\u015flemleri i\u00e7in GORM fazlas\u0131yla yeterlidir. Bu sayede, Go ile \u00fcretim kalitesinde bir API'\u0131 mevcut bir veritaban\u0131 \u00fczerine h\u0131zl\u0131ca in\u015fa etme yetene\u011fini kazanm\u0131\u015f oluyorsunuz.<\/p>\n\u00dcretim Kalitesi \u0130\u00e7in \u0130pu\u00e7lar\u0131: Performans, G\u00fcvenlik ve \u00d6l\u00e7eklenebilirlik Nas\u0131l Sa\u011flan\u0131r?<\/h2>\n
Bir REST API'\u0131 olu\u015fturmak ba\u015flang\u0131\u00e7 ad\u0131m\u0131d\u0131r, ancak onu \u00fcretim ortam\u0131nda g\u00fcvenle ve verimli bir \u015fekilde \u00e7al\u0131\u015ft\u0131rmak bamba\u015fka bir konudur. Go'nun do\u011fas\u0131nda var olan performans ve e\u015fzamanl\u0131l\u0131k yetenekleri, bize g\u00fc\u00e7l\u00fc bir temel sunarken, \u00fcretim kalitesinde bir API i\u00e7in ek katmanlar ve dikkatli yakla\u015f\u0131mlar gereklidir. Bu b\u00f6l\u00fcmde, Go API'\u0131n\u0131z\u0131n performans\u0131n\u0131 optimize etmek, g\u00fcvenli\u011fini sa\u011flamak ve \u00f6l\u00e7eklenebilirli\u011fini art\u0131rmak i\u00e7in temel ipu\u00e7lar\u0131n\u0131 ve teknikleri ele alaca\u011f\u0131z.<\/p>\n
API G\u00fcvenli\u011fi: Kimlik Do\u011frulama ve Yetkilendirme (JWT, OAuth)<\/h3>\n
API g\u00fcvenli\u011fi, herhangi bir \u00fcretim uygulamas\u0131 i\u00e7in en kritik unsurlardan biridir. \u0130zinsiz eri\u015fimi engellemek ve hassas verileri korumak esast\u0131r. En yayg\u0131n kullan\u0131lan y\u00f6ntemler aras\u0131nda kimlik do\u011frulama (authentication) ve yetkilendirme (authorization) bulunur:<\/p>\n
\n- Kimlik Do\u011frulama (Authentication):<\/strong> Kullan\u0131c\u0131n\u0131n kimli\u011fini do\u011frular. Yayg\u0131n y\u00f6ntemler aras\u0131nda API Anahtarlar\u0131 (API Keys), Temel Kimlik Do\u011frulama (Basic Auth), OAuth 2.0 ve JWT (JSON Web Tokens) bulunur. Go'da JWT kullan\u0131m\u0131 olduk\u00e7a pop\u00fclerdir. Bir JWT token'\u0131, kullan\u0131c\u0131n\u0131n kimlik bilgilerini g\u00fcvenli bir \u015fekilde ta\u015f\u0131r ve her istekte g\u00f6nderilerek sunucunun kullan\u0131c\u0131n\u0131n kimli\u011fini do\u011frulamas\u0131n\u0131 sa\u011flar.<\/li>\n
- Yetkilendirme (Authorization):<\/strong> Kimli\u011fi do\u011frulanm\u0131\u015f bir kullan\u0131c\u0131n\u0131n belirli bir kayna\u011fa eri\u015fim veya belirli bir i\u015flemi yapma yetkisine sahip olup olmad\u0131\u011f\u0131n\u0131 kontrol eder. \u00d6rne\u011fin, bir \"admin\" kullan\u0131c\u0131s\u0131 t\u00fcm \u00fcr\u00fcnleri silebilirken, \"misafir\" kullan\u0131c\u0131s\u0131 sadece \u00fcr\u00fcnleri g\u00f6r\u00fcnt\u00fcleyebilir. Go'da middleware'ler (ara yaz\u0131l\u0131mlar) kullanarak bu kontrolleri merkezi bir yerde kolayca uygulayabiliriz.<\/li>\n<\/ul>\n
\n\/\/ Basit bir JWT middleware \u00f6rne\u011fi (production kalitesinde de\u011fildir, sadece konsept g\u00f6sterimi)\nfunc JWTMiddleware(next http.Handler) http.Handler {\n\treturn http.HandlerFunc(func(w http.ResponseWriter, r *http.Request) {\n\t\ttokenString := r.Header.Get(\"Authorization\")\n\t\tif tokenString == \"\" {\n\t\t\thttp.Error(w, \"Yetkilendirme token'\u0131 eksik\", http.StatusUnauthorized)\n\t\t\treturn\n\t\t}\n\n\t\t\/\/ Token'\u0131n \"Bearer \" ile ba\u015flad\u0131\u011f\u0131n\u0131 varsayal\u0131m\n\t\tif len(tokenString) > 7 && tokenString[:7] == \"Bearer \" {\n\t\t\ttokenString = tokenString[7:]\n\t\t} else {\n\t\t\thttp.Error(w, \"Ge\u00e7ersiz token format\u0131\", http.StatusUnauthorized)\n\t\t\treturn\n\t\t}\n\n\t\t\/\/ Burada JWT token'\u0131n\u0131 do\u011frula ve parse et\n\t\t\/\/ jwt-go gibi bir k\u00fct\u00fcphane kullanmal\u0131s\u0131n\u0131z:\n\t\t\/\/ token, err := jwt.Parse(tokenString, func(token *jwt.Token) (interface{}, error) {\n\t\t\/\/ \treturn []byte(os.Getenv(\"JWT_SECRET\")), nil\n\t\t\/\/ })\n\n\t\t\/\/ if err != nil || !token.Valid {\n\t\t\/\/ \thttp.Error(w, \"Ge\u00e7ersiz veya s\u00fcresi dolmu\u015f token\", http.StatusUnauthorized)\n\t\t\/\/ \treturn\n\t\t\/\/ }\n\n\t\t\/\/ Ba\u015far\u0131l\u0131 ise sonraki handler'\u0131 \u00e7a\u011f\u0131r\n\t\tnext.ServeHTTP(w, r)\n\t})\n}\n <\/pre>\n<\/code><\/p>\n
Bu middleware'\u0131 gorilla\/mux<\/code> router'\u0131na ekleyerek belirli rotalara uygulayabilirsiniz. Ayr\u0131ca, HTTPS kullan\u0131m\u0131, SQL enjeksiyonu ve XSS sald\u0131r\u0131lar\u0131na kar\u015f\u0131 \u00f6nlemler almak da kritik \u00f6neme sahiptir.<\/p>\nHata Y\u00f6netimi ve Loglama Stratejileri<\/h3>\n
\u00dcretim ortam\u0131nda, hatalar\u0131n do\u011fru bir \u015fekilde ele al\u0131nmas\u0131 ve kaydedilmesi, uygulaman\u0131n sa\u011fl\u0131\u011f\u0131n\u0131 izlemek ve sorunlar\u0131 gidermek i\u00e7in hayati \u00f6nem ta\u015f\u0131r. Go'da hata y\u00f6netimi genellikle error<\/code> interface'i arac\u0131l\u0131\u011f\u0131yla yap\u0131l\u0131r. \u00d6zel hata tipleri olu\u015fturarak daha anlaml\u0131 hatalar d\u00f6nd\u00fcrebiliriz. Loglama i\u00e7in ise Go'nun standart log<\/code> paketi yeterli olsa da, logrus<\/a> veya zap<\/a> gibi yap\u0131land\u0131r\u0131lm\u0131\u015f loglama k\u00fct\u00fcphaneleri, daha fazla kontrol ve okunabilirlik sunar. Loglar, genellikle JSON format\u0131nda, log toplama sistemlerine (ELK Stack, Grafana Loki vb.) g\u00f6nderilir.<\/p>\n\n\/\/ main fonksiyonunda log ayarlar\u0131\nfunc main() {\n \/\/ ...\n \/\/ router'\u0131 olu\u015fturduktan sonra middleware'lar\u0131 ekleyebiliriz\n router.Use(loggingMiddleware) \/\/ Her iste\u011fi loglayan bir middleware\n\n log.Fatal(http.ListenAndServe(\":8000\", router)) \/\/ Hata durumunda loglar\n}\n\nfunc loggingMiddleware(next http.Handler) http.Handler {\n return http.HandlerFunc(func(w http.ResponseWriter, r *http.Request) {\n log.Printf(\"\u0130stek: %s %s\", r.Method, r.RequestURI)\n next.ServeHTTP(w, r)\n })\n}\n\n\/\/ Hata d\u00f6n\u00fc\u015f \u00f6rne\u011fi\nfunc handleError(w http.ResponseWriter, err error, statusCode int) {\n w.Header().Set(\"Content-Type\", \"application\/json\")\n w.WriteHeader(statusCode)\n json.NewEncoder(w).Encode(map[string]string{\"error\": err.Error()})\n log.Printf(\"API hatas\u0131: %v\", err) \/\/ Hatalar\u0131 logla\n}\n <\/pre>\n<\/code><\/p>\n
Konfig\u00fcrasyon Y\u00f6netimi ve \u00c7evre De\u011fi\u015fkenleri<\/h3>\n
Veritaban\u0131 ba\u011flant\u0131 dizesi, API anahtarlar\u0131, JWT s\u0131rlar\u0131 gibi hassas veya ortama \u00f6zg\u00fc bilgiler do\u011frudan kodda tutulmamal\u0131d\u0131r. Bunlar genellikle \u00e7evre de\u011fi\u015fkenleri (environment variables) veya konfig\u00fcrasyon dosyalar\u0131 arac\u0131l\u0131\u011f\u0131yla y\u00f6netilir. Go'da os.Getenv()<\/code> kullanarak \u00e7evre de\u011fi\u015fkenlerine eri\u015febilir veya Viper<\/a> gibi k\u00fct\u00fcphanelerle daha geli\u015fmi\u015f konfig\u00fcrasyon y\u00f6netimi yapabilirsiniz. Bu, uygulaman\u0131z\u0131n farkl\u0131 ortamlarda (geli\u015ftirme, test, \u00fcretim) kolayca yap\u0131land\u0131r\u0131labilmesini sa\u011flar ve g\u00fcvenlik risklerini azalt\u0131r.<\/p>\nPerformans Optimizasyonu (Goroutines, Caching)<\/h3>\n
Go'nun en b\u00fcy\u00fck avantajlar\u0131ndan biri goroutine'ler arac\u0131l\u0131\u011f\u0131yla kolayca e\u015fzamanl\u0131l\u0131k sa\u011flamas\u0131d\u0131r. Uzun s\u00fcren I\/O i\u015flemleri (veritaban\u0131 sorgular\u0131, harici API \u00e7a\u011fr\u0131lar\u0131) veya yo\u011fun hesaplama gerektiren g\u00f6revler i\u00e7in goroutine'leri kullanarak isteklerin paralel olarak i\u015flenmesini sa\u011flayabilir, b\u00f6ylece API'n\u0131z\u0131n yan\u0131t s\u00fcresini \u00f6nemli \u00f6l\u00e7\u00fcde iyile\u015ftirebilirsiniz. Ayr\u0131ca, s\u0131k eri\u015filen ama nadiren de\u011fi\u015fen veriler i\u00e7in \u00f6nbellekleme (caching) mekanizmalar\u0131 uygulamak performans\u0131 art\u0131rabilir. Redis gibi belleki\u00e7i veri depolar\u0131, API \u00f6nbelle\u011fi olarak s\u0131kl\u0131kla kullan\u0131l\u0131r.<\/p>\n
Uzman \u0130pucu: Goroutine'leri kullan\u0131rken dikkatli olun! A\u015f\u0131r\u0131 goroutine olu\u015fturmak veya goroutine'ler aras\u0131 senkronizasyonu do\u011fru y\u00f6netememek, uygulaman\u0131zda performans sorunlar\u0131na veya kilitlenmelere yol a\u00e7abilir. Her zaman performans testleri yap\u0131n ve kaynak kullan\u0131m\u0131n\u0131 izleyin.<\/div>\nMobil Uyumluluk ve Responsive Tasar\u0131m Yakla\u015f\u0131m\u0131<\/h3>\n
REST API'lar do\u011frudan bir kullan\u0131c\u0131 aray\u00fcz\u00fc sunmazlar; genellikle mobil uygulamalar, web siteleri veya di\u011fer servisler taraf\u0131ndan t\u00fcketilirler. Ancak, API tasar\u0131m\u0131nda mobil uyumlulu\u011fu dolayl\u0131 olarak d\u00fc\u015f\u00fcnmek \u00f6nemlidir. \u00d6rne\u011fin, b\u00fcy\u00fck veri k\u00fcmelerini tek seferde g\u00f6ndermek yerine sayfalama (pagination) uygulamak, mobil cihazlar\u0131n daha az veri t\u00fcketmesini sa\u011flar. Ayr\u0131ca, API yan\u0131tlar\u0131n\u0131n boyutunu k\u00fc\u00e7\u00fcltmek i\u00e7in gereksiz alanlar\u0131 d\u0131\u015far\u0131da b\u0131rakmak veya s\u0131k\u0131\u015ft\u0131rma kullanmak da faydal\u0131d\u0131r. API'n\u0131z\u0131n t\u00fcketicileri i\u00e7in tutarl\u0131 ve iyi belgelenmi\u015f bir aray\u00fcz sa\u011flamak, mobil geli\u015ftiricilerin i\u015fini kolayla\u015ft\u0131r\u0131r. Direkt olarak HTML \u00e7\u0131kt\u0131s\u0131 olmasa da, e\u011fer API'n\u0131z bir web aray\u00fcz\u00fcn\u00fc besliyorsa, o web aray\u00fcz\u00fcn\u00fcn mobil uyumlu HTML\/CSS'e sahip oldu\u011fundan emin olun. A\u015fa\u011f\u0131daki gibi basit bir CSS yap\u0131s\u0131, mobil uyumlu bir aray\u00fcz i\u00e7in ba\u015flang\u0131\u00e7 noktas\u0131 olabilir:<\/p>\n
\n