Yadda farawa ɗaya ya tashi daga docker-compose zuwa Kubernetes

A cikin wannan labarin, Ina so in yi magana game da yadda muka canza tsarin ƙididdiga a kan aikin farawa, dalilin da ya sa muka yi shi da kuma matsalolin da muka magance a hanya. Wannan labarin ba zai iya da'awar zama na musamman ba, amma har yanzu ina tsammanin zai iya zama da amfani ga wani, tun lokacin da ake magance matsalar, mun tattara kayan tare da ƙoƙari mai kyau.  

Me muke da shi kuma me muke magana akai? Kuma muna da aikin farawa tare da kimanin shekaru 2 na tarihin ci gaba daga filin talla. An fara gina aikin a matsayin microservice, kuma an rubuta sashin sabar sa a Symfony + ƙaramin Laravel, Django da NodeJs na asali. Ayyukan galibi API ne don abokan cinikin wayar hannu (akwai 3 daga cikinsu a cikin aikin) da namu SDK don IOS (wanda aka gina a cikin aikace-aikacen abokan cinikinmu), da kuma mu'amalar yanar gizo da dashboards iri-iri na waɗannan abokan cinikin. Duk hidimomin da farko an kulle su kuma an gudanar da su ƙarƙashin docker-compose.

Gaskiya ne, ba a yi amfani da docker-compose a ko'ina ba, amma kawai a cikin yanayin gida na masu haɓakawa, a kan uwar garken gwaji, da kuma cikin bututun lokacin gini da ayyukan gwaji. Amma a cikin yanayin samarwa, Google Kubernetes Engine (GKE) an yi amfani da shi. Haka kuma, mun saita GKE a farkon aikin gaba ɗaya ta hanyar haɗin yanar gizon sa, wanda yake da sauri sosai kuma, kamar yadda muke gani a lokacin, dacewa. Tsarin gina hotunan docker kawai don ƙaddamar da ayyuka a cikin GKE an sarrafa shi ta atomatik anan.

Kara karantawa