Karma\u015f\u0131k i\u015f s\u00fcre\u00e7lerini y\u00f6netmekte zorlan\u0131yor musunuz? go-workflow-engine ile Go projelerinizde tak-\u00e7al\u0131\u015ft\u0131r i\u015f ak\u0131\u015flar\u0131 olu\u015fturmay\u0131 ad\u0131m ad\u0131m \u00f6\u011frenin.<\/p>\n
Modern yaz\u0131l\u0131m geli\u015ftirme d\u00fcnyas\u0131nda, \u00f6zellikle mikroservis mimarileri (microservices architecture) ve da\u011f\u0131t\u0131k sistemler yayg\u0131nla\u015ft\u0131k\u00e7a, i\u015f s\u00fcre\u00e7lerinin y\u00f6netimi b\u00fcy\u00fck bir sorun haline gelmektedir. Bir kullan\u0131c\u0131n\u0131n e-ticaret sitesinden al\u0131\u015fveri\u015f yapmas\u0131 kadar basit g\u00f6r\u00fcnen bir i\u015flem bile arka planda \u00f6deme alma, stok g\u00fcncelleme, fatura kesme ve kargoya verme gibi onlarca farkl\u0131 ad\u0131mdan olu\u015fur. Bu ad\u0131mlar\u0131n s\u0131ras\u0131yla, g\u00fcvenli bir \u015fekilde ve hata durumlar\u0131nda geri al\u0131nabilir (rollback) olarak y\u00f6netilmesi gerekir. \u0130\u015fte tam bu noktada, Go dilinin g\u00fcc\u00fcn\u00fc arkas\u0131na alan hafif ve esnek bir k\u00fct\u00fcphane olan Geli\u015ftiriciler olarak genellikle bu t\u00fcr s\u00fcre\u00e7leri y\u00f6netmek i\u00e7in karma\u015f\u0131k Yaz\u0131l\u0131m projelerinin ba\u015flang\u0131c\u0131nda i\u015f s\u00fcre\u00e7leri genellikle olduk\u00e7a basit g\u00f6r\u00fcn\u00fcr. \u00d6rne\u011fin, bir kullan\u0131c\u0131n\u0131n kaydolma s\u00fcreci yaln\u0131zca veritaban\u0131na kay\u0131t eklemekten ibaret olabilir. Ancak, i\u015f gereksinimleri b\u00fcy\u00fcd\u00fck\u00e7e bu s\u00fcrece e-posta do\u011frulama, ho\u015f geldin SMS’i g\u00f6nderme, CRM sistemine veri aktarma ve analitik ara\u00e7lar\u0131n\u0131 tetikleme gibi yeni ad\u0131mlar eklenir. Bu ad\u0131mlar\u0131n her biri farkl\u0131 d\u0131\u015f servislerle (third-party APIs) ileti\u015fim kurmay\u0131 gerektirir.<\/p>\n \u00d6zellikle d\u0131\u015f servislerin yan\u0131t vermemesi, a\u011f kesintileri veya beklenmedik sistem hatalar\u0131 durumunda s\u00fcrecin nas\u0131l davranaca\u011f\u0131 b\u00fcy\u00fck bir muammad\u0131r. E\u011fer \u00f6deme ba\u015far\u0131l\u0131 olduysa ancak stok g\u00fcncelleme s\u0131ras\u0131nda hata al\u0131nd\u0131ysa ne olacak? Kullan\u0131c\u0131n\u0131n paras\u0131 iade edilecek mi, yoksa sistem otomatik olarak i\u015flemi yeniden mi deneyecek (retry)? Bu t\u00fcr senaryolar\u0131 manuel olarak kodlamak, spagetti kod (spaghetti code) olarak adland\u0131r\u0131lan karma\u015f\u0131k yap\u0131lar\u0131n ortaya \u00e7\u0131kmas\u0131na neden olur.<\/p>\n Bununla birlikte, i\u015f ak\u0131\u015flar\u0131n\u0131n izlenebilirli\u011fi (observability) de ayr\u0131 bir problemdir. Hangi i\u015flemin hangi ad\u0131mda tak\u0131ld\u0131\u011f\u0131n\u0131, hangi hatayla kar\u015f\u0131la\u015f\u0131ld\u0131\u011f\u0131n\u0131 ve s\u00fcrecin ne kadar s\u00fcrede tamamland\u0131\u011f\u0131n\u0131 g\u00f6rmek her zaman kolay olmaz. Bir i\u015f ak\u0131\u015f\u0131 motoru (workflow engine), t\u00fcm bu karma\u015f\u0131kl\u0131\u011f\u0131 soyutlayarak geli\u015ftiriciye standart, g\u00fcvenli ve izlenebilir bir yap\u0131 sunar. Go dilinin y\u00fcksek e\u015fzamanl\u0131l\u0131k (concurrency) yetenekleri sayesinde, bu s\u00fcre\u00e7leri minimum kaynak t\u00fcketimiyle y\u00f6netmek m\u00fcmk\u00fcnd\u00fcr.<\/p>\n Bu k\u00fct\u00fcphanenin temel amac\u0131, i\u015f s\u00fcre\u00e7lerinizi k\u00fc\u00e7\u00fck, ba\u011f\u0131ms\u0131z ve yeniden kullan\u0131labilir g\u00f6revlere (tasks) b\u00f6lmenizi sa\u011flamakt\u0131r. Her bir g\u00f6rev, girdileri (inputs) al\u0131r, kendi mant\u0131\u011f\u0131n\u0131 \u00e7al\u0131\u015ft\u0131r\u0131r ve \u00e7\u0131kt\u0131lar\u0131 (outputs) bir sonraki g\u00f6reve aktar\u0131r. K\u00fct\u00fcphane, bu g\u00f6revlerin hangi s\u0131ra ile \u00e7al\u0131\u015faca\u011f\u0131n\u0131, hata durumlar\u0131nda nas\u0131l davran\u0131laca\u011f\u0131n\u0131 ve s\u00fcre\u00e7lerin nas\u0131l izlenece\u011fini y\u00f6netir.<\/p>\n K\u00fct\u00fcphanenin sundu\u011fu temel kavramlar\u0131 \u015fu \u015fekilde \u00f6zetleyebiliriz:<\/p>\n \u015eimdi, Paket kurulumunu tamamlad\u0131ktan sonra, ilk i\u015f ak\u0131\u015f\u0131m\u0131z\u0131 tan\u0131mlamak i\u00e7in kod yazmaya ba\u015flayabiliriz. Bu \u00f6rnekte, bir kullan\u0131c\u0131n\u0131n kaydolmas\u0131n\u0131n ard\u0131ndan veritaban\u0131na kaydedilmesi ve ard\u0131ndan bir ho\u015f geldin e-postas\u0131 g\u00f6nderilmesi ad\u0131mlar\u0131n\u0131 sim\u00fcle edece\u011fiz. A\u015fa\u011f\u0131daki kod blo\u011funda bu basit ak\u0131\u015f\u0131n nas\u0131l kuruldu\u011funu g\u00f6rebilirsiniz:<\/p>\n Yukar\u0131daki kodda, ilk olarak iki adet g\u00f6rev (task) tan\u0131mlad\u0131k. Her g\u00f6rev, Basit \u00f6rneklerin \u00f6tesine ge\u00e7erek, ger\u00e7ek hayatta s\u0131kl\u0131kla kar\u015f\u0131la\u015ft\u0131\u011f\u0131m\u0131z bir e-ticaret sipari\u015f s\u00fcrecini ele alal\u0131m. Bu senaryoda, kullan\u0131c\u0131n\u0131n sepeti onaylamas\u0131ndan kargoya verilmesine kadar ge\u00e7en s\u00fcreci tasarlayaca\u011f\u0131z. \u0130\u015f ak\u0131\u015f\u0131m\u0131z \u015fu ad\u0131mlardan olu\u015facak: \u00d6deme kontrol\u00fc, stok d\u00fc\u015f\u00fcm\u00fc, fatura olu\u015fturma ve kargo \u015firketine bildirim.<\/p>\n Bu s\u00fcre\u00e7te ya\u015fanabilecek olas\u0131 hatalar\u0131 da g\u00f6z \u00f6n\u00fcnde bulundurmal\u0131y\u0131z. \u00d6rne\u011fin, \u00f6deme ba\u015far\u0131l\u0131 olmas\u0131na ra\u011fmen stok yetersiz \u00e7\u0131karsa ne olacak? Bu durumda “telafi edici i\u015flem” (compensating transaction) \u00e7al\u0131\u015fmal\u0131 ve \u00f6deme iade edilmelidir. A\u015fa\u011f\u0131daki tabloda bu karma\u015f\u0131k ak\u0131\u015f\u0131n durum ge\u00e7i\u015flerini inceleyebilirsiniz:<\/p>\n G\u00f6r\u00fcld\u00fc\u011f\u00fc \u00fczere, her ba\u015far\u0131l\u0131 ad\u0131m bir sonrakini tetiklerken, herhangi bir ad\u0131mda ya\u015fanacak ba\u015far\u0131s\u0131zl\u0131k \u00f6nceki ad\u0131mlar\u0131n geri al\u0131nmas\u0131n\u0131 gerektirir. Ger\u00e7ek d\u00fcnya projelerinde t\u00fcm g\u00f6revler do\u011frusal (linear) bir s\u0131rada ilerlemez. Baz\u0131 i\u015flemlerin performans\u0131 art\u0131rmak ad\u0131na paralel olarak \u00e7al\u0131\u015ft\u0131r\u0131lmas\u0131 gerekir. \u00d6rne\u011fin, bir sipari\u015f tamamland\u0131\u011f\u0131nda hem kullan\u0131c\u0131ya SMS g\u00f6ndermek hem de muhasebe sistemine veri g\u00f6ndermek istiyorsak, bu iki i\u015flemi ayn\u0131 anda ba\u015flatabiliriz. Go dilinin Hata y\u00f6netimi (error handling) taraf\u0131nda ise k\u00fct\u00fcphane bize geli\u015fmi\u015f yeniden deneme (retry) politikalar\u0131 sunar. \u00d6zellikle d\u0131\u015f servislerle \u00e7al\u0131\u015f\u0131rken, ge\u00e7ici a\u011f kesintileri nedeniyle hatalar alabiliriz. Bu durumlarda hemen hata vermek yerine, i\u015flemi belirli aral\u0131klarla yeniden denemek en do\u011fru yakla\u015f\u0131md\u0131r. \u00dcstsel geri \u00e7ekilme (exponential backoff) algoritmas\u0131 kullanarak, d\u0131\u015f servisi yormadan ak\u0131ll\u0131 yeniden denemeler yap\u0131land\u0131rabilirsiniz.<\/p>\n Y\u00fcksek trafikli sistemlerde \u00e7al\u0131\u015fan bir i\u015f ak\u0131\u015f\u0131 motorunun en b\u00fcy\u00fck s\u0131nav\u0131 performans ve bellek (memory) y\u00f6netimidir. Go dili, hafif yap\u0131s\u0131 sayesinde bu konuda olduk\u00e7a avantajl\u0131d\u0131r. Ancak, yanl\u0131\u015f tasarlanm\u0131\u015f bir i\u015f ak\u0131\u015f\u0131 motoru bellek s\u0131z\u0131nt\u0131lar\u0131na (memory leaks) yol a\u00e7abilir. \u0130lk olarak, g\u00f6revler aras\u0131nda ta\u015f\u0131nan veri miktar\u0131n\u0131 minimumda tutmal\u0131s\u0131n\u0131z. Bununla birlikte, Go’nun \u00e7\u00f6p toplay\u0131c\u0131s\u0131n\u0131 (garbage collector) yormamak ad\u0131na, nesne havuzlama (object pooling) tekniklerinden yararlanabilirsiniz. S\u0131k olu\u015fturulup yok edilen i\u015f ak\u0131\u015f\u0131 nesneleri yerine, Evet, olduk\u00e7a uygundur. \u00d6zellikle mikroservisleriniz i\u00e7inde hafif, h\u0131zl\u0131 ve harici ba\u011f\u0131ml\u0131l\u0131\u011f\u0131 olmayan bir i\u015f ak\u0131\u015f\u0131 \u00e7\u00f6z\u00fcm\u00fc ar\u0131yorsan\u0131z, bu k\u00fct\u00fcphane \u00fcretim ortam\u0131nda y\u00fcksek performansla \u00e7al\u0131\u015facakt\u0131r. Ancak, \u00e7ok b\u00fcy\u00fck ve haftalarca s\u00fcren uzun soluklu (long-running) i\u015f ak\u0131\u015flar\u0131 i\u00e7in Temporal gibi durum saklama \u00f6zellikli sistemleri tercih etmek daha do\u011fru olabilir.<\/p>\n Evet, k\u00fct\u00fcphane durum saklama (state persistence) aray\u00fczlerini (interface) destekler. Kendi veritaban\u0131 adapt\u00f6r\u00fcn\u00fcz\u00fc yazarak (PostgreSQL, MySQL veya Redis gibi), i\u015f ak\u0131\u015f\u0131n\u0131n kald\u0131\u011f\u0131 yeri veritaban\u0131na kaydedebilir ve sistem kapansa bile kald\u0131\u011f\u0131 yerden devam etmesini sa\u011flayabilirsiniz.<\/p>\n Her bir g\u00f6revinize bir K\u00fct\u00fcphane Go tabanl\u0131 olsa da, g\u00f6revlerinizin i\u00e7ine HTTP veya gRPC \u00e7a\u011fr\u0131lar\u0131 ekleyerek Java, Python veya Node.js ile yaz\u0131lm\u0131\u015f harici servisleri i\u015f ak\u0131\u015f\u0131n\u0131z\u0131n bir par\u00e7as\u0131 haline getirebilirsiniz.<\/p>\n #Teknoloji #WebGeli\u015ftirme #Golang #Yaz\u0131l\u0131mGeli\u015ftirme #WorkflowEngine<\/p>\ngo-workflow-engine<\/code> devreye giriyor.<\/p>\nif-else<\/code> bloklar\u0131 veya devasa durum makineleri (state machine) yazar\u0131z. Ancak, zamanla bu kod taban\u0131 okunamaz ve bak\u0131m\u0131 yap\u0131lamaz bir hale gelir. Bu makalede, Go dilinde i\u015f ak\u0131\u015flar\u0131n\u0131z\u0131 nas\u0131l “tak-\u00e7al\u0131\u015ft\u0131r” (plug-and-play) bir yakla\u015f\u0131mla tasarlayabilece\u011finizi, kod karma\u015fas\u0131ndan nas\u0131l kurtulabilece\u011finizi ve go-workflow-engine<\/code> k\u00fct\u00fcphanesini projelerinize nas\u0131l entegre edebilece\u011finizi detayl\u0131ca inceleyece\u011fiz.<\/p>\n\u0130\u015f Ak\u0131\u015f\u0131 Y\u00f6netimi Neden Bu Kadar Karma\u015f\u0131k?<\/h2>\n
go-workflow-engine Nedir ve Ne \u0130\u015fe Yarar?<\/h2>\n
go-workflow-engine<\/code>, Go (Golang) dili ile geli\u015ftirilmi\u015f, minimalist ve son derece esnek bir i\u015f ak\u0131\u015f\u0131 y\u00f6netim k\u00fct\u00fcphanesidir. A\u011f\u0131r ve kurulumu zor olan kurumsal i\u015f ak\u0131\u015f\u0131 motorlar\u0131n\u0131n (\u00f6rne\u011fin Camunda veya Temporal) aksine, bu k\u00fct\u00fcphane projenize do\u011frudan bir k\u00fct\u00fcphane (library) olarak dahil edilir. Herhangi bir harici sunucu veya veritaban\u0131 ba\u011f\u0131ml\u0131l\u0131\u011f\u0131 gerektirmeden, do\u011frudan uygulama kodunuzun i\u00e7inde \u00e7al\u0131\u015f\u0131r.<\/p>\n\n
Ad\u0131m Ad\u0131m Kurulum ve \u0130lk \u0130\u015f Ak\u0131\u015f\u0131n\u0131n Olu\u015fturulmas\u0131<\/h2>\n
go-workflow-engine<\/code> k\u00fct\u00fcphanesini projemize dahil edelim ve basit bir \u00fcyelik onaylama s\u00fcreci tasarlayal\u0131m. \u0130lk olarak, Go mod\u00fcl\u00fcm\u00fcz\u00fc ba\u015flatal\u0131m ve gerekli paketleri projemize \u00e7ekelim. Terminal \u00fczerinden a\u015fa\u011f\u0131daki komutlar\u0131 \u00e7al\u0131\u015ft\u0131rarak ba\u015flayabilirsiniz:<\/p>\ngo mod init go-workflow-demo\ngo get github.com\/username\/go-workflow-engine<\/code><\/pre>\n<\/div>\npackage main\n\nimport (\n\t\"context\"\n\t\"fmt\"\n\t\"log\"\n\t\"time\"\n\n\t\"github.com\/username\/go-workflow-engine\/workflow\"\n)\n\n\/\/ DBRegisterTask veritaban\u0131 kay\u0131t ad\u0131m\u0131n\u0131 temsil eder\ntype DBRegisterTask struct{}\n\nfunc (t *DBRegisterTask) Execute(ctx context.Context, state *workflow.State) error {\n\tfmt.Println(\"[Ad\u0131m 1] Kullan\u0131c\u0131 veritaban\u0131na kaydediliyor...\")\n\ttime.Sleep(500 * time.Millisecond) \/\/ Sim\u00fcle edilen gecikme\n\tstate.Set(\"userID\", \"usr_12345\")\n\treturn nil\n}\n\n\/\/ SendEmailTask e-posta g\u00f6nderme ad\u0131m\u0131n\u0131 temsil eder\ntype SendEmailTask struct{}\n\nfunc (t *SendEmailTask) Execute(ctx context.Context, state *workflow.State) error {\n\tuserID, _ := state.Get(\"userID\")\n\tfmt.Printf(\"[Ad\u0131m 2] %s ID'li kullan\u0131c\u0131ya ho\u015f geldin e-postas\u0131 g\u00f6nderiliyor...\\n\", userID)\n\treturn nil\n}\n\nfunc main() {\n\t\/\/ Yeni bir i\u015f ak\u0131\u015f\u0131 olu\u015fturuluyor\n\tengine := workflow.NewEngine()\n\n\t\/\/ G\u00f6revler tan\u0131mlan\u0131yor\n\tdbTask := &DBRegisterTask{}\n\temailTask := &SendEmailTask{}\n\n\t\/\/ \u0130\u015f ak\u0131\u015f\u0131 ad\u0131mlar\u0131 ekleniyor\n\tengine.RegisterTask(\"RegisterDB\", dbTask)\n\tengine.RegisterTask(\"SendEmail\", emailTask)\n\n\t\/\/ Ak\u0131\u015f s\u0131ras\u0131 belirleniyor\n\tengine.SetSequence([]string{\"RegisterDB\", \"SendEmail\"})\n\n\t\/\/ \u0130\u015f ak\u0131\u015f\u0131n\u0131 ba\u015flat\n\tctx := context.Background()\n\terr := engine.Start(ctx)\n\tif err != nil {\n\t\tlog.Fatalf(\"\u0130\u015f ak\u0131\u015f\u0131 hatayla sonu\u00e7land\u0131: %v\", err)\n\t}\n\n\tfmt.Println(\"\u0130\u015f ak\u0131\u015f\u0131 ba\u015far\u0131yla tamamland\u0131!\")\n}<\/code><\/pre>\n<\/div>\nExecute<\/code> metoduna sahip bir yap\u0131d\u0131r (struct). state<\/code> nesnesi sayesinde, ilk g\u00f6revde \u00fcretti\u011fimiz userID<\/code> bilgisini g\u00fcvenli bir \u015fekilde ikinci g\u00f6reve aktarabildik. Sonu\u00e7 olarak, karma\u015f\u0131k durum y\u00f6netimleri ile u\u011fra\u015fmadan, temiz ve mod\u00fcler bir i\u015f ak\u0131\u015f\u0131 elde etmi\u015f olduk.<\/p>\nGer\u00e7ek D\u00fcnya Senaryosu: E-Ticaret Sipari\u015f ve Kargo S\u00fcreci<\/h2>\n
\n\n
\n \nMevcut Durum<\/th>\n Tetiklenen Olay<\/th>\n Hedef Durum<\/th>\n Hata Durumunda Aksiyon<\/th>\n<\/tr>\n<\/thead>\n \n Sipari\u015f Al\u0131nd\u0131<\/td>\n \u00d6deme Ba\u015far\u0131l\u0131<\/td>\n \u00d6deme Onayland\u0131<\/td>\n \u0130\u015flemi \u0130ptal Et<\/td>\n<\/tr>\n \n \u00d6deme Onayland\u0131<\/td>\n Stok Rezerv Edildi<\/td>\n Stok G\u00fcncellendi<\/td>\n \u00d6demeyi \u0130ade Et (Rollback)<\/td>\n<\/tr>\n \n Stok G\u00fcncellendi<\/td>\n Fatura Kesildi<\/td>\n Fatura Haz\u0131r<\/td>\n Stoku Geri Sal + \u00d6demeyi \u0130ade Et<\/td>\n<\/tr>\n \n Fatura Haz\u0131r<\/td>\n Kargoya Verildi<\/td>\n Sipari\u015f Tamamland\u0131<\/td>\n Destek Talebi A\u00e7<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n go-workflow-engine<\/code>, bu t\u00fcr geri alma (rollback) senaryolar\u0131n\u0131 yerle\u015fik olarak destekler. Her g\u00f6reve bir Rollback<\/code> metodu tan\u0131mlayarak, hata an\u0131nda sistemin otomatik olarak \u00f6nceki ad\u0131mlar\u0131 tersine i\u015fletmesini sa\u011flayabilirsiniz. Bu sayede veri tutarl\u0131l\u0131\u011f\u0131 (data consistency) her zaman korunmu\u015f olur.<\/p>\nGeli\u015fmi\u015f \u00d6zellikler: Paralel G\u00f6revler ve Hata Y\u00f6netimi Nas\u0131l Yap\u0131l\u0131r?<\/h2>\n
goroutine<\/code> yap\u0131s\u0131 sayesinde bu olduk\u00e7a kolayd\u0131r ancak takibi zordur.<\/p>\ngo-workflow-engine<\/code>, paralel g\u00f6rev y\u00f6netimini dahili olarak destekler. K\u00fct\u00fcphanenin sundu\u011fu paralel grup (parallel group) \u00f6zelli\u011fi sayesinde, birden fazla g\u00f6revi ayn\u0131 anda ba\u015flatabilir ve t\u00fcm\u00fcn\u00fcn tamamlanmas\u0131n\u0131 bekleyebilirsiniz. A\u015fa\u011f\u0131daki kod \u00f6rne\u011finde, paralel g\u00f6revlerin nas\u0131l tan\u0131mland\u0131\u011f\u0131n\u0131 g\u00f6rebilirsiniz:<\/p>\n\/\/ Paralel \u00e7al\u0131\u015facak g\u00f6revlerin tan\u0131mlanmas\u0131\nparallelGroup := workflow.NewParallelGroup()\n\nparallelGroup.AddTask(\"SMS_Notify\", &SMSNotificationTask{})\nparallelGroup.AddTask(\"Slack_Notify\", &SlackNotificationTask{})\n\n\/\/ Ana i\u015f ak\u0131\u015f\u0131na paralel grubun eklenmesi\nengine.RegisterGroup(\"Notifications\", parallelGroup)<\/code><\/pre>\n<\/div>\ngo-workflow-engine ile Performans Optimizasyonu Nas\u0131l Sa\u011flan\u0131r?<\/h2>\n
go-workflow-engine<\/code> kullan\u0131rken performans\u0131 en \u00fcst d\u00fczeye \u00e7\u0131karmak i\u00e7in dikkat edilmesi gereken baz\u0131 \u00f6nemli noktalar vard\u0131r.<\/p>\nstate<\/code> nesnesine devasa JSON nesneleri veya b\u00fcy\u00fck veri yap\u0131lar\u0131 koymak yerine, yaln\u0131zca ilgili verilerin benzersiz kimliklerini (ID) aktarmak ve veritaban\u0131 sorgular\u0131n\u0131 g\u00f6revlerin i\u00e7inde yapmak bellek t\u00fcketimini ciddi oranda azaltacakt\u0131r.<\/p>\nsync.Pool<\/code> kullanarak \u00f6nceden olu\u015fturulmu\u015f nesneleri yeniden kullanmak, y\u00fcksek e\u015fzamanl\u0131l\u0131k gerektiren anlarda CPU \u00fczerindeki y\u00fck\u00fc hafifletecektir. Ayr\u0131ca, veritaban\u0131 ba\u011flant\u0131lar\u0131n\u0131 ve HTTP istemcilerini (HTTP client) her g\u00f6revde yeniden olu\u015fturmak yerine, tek bir global \u00f6rnek (singleton) \u00fczerinden payla\u015fmak ba\u011flant\u0131 havuzunun verimli kullan\u0131lmas\u0131n\u0131 sa\u011flar.<\/p>\nS\u0131k\u00e7a Sorulan Sorular (SSS)<\/h2>\n
1. go-workflow-engine \u00fcretim ortam\u0131 (production) i\u00e7in uygun mudur?<\/h3>\n
2. \u0130\u015f ak\u0131\u015f\u0131n\u0131n durumunu bir veritaban\u0131nda saklayabilir miyim?<\/h3>\n
3. Hata durumunda t\u00fcm ak\u0131\u015f\u0131 nas\u0131l geri alabilirim (rollback)?<\/h3>\n
Rollback<\/code> metodu tan\u0131mlayarak bu i\u015flemi ger\u00e7ekle\u015ftirebilirsiniz. \u0130\u015f ak\u0131\u015f\u0131 s\u0131ras\u0131nda herhangi bir ad\u0131mda hata olu\u015ftu\u011funda, motor otomatik olarak o ana kadar ba\u015far\u0131yla tamamlanm\u0131\u015f t\u00fcm ad\u0131mlar\u0131n rollback metotlar\u0131n\u0131 ters s\u0131rayla \u00e7al\u0131\u015ft\u0131r\u0131r.<\/p>\n4. Di\u011fer dillerle yaz\u0131lm\u0131\u015f servisleri bu ak\u0131\u015fa dahil edebilir miyim?<\/h3>\n