{"id":53442,"date":"2019-12-02T00:00:00","date_gmt":"2019-12-01T21:00:00","guid":{"rendered":"https:\/\/prohoster.info\/blog\/blog_prohoster\/legacy-servisy-v-vashej-infrastrukture"},"modified":"2020-02-18T14:01:20","modified_gmt":"2020-02-18T11:01:20","slug":"legacy-servisy-v-vashej-infrastrukture","status":"publish","type":"post","link":"https:\/\/prohoster.info\/sq\/blog\/administrirovanie\/legacy-servisy-v-vashej-infrastrukture","title":{"rendered":"Sh\u00ebrbimet Legacy n\u00eb infrastruktur\u00ebn tuaj","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"

P\u00ebrsh\u00ebndetje! Un\u00eb quhem Pasha Chernyak, jam zhvilluesi kryesor n\u00eb QIWI, dhe sot dua t\u00eb flas p\u00ebr t\u00eb pashmangshmen. Rreth Legacy.<\/p>\n

T\u00eb fillojm\u00eb me nj\u00eb pyetje: \u00e7far\u00eb \u00ebsht\u00eb nj\u00eb sh\u00ebrbim Legacy? A \u00ebsht\u00eb nj\u00eb sh\u00ebrbim, t\u00eb cilin zhvilluesi nuk e ka prekur p\u00ebr nj\u00eb jav\u00eb\/muaj\/vit? Apo \u00ebsht\u00eb nj\u00eb sh\u00ebrbim, q\u00eb \u00ebsht\u00eb shkruar nga nj\u00eb programues m\u00eb pak me p\u00ebrvoj\u00eb, p\u00ebr shembull, konkretisht nga ju, por nj\u00eb vit m\u00eb par\u00eb? Dhe tani ju jeni m\u00eb t\u00eb zot\u00eb dhe m\u00eb t\u00eb p\u00ebrvoj\u00eb. Apo ndoshta, sh\u00ebrbimi Legacy \u00ebsht\u00eb nj\u00eb sh\u00ebrbim q\u00eb ju vendos\u00ebt t\u00eb mos e angazhoni m\u00eb dhe po e p\u00ebrgatitni ngadal\u00eb p\u00ebr z\u00ebvend\u00ebsim? \u00c7far\u00ebdo qoft\u00eb, l\u00ebnia e k\u00ebtij sh\u00ebrbimi pa mbik\u00ebqyrje dhe mos e p\u00ebrdit\u00ebsimi i tij \u2014 \u00ebsht\u00eb nj\u00eb bomb\u00eb me sahat q\u00eb mund t\u00eb shp\u00ebrthej\u00eb m\u00eb von\u00eb.<\/p>\n

\"Sh\u00ebrbimet<\/a><\/noindex><\/p>\n

Para se t\u00eb kalojm\u00eb te m\u00ebnyra se si ne n\u00eb QIWI punojm\u00eb me sh\u00ebrbimet tona Legacy, do t\u00eb flas p\u00ebr m\u00ebnyr\u00ebn se si ne rregulluam sh\u00ebrbimet n\u00eb Portofolin. Q\u00eb dy vjet, un\u00eb kam p\u00ebrgjegj\u00ebsin\u00eb p\u00ebr funksionimin e tij. N\u00ebse ndonj\u00ebher\u00eb ka nj\u00eb problem, gjithmon\u00eb m\u00eb telefonojn\u00eb p\u00ebr her\u00eb t\u00eb par\u00eb. M\u00eb zakonisht, nuk kam guximin t\u00eb telefonoj dik\u00eb tjet\u00ebr n\u00eb 11 t\u00eb nat\u00ebs, k\u00ebshtu q\u00eb m\u00eb duhet t\u00eb ulem dhe t\u00eb merrem me t\u00eb gjitha sh\u00ebrbimet e domain-it ton\u00eb. <\/p>\n

Por un\u00eb, si \u00e7do njeri tjet\u00ebr, m\u00eb p\u00eblqen t\u00eb fle nat\u00ebn, prandaj p\u00ebrpiqesha t\u00eb kuptoja ekspluatimin: \"Djem, pse m\u00eb telefononi mua?\" P\u00ebr t\u00eb cilin mora nj\u00eb p\u00ebrgjigje mjaft t\u00eb shkurt\u00ebr si: \"Kujt tjet\u00ebr?\". Sepse un\u00eb riparoj sh\u00ebrbimet, dhe djemt\u00eb thjesht nuk din\u00eb se kush duhet t\u00eb telefonojn\u00eb.<\/p>\n

Prandaj, n\u00eb nj\u00eb nga retrospektivat e ekipit t\u00eb backend-it t\u00eb Portofolit ne vendos\u00ebm se duhej t\u00eb krijonim nj\u00eb tabel\u00eb, n\u00eb t\u00eb cil\u00ebn do t\u00eb ishte lista e sh\u00ebrbimeve tona, mikrosh\u00ebrbimeve dhe monoliteve t\u00eb portofolit, dhe ata q\u00eb jan\u00eb p\u00ebrgjegj\u00ebs p\u00ebr to. Tabelat jan\u00eb t\u00eb dobishme, brenda arsyeshm\u00ebrive.
\n<\/a><\/noindex>
\nP\u00ebrve\u00e7 informacionit se kush p\u00ebrgjigjet p\u00ebr \u00e7far\u00eb, aty ishin p\u00ebrgjigjet p\u00ebr pyetje: kush \u00ebsht\u00eb pronari i sh\u00ebrbimit, kush \u00ebsht\u00eb p\u00ebrgjegj\u00ebs p\u00ebr zhvillimin e tij, p\u00ebr arkitektur\u00ebn dhe ciklin e jet\u00ebs. Nj\u00ebrit p\u00ebrgjegj\u00ebs p\u00ebr k\u00ebt\u00eb sh\u00ebrbim \u2014 njer\u00ebzit q\u00eb mund ta rregullojn\u00eb at\u00eb n\u00eb rast nevoje. Pronari i sh\u00ebrbimit ka t\u00eb drejt\u00eb t\u00eb l\u00ebr\u00eb +2 n\u00eb komitetet, p\u00ebrgjegj\u00ebsit gjithashtu duhet t\u00eb jen\u00eb patjet\u00ebr prezent\u00eb n\u00eb rishikim, p\u00ebrpara se ky sh\u00ebrbim t\u00eb pranoj\u00eb nj\u00eb komitet t\u00eb ri.<\/p>\n

Koha kalonte, filluan t\u00eb aplikoheshin praktika t\u00eb reja, p\u00ebr shembull, migrimi n\u00eb Kubernetes, kontrolli i stilit, spotbugs, ktlint, pranimi i log-eve n\u00eb Kibana, autodiscovery t\u00eb sh\u00ebrbimeve n\u00eb vend t\u00eb caktimit direkt t\u00eb adresave dhe tjera dobishm\u00ebri. Dhe kudo, tabela jon\u00eb na lejonte t\u00eb mbajm\u00eb aktualitetin e sh\u00ebrbimeve tona. P\u00ebr ne, kjo \u00ebsht\u00eb nj\u00eb lloj liste kontrolli q\u00eb tregon se ky sh\u00ebrbim di ta b\u00ebj\u00eb k\u00ebt\u00eb, por k\u00ebt\u00eb tjet\u00ebr ende jo. Por ne shkuam p\u00ebrpara, duke kuptuar se na mungonte informacioni mbi sh\u00ebrbimet tona, p\u00ebr t\u00eb cilat ne mbikqyrim, ku ndodhen burimet e sh\u00ebrbimit, ku nisen detyrat p\u00ebr nd\u00ebrtim n\u00eb TeamCity, si depozitojn\u00eb, ku ruhen burimet e testeve end2end, fotografit\u00eb p\u00ebr arkitektur\u00ebn, p\u00ebr vendimet e marra. N\u00eb m\u00ebnyr\u00eb ideale do t\u00eb donim q\u00eb t\u00eb gjith\u00eb ky informacion t\u00eb ishte diku dhe t\u00eb ishte n\u00eb dispozicion kur t\u00eb nevojitej. Prandaj, tabel\u00ebn ton\u00eb e b\u00ebm\u00eb fillimin p\u00ebr k\u00ebrkimin e informacionit.<\/p>\n

Por QIWI, ndon\u00ebse ruan shpirtin e nj\u00eb startup-i, \u00ebsht\u00eb nj\u00eb kompani e madhe. Ne jemi tashm\u00eb 12 vjet dhe ekipet po ndryshojn\u00eb: njer\u00ebzit ikin, njer\u00ebzit vijn\u00eb, formohen ekipe t\u00eb reja. Dhe zbuluam n\u00eb domenin ton\u00eb disa sh\u00ebrbime q\u00eb na kishin mbetur trash\u00ebgim. Disa erdh\u00ebn nga zhvilluesit e ekipeve t\u00eb tjera, disa lidheshin n\u00eb m\u00ebnyr\u00eb indirekte me Portofolin, prandaj sh\u00ebrbimi tani \u00ebsht\u00eb n\u00eb bilancin ton\u00eb. Pse t\u00eb merremi me at\u00eb se \u00e7far\u00eb punon dhe si? Sh\u00ebrbimi funksionon, dhe kemi ve\u00e7ori produkti q\u00eb duhet t'i zbatojm\u00eb patjet\u00ebr.<\/p>\n

Si ndodh zakonisht<\/h2>\n

\nPor n\u00eb nj\u00eb moment t\u00eb caktuar, zbulojm\u00eb se sh\u00ebrbimi ndalon s\u00eb funksionuari, di\u00e7ka \u00ebsht\u00eb prishur \u2014 \u00e7far\u00eb t\u00eb b\u00ebjm\u00eb n\u00eb k\u00ebt\u00eb situat\u00eb? Sh\u00ebrbimi thjesht ka pushuar s\u00eb funksionuari. Plot\u00ebsisht. Dhe e m\u00ebsuam k\u00ebt\u00eb, s\u00eb pari, rast\u00ebsisht, dhe s\u00eb dyti, pas gjasht\u00eb muajsh. K\u00ebshtu ndodh. E vetmja gj\u00eb q\u00eb dinim ishte n\u00eb cilat virtualka \u00ebsht\u00eb instaluar sh\u00ebrbimi, ku ndodhen burimet e tij, dhe gjith\u00e7ka tjet\u00ebr. Ne b\u00ebjm\u00eb git clone dhe p\u00ebrfshihemi n\u00eb mendimet e personit q\u00eb e kishte shkruar k\u00ebt\u00eb disa vjet m\u00eb par\u00eb, por \u00e7far\u00eb shohim? Asnj\u00eb gj\u00eb e njohur p\u00ebr ne si Spring Boot, megjith\u00ebse jemi m\u00ebsuar me gjith\u00e7ka, na duhen full stack dhe t\u00eb gjitha ato. Ndoshta ka Spring Framework? Por jo.<\/p>\n

Djali q\u00eb e shkruajti k\u00ebt\u00eb ishte i ashp\u00ebr dhe shkruante gjith\u00e7ka n\u00eb Java t\u00eb past\u00ebr. Nuk ka asnj\u00eb mjet t\u00eb njohur p\u00ebr zhvilluesit, dhe lind ideja - duhet ta rishkruajm\u00eb t\u00eb gjith\u00eb k\u00ebt\u00eb. Ne kemi mikrosh\u00ebrbime, dhe nga secili toster d\u00ebgjohet e njohura \"Djem, mikrosh\u00ebrbimet jan\u00eb ato q\u00eb ju duhen!\". N\u00ebse ndodhi ndonj\u00eb gj\u00eb e keqe, ju do t\u00eb mund t\u00eb merrni \u00e7do gjuh\u00eb dhe gjith\u00e7ka do t\u00eb shkoj\u00eb mir\u00eb.<\/p>\n

Problemi \u00ebsht\u00eb se momentalisht nuk kemi nj\u00eb klient q\u00eb p\u00ebrgjigjet p\u00ebr k\u00ebt\u00eb sh\u00ebrbim. \u00c7far\u00eb k\u00ebrkesash biznesi kishte ai, \u00e7far\u00eb duhet t\u00eb b\u00ebj\u00eb ky sh\u00ebrbim? Ky sh\u00ebrbim \u00ebsht\u00eb ngusht\u00ebsisht i integruar n\u00eb proceset tuaja biznesore. <\/p>\n

Tani, sa e leht\u00eb \u00ebsht\u00eb t\u00eb rishkruash nj\u00eb sh\u00ebrbim, pa e ditur k\u00ebrkesat e tij biznesore? Sh\u00ebrbimi nuk dihet si logaritet, a ka metrika - nuk dihet. Cilat jan\u00eb ato, n\u00ebse ka - akoma m\u00eb shum\u00eb nuk dihet. Dhe gjithashtu, n\u00eb sh\u00ebrbim ka nj\u00eb num\u00ebr t\u00eb madh klasash me logjik\u00eb biznesi t\u00eb paqart\u00eb. Disa gj\u00ebra futen n\u00eb nj\u00eb baz\u00eb t\u00eb dh\u00ebnash, p\u00ebr t\u00eb cil\u00ebn ne p\u00ebr momentin nuk dim\u00eb asgj\u00eb. <\/p>\n

Nga e duhet t\u00eb fillosh?<\/h2>\n

\nNga gj\u00ebja m\u00eb logjike - nga prania e testeve. Atje zakonisht shkruhet ndonj\u00eb logjik\u00eb dhe mund t\u00eb nxirren konkluzione p\u00ebr at\u00eb q\u00eb po ndodh. Tani \u00ebsht\u00eb mod\u00eb TDD, por ne shohim se at\u00ebher\u00eb 5 vjet m\u00eb par\u00eb gjith\u00e7ka ishte praktikisht n\u00eb t\u00eb nj\u00ebjt\u00ebn gj\u00ebndje si tani: nuk ka pothuajse asnj\u00eb test unit, dhe ato nuk do t\u00eb na thon\u00eb asgj\u00eb. Ndoshta vet\u00ebm p\u00ebr ndonj\u00eb kontroll, si n\u00ebnshkruhet ndonj\u00eb xml me ndonj\u00eb certifikat\u00eb t\u00eb personalizuar.<\/p>\n

Me kodin nuk kemi arritur t\u00eb kuptojm\u00eb asgj\u00eb, dhe ne duhet t\u00eb shohim \u00e7far\u00eb ndodh n\u00eb virtualizim. Hap\u00ebm log-et e sh\u00ebrbimit, gjet\u00ebm n\u00eb to nj\u00eb gabim t\u00eb klientit http, nj\u00eb certifikat\u00eb e vet\u00eb-n\u00ebnshkruar, e cila ishte e p\u00ebrfshir\u00eb n\u00eb burimet e aplikacionit, kishte skaduar pa turp. Contact me analist\u00ebt tan\u00eb, ata k\u00ebrkuan nj\u00eb certifikat\u00eb t\u00eb re, na e l\u00ebshuan dhe sh\u00ebrbimi tani funksionon p\u00ebrs\u00ebri. Mund t\u00eb dukej se kjo \u00ebsht\u00eb e gjitha. Apo jo? N\u00eb fund t\u00eb fundit sh\u00ebrbimi funksionon, ai kryen nj\u00eb funksion t\u00eb caktuar q\u00eb i nevojitet biznesit ton\u00eb. Ne kemi disa standarde p\u00ebr zhvillimin e aplikacioneve, q\u00eb me siguri i keni edhe ju. P\u00ebr shembull, mos i ruani log-et n\u00eb nod n\u00eb dosje, por ruajini n\u00eb nj\u00eb magazin\u00eb, si Elasticsearch, dhe shikoni ato n\u00eb Kibana. Mund t\u00eb kujtojm\u00eb edhe metrikat e arta. K\u00ebshtu, ngarkesa n\u00eb sh\u00ebrbim, numri i k\u00ebrkesave n\u00eb sh\u00ebrbim, a \u00ebsht\u00eb ai aktiv apo jo, si kalon HealthCheck-un. T\u00eb pakt\u00ebn k\u00ebto metrika do t\u00eb ndihmojn\u00eb t\u00eb kuptoni se kur mund ta nxirrni at\u00eb me nj\u00eb nd\u00ebrgjegje t\u00eb qet\u00eb nga eksploatimi dhe ta harroni si nj\u00eb \u00ebnd\u00ebrr t\u00eb keqe.<\/p>\n

\u00c7far\u00eb t\u00eb b\u00ebjm\u00eb<\/h2>\n

\nPrandaj, ne e shtojm\u00eb k\u00ebt\u00eb sh\u00ebrbim t\u00eb vjet\u00ebr n\u00eb tabel\u00eb, dhe m\u00eb pas shkojm\u00eb t\u00eb k\u00ebrkojm\u00eb mes zhvilluesve vullnetar\u00eb q\u00eb do t\u00eb merren me sh\u00ebrbimin dhe do ta sjellin at\u00eb n\u00eb rend: do t\u00eb shkruajn\u00eb ndonj\u00eb informacion p\u00ebr sh\u00ebrbimin, do t\u00eb shtojn\u00eb lidhje n\u00eb dashboard-et n\u00eb Grafana, n\u00eb task-et e nd\u00ebrtimit, do t\u00eb kuptojn\u00eb si t\u00eb zhvillojn\u00eb aplikacionin, nuk duhet ta b\u00ebjn\u00eb at\u00eb manualisht duke hedhur skedar\u00eb p\u00ebrmes FTP. <\/p>\n

E r\u00ebnd\u00ebsishme \u00ebsht\u00eb \u2014 sa koh\u00eb do t\u00eb marr\u00eb kjo aktivitet i dobish\u00ebm vullnetar? Nj\u00eb sprint p\u00ebr nj\u00eb zhvillues mjaft t\u00eb p\u00ebrvojsh\u00ebm, p\u00ebr shembull, gjat\u00eb 20%-t\u00eb e borxhit teknik. Dhe sa koh\u00eb \u00ebsht\u00eb k\u00ebrkuar p\u00ebr t\u00eb kuptuar gjith\u00eb logjik\u00ebn e ngulitur p\u00ebr komunikimin me ndonj\u00eb sistem shtet\u00ebror, p\u00ebr ta sjell\u00eb at\u00eb n\u00eb teknologji m\u00eb t\u00eb reja? Nuk mund t\u00eb jap nj\u00eb garanci p\u00ebr k\u00ebt\u00eb, ndoshta nj\u00eb muaj, ndoshta edhe dy pun\u00eb ekipesh. K\u00ebt\u00eb e them nga p\u00ebrvoja e integrimit n\u00eb koh\u00ebn aktuale me ndonj\u00eb sh\u00ebrbim t\u00eb ri.<\/p>\n

Megjithat\u00eb, nuk ka ndonj\u00eb vler\u00eb biznesi nga kjo. Aspak. T\u00eb merrni sh\u00ebrbimin p\u00ebr mb\u00ebshtetje dhe t\u00eb shpenzoni pak koh\u00eb p\u00ebr k\u00ebt\u00eb \u2014 \u00ebsht\u00eb normale. Por pas standardeve tona t\u00eb zakonshme me sh\u00ebrbimin e shtuam at\u00eb n\u00eb tabel\u00eb, shtuam informacion p\u00ebr t\u00eb dhe, ndoshta, nj\u00eb dit\u00eb do ta riprogramojm\u00eb. Por tani ai p\u00ebrmbush standardet tona t\u00eb pun\u00ebs me sh\u00ebrbimet.<\/p>\n

Si p\u00ebrfundim, do t\u00eb doja t\u00eb arrija n\u00eb nj\u00eb plan p\u00ebr at\u00eb \u00e7far\u00eb t\u00eb b\u00ebjm\u00eb me sh\u00ebrbimet Legacy. <\/p>\n

T\u00eb riprogramosh heritage-n nga e para \u2014 \u00ebsht\u00eb nj\u00eb ide e keqe<\/b>
\nSeriozisht, mund t\u00eb mos mendoni fare p\u00ebr k\u00ebt\u00eb. \u00cbsht\u00eb e qart\u00eb q\u00eb do t\u00eb donim, dhe duket se ka disa p\u00ebrfitime, por zakonisht askujt nuk i nevojitet, p\u00ebrfshir\u00eb veten tuaj.<\/p>\n

Katalog<\/b>
\nG\u00ebrmoni kodet burimore t\u00eb aplikacioneve tuaja, krijoni nj\u00eb katalog ku do t\u00eb shpjegoni se \u00e7far\u00eb dhe ku ndodhet dhe si funksionon, gjithashtu p\u00ebrfshini p\u00ebrshkrimin e projektit (e th\u00ebn\u00eb ndryshe readme.md), p\u00ebr ta kuptuar shpejt se ku ndodhen log-\u00ebt dhe metrikat. Programuesi q\u00eb do t\u00eb merret me k\u00ebt\u00eb pas jush, vet\u00ebm do t'ju falenderoj\u00eb.<\/p>\n

Kuptoni domainin<\/b>
\nN\u00ebse keni ndonj\u00eb domain, p\u00ebrpiquni t\u00eb q\u00ebndroni mbi pulsin. Ting\u00ebllon banal, po, por jo t\u00eb gjith\u00eb kujdesen q\u00eb sh\u00ebrbimet t\u00eb jen\u00eb n\u00eb nj\u00eb nj\u00ebsi t\u00eb vetme. Punimi n\u00eb nj\u00eb standard n\u00eb t\u00eb v\u00ebrtet\u00eb \u00ebsht\u00eb m\u00eb i leht\u00eb.<\/p>\n

Vet\u00ebm p\u00ebrdoruesit e regjistruar mund t\u00eb marrin pjes\u00eb n\u00eb anket\u00eb. Hyni<\/a><\/noindex>, ju lutem.<\/p>\n

\u00c7far\u00eb po b\u00ebni me legacy tuaj?<\/h2>\n