{"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 legjend\u00eb n\u00eb infrastruktur\u00ebn tuaj","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"

P\u00ebrsh\u00ebndetje! Emri im \u00ebsht\u00eb Pasha Chernyak, un\u00eb jam zhvillues kryesor n\u00eb QIWI, dhe sot d\u00ebshiroj t\u00eb flas p\u00ebr di\u00e7ka t\u00eb pashmangshme. Rreth Legacy.<\/p>\n

Le t\u00eb fillojm\u00eb me nj\u00eb pyetje: \u00e7far\u00eb \u00ebsht\u00eb nj\u00eb sh\u00ebrbim Legacy? A \u00ebsht\u00eb nj\u00eb sh\u00ebrbim q\u00eb zhvilluesi nuk e ka prekur p\u00ebr nj\u00eb jav\u00eb\/muaj\/vit? Apo \u00ebsht\u00eb nj\u00eb sh\u00ebrbim q\u00eb u shkrua nga nj\u00eb programues m\u00eb pak t\u00eb eksperienc\u00ebs, si\u00e7 ishit ju, por nj\u00eb vit m\u00eb par\u00eb? Tani, ju jeni m\u00eb t\u00eb mir\u00eb dhe m\u00eb t\u00eb p\u00ebrvojsh\u00ebm. Apo ndoshta, sh\u00ebrbimi Legacy \u00ebsht\u00eb ai q\u00eb keni vendosur ta lini pa e prekur m\u00eb dhe po p\u00ebrgatiteni p\u00ebr ta z\u00ebvend\u00ebsuar ngadal\u00eb? N\u00eb \u00e7do rast, l\u00ebnia e nj\u00eb sh\u00ebrbimi t\u00eb till\u00eb pa mbik\u00ebqyrje dhe pa e p\u00ebrdit\u00ebsuar \u2014 \u00ebsht\u00eb nj\u00eb bomb\u00eb me koh\u00ebzgjatje, e cila mund t\u00eb shp\u00ebrthej\u00eb m\u00eb von\u00eb.<\/p>\n

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

Para se t\u00eb kalojm\u00eb tek m\u00ebnyra se si ne n\u00eb QIWI punojm\u00eb me sh\u00ebrbimet tona Legacy, do t'ju tregoj se si e rregulluam situat\u00ebn me sh\u00ebrbimet n\u00eb Portofolin. Ka dy vjet q\u00eb un\u00eb p\u00ebrgjigjem p\u00ebr funksionimin e tij. N\u00ebse ka ndonj\u00eb problem, gjithmon\u00eb m\u00eb telefonojn\u00eb mua s\u00eb pari. M\u00eb mungon zakonisht guximi p\u00ebr t'i telefonuar dikujt tjet\u00ebr n\u00eb or\u00ebn 11 t\u00eb mbr\u00ebmjes, prandaj kam qen\u00eb i detyruar t\u00eb ulem dhe t\u00eb kuptoj t\u00eb gjitha sh\u00ebrbimet e domainit ton\u00eb. <\/p>\n

Por ndonj\u00eb arsye, si \u00e7do njeri tjet\u00ebr, un\u00eb e dua t\u00eb flen\u00eb nat\u00ebn, prandaj p\u00ebrpiqesha t\u00eb kuptoja situat\u00ebn: \"Djem, pse m\u00eb telefononi?\". P\u00ebrgjigjja ishte e thjesht\u00eb: \"K\u00ebnd tjet\u00ebr?\". Sepse un\u00eb marr\u00eb n\u00eb dor\u00eb sh\u00ebrbimet, nd\u00ebrsa ata thjesht nuk din\u00eb se kujt t'i drejtohen.<\/p>\n

Prandaj, n\u00eb nj\u00eb nga retrospektivat e ekipit t\u00eb back-end t\u00eb Portofolit, vendos\u00ebm q\u00eb t\u00eb p\u00ebrgatitim nj\u00eb tabel\u00eb me list\u00ebn e sh\u00ebrbimeve tona, mikrosh\u00ebrbimeve dhe monoliteve t\u00eb portofolit, s\u00eb bashku me p\u00ebrgjegj\u00ebsit p\u00ebr to. Tabelat jan\u00eb gjithmon\u00eb t\u00eb dobishme, n\u00eb kufij t\u00eb arsyesh\u00ebm.
\n<\/a><\/noindex>
\nP\u00ebrve\u00e7 informacionit se kush \u00ebsht\u00eb p\u00ebrgjegj\u00ebs p\u00ebr \u00e7far\u00eb, aty kishte p\u00ebrgjigje p\u00ebr pyetje si: 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. Njer\u00ebzit p\u00ebrgjegj\u00ebs p\u00ebr k\u00ebt\u00eb sh\u00ebrbim jan\u00eb ata q\u00eb mund ta riparojn\u00eb at\u00eb n\u00eb rast nevoje. Pronari i sh\u00ebrbimit ka t\u00eb drejt\u00eb t\u00eb l\u00ebr\u00eb +2 n\u00eb komitet, nd\u00ebrsa p\u00ebrgjegj\u00ebsit duhet gjithmon\u00eb t\u00eb jen\u00eb t\u00eb pranish\u00ebm n\u00eb rishikim p\u00ebrpara se ky sh\u00ebrbim t\u00eb marr\u00eb nj\u00eb komitet t\u00eb ri.<\/p>\n

Koha kalonte, filluan t\u00eb aplikoheshin praktika t\u00eb reja, si migrimi n\u00eb Kubernetes, kontrollet checkstyle, spotbugs, ktlint, pranimi i logeve n\u00eb Kibana, autodiscovery e sh\u00ebrbimeve n\u00eb vend t\u00eb tregimit t\u00eb adresave direkt dhe shum\u00eb t\u00eb tjera. Dhe kudo tabela jon\u00eb lejonte t\u00eb mbante aktualitetin e sh\u00ebrbimeve tona. P\u00ebr ne, kjo \u00ebsht\u00eb nj\u00eb lloj liste kontrolli q\u00eb tregon q\u00eb kjo sh\u00ebrbim di t\u00eb b\u00ebj\u00eb k\u00ebt\u00eb, por p\u00ebr k\u00ebt\u00eb ende nuk \u00ebsht\u00eb. Por ne shkuam m\u00eb tej, duke kuptuar se na mungonte informacioni mbi sh\u00ebrbimet tona, p\u00ebr t\u00eb cilat ne mbajm\u00eb n\u00ebn v\u00ebzhgim, ku ndodhen kodet burimore t\u00eb sh\u00ebrbimit, ku startohen detyrat p\u00ebr nd\u00ebrtim n\u00eb TeamCity, si sh\u00ebrbehen ato, ku ruhen kodet burimor t\u00eb testeve end2end, fotografit\u00eb e arkitektur\u00ebs, p\u00ebr vendimet e marra. N\u00eb m\u00ebnyr\u00eb ideale, do t\u00eb doja q\u00eb gjith\u00eb ky informacion t\u00eb ishte diku i ruajtur dhe i thjesht\u00eb p\u00ebr t'u gjetur kur \u00ebsht\u00eb e nevojshme. Prandaj, tabela jon\u00eb u b\u00eb pika e nisjes p\u00ebr t\u00eb k\u00ebrkuar informacion.<\/p>\n

Por QIWI, ndon\u00ebse ruan frym\u00ebn e nj\u00eb startupi, \u00ebsht\u00eb nj\u00eb kompani e madhe. Ne jemi tashm\u00eb 12 vje\u00e7, dhe ekipet ndryshojn\u00eb: njer\u00ebzit largohen, njer\u00ebzit vijn\u00eb, formohen ekipe t\u00eb reja. Dhe ne kemi zbuluar n\u00eb domenin ton\u00eb disa sh\u00ebrbime, q\u00eb na jan\u00eb trash\u00ebguar. Disa erdh\u00ebn me zhvilluesit nga ekipe t\u00eb tjera, disa thjesht nd\u00ebrlidheshin n\u00eb nj\u00eb m\u00ebnyr\u00eb me Portofolin, prandaj sh\u00ebrbimi tani \u00ebsht\u00eb n\u00eb bilancin ton\u00eb. Pse t\u00eb merremi me ato q\u00eb funksionojn\u00eb dhe si funksionojn\u00eb? Sh\u00ebrbimi po punon dhe ne kemi karakteristika produktesh q\u00eb duhet patjet\u00ebr t\u00eb realizojm\u00eb.<\/p>\n

Si ndodh<\/h2>\n

\nPor nj\u00eb moment t\u00eb caktuar, e kuptojm\u00eb se sh\u00ebrbimi ka ndalur s\u00eb funksionuari, di\u00e7ka \u00ebsht\u00eb prishur \u2014 \u00e7far\u00eb t\u00eb b\u00ebjm\u00eb n\u00eb nj\u00eb situat\u00eb t\u00eb till\u00eb? Sh\u00ebrbimi ndaloi s\u00eb funksionuari. Plot\u00ebsisht. Dhe e m\u00ebsuam p\u00ebr k\u00ebt\u00eb, n\u00eb radh\u00eb t\u00eb par\u00eb, rast\u00ebsisht, dhe n\u00eb radh\u00eb t\u00eb dyt\u00eb, pas gjasht\u00eb muajsh. K\u00ebshtu ndodh. E vetmja gj\u00eb q\u00eb dinim ishte se n\u00eb cilat virtualka ishte vendosur sh\u00ebrbimi, ku ndodheshin kodet e tij burimore dhe asgj\u00eb m\u00eb tep\u00ebr. Ne b\u00ebjm\u00eb git clone dhe zhytim n\u00eb mendimet e atij q\u00eb e shkroi k\u00ebt\u00eb disa vite m\u00eb par\u00eb, por \u00e7far\u00eb shohim? Asnj\u00eb Spring Boot t\u00eb zakonsh\u00ebm p\u00ebr ne, pavar\u00ebsisht se jemi m\u00ebsuar me gjith\u00e7ka, ne jemi full stack dhe di\u00e7ka t\u00eb till\u00eb. Nd\u00ebrsa, ndoshta, \u00ebsht\u00eb aty Spring Framework? Por ja q\u00eb nuk \u00ebsht\u00eb.<\/p>\n

Djali q\u00eb shkruante gjith\u00e7ka ishte i ashp\u00ebr dhe shkruante gjith\u00e7ka n\u00eb Java t\u00eb past\u00ebr. Nuk ka mjete t\u00eb zakonshme p\u00ebr zhvilluesit, dhe lind ideja \u2014 duhet t\u00eb rikodojm\u00eb gjith\u00e7ka. Ne kemi mikrosh\u00ebrbime, dhe nga \u00e7do tostier\u00eb vjen deklarata e zakonshme \"Djem, mikrosh\u00ebrbimet jan\u00eb ato q\u00eb ju duhen!\". N\u00ebse ndodhi ndonj\u00eb gj\u00eb e keqe, do t\u00eb merrni qet\u00ebsisht \u00e7far\u00ebdo gjuhe dhe gjith\u00e7ka do t\u00eb shkoj\u00eb p\u00ebr mrekulli.<\/p>\n

Problemi \u00ebsht\u00eb se tani 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

Dhe tani, sa e leht\u00eb \u00ebsht\u00eb t\u00eb riprogramosh sh\u00ebrbimin pa e ditur k\u00ebrkesat e tij biznesore? Si logaritet sh\u00ebrbimi, ka metrika - kjo \u00ebsht\u00eb e panjohur. Cilat jan\u00eb ato, n\u00ebse ekzistojn\u00eb - kjo \u00ebsht\u00eb gjithashtu e panjohur. Dhe p\u00ebr m\u00eb tep\u00ebr, n\u00eb sh\u00ebrbim ka nj\u00eb num\u00ebr t\u00eb madh klasash me logjik\u00eb biznesi t\u00eb paqart\u00eb. Di\u00e7ka hyn n\u00eb nj\u00eb baz\u00eb t\u00eb dh\u00ebnash, p\u00ebr t\u00eb cil\u00ebn ne gjithashtu nuk dim\u00eb asgj\u00eb akoma. <\/p>\n

Nga t\u00eb fillojm\u00eb?<\/h2>\n

\nNga gj\u00ebja m\u00eb logjike - prania e testeve. Aty zakonisht \u00ebsht\u00eb shkruar ndonj\u00eb logjik\u00eb dhe mund t\u00eb nxirren p\u00ebrfundime mbi at\u00eb q\u00eb po ndodh. Tani \u00ebsht\u00eb n\u00eb mod\u00eb TDD, por ne shohim q\u00eb edhe 5 vjet m\u00eb par\u00eb ishte pothuajse ashtu si tani: testet unit jan\u00eb gati t\u00eb pa ekzistueshme, dhe ato nuk do t'na tregojn\u00eb asgj\u00eb n\u00eb m\u00ebnyr\u00eb t\u00eb sakt\u00eb. T\u00eb pakt\u00ebn, p\u00ebrve\u00e7 ndonj\u00eb kontrolli, si n\u00ebnshkruhet nj\u00eb xml me ndonj\u00eb certifikat\u00eb t\u00eb personalizuar.<\/p>\n

Nga kodi nuk arrit\u00ebm t\u00eb kuptonim asgj\u00eb, dhe ne e shikuam virtualen. Hap\u00ebm logjet e sh\u00ebrbimit dhe gjet\u00ebm nj\u00eb gabim t\u00eb HTTP klientit, nj\u00eb certificat vet\u00eb-n\u00ebnshkruar q\u00eb ishte inkorporuar n\u00eb burimet e aplikacionit, ishte shkat\u00ebrruar pa m\u00ebshir\u00eb. Kemi kontaktuar analist\u00ebt tan\u00eb, ata k\u00ebrkuan nj\u00eb certificat t\u00eb ri, ne e mor\u00ebm at\u00eb dhe sh\u00ebrbimi p\u00ebrs\u00ebri funksionon. Mund t\u00eb duket sikur kjo \u00ebsht\u00eb e gjitha. Apo jo? Megjithat\u00eb, sh\u00ebrbimi funksionon, ai realizon nj\u00eb funksion t\u00eb caktuar q\u00eb i nevojitet biznesit ton\u00eb. Kemi disa standarde p\u00ebr zhvillimin e aplikacioneve, t\u00eb cilat me siguri i keni edhe ju. P\u00ebr shembull, t\u00eb mos ruajm\u00eb logjet n\u00eb nod\u00eb n\u00eb nj\u00eb dosje, por t'i ruajm\u00eb n\u00eb nj\u00eb depo, si elastic, p\u00ebr t'i par\u00eb ato n\u00eb Kibana. Mund t\u00eb p\u00ebrmendim edhe metrikat e arta. K\u00ebshtu, ngarkesa mbi sh\u00ebrbim, numri i k\u00ebrkesave mbi sh\u00ebrbim, n\u00ebse \u00ebsht\u00eb aktiv apo jo, si kalon kontrollin sh\u00ebndet\u00ebsor. T\u00eb pakt\u00ebn, k\u00ebto metrika do t\u00eb ndihmojn\u00eb t\u00eb kuptojm\u00eb kur mund ta \u00e7elim at\u00eb me nj\u00eb nd\u00ebrgjegje t\u00eb qet\u00eb dhe ta harrojm\u00eb si nj\u00eb makth t\u00eb keq.<\/p>\n

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

\nPrandaj ne e shtojm\u00eb nj\u00eb sh\u00ebrbim kaq t\u00eb vjet\u00ebr n\u00eb tabel\u00eb, dhe pastaj shkojm\u00eb t\u00eb k\u00ebrkojm\u00eb nga zhvilluesit vullnetar\u00eb q\u00eb t\u00eb merren me sh\u00ebrbimin dhe ta sjellin at\u00eb n\u00eb form\u00eb: t\u00eb shkruajn\u00eb ndonj\u00eb informacion p\u00ebr sh\u00ebrbimin, t\u00eb shtojn\u00eb lidhje p\u00ebr tabelat n\u00eb Grafana, p\u00ebr detyrat e nd\u00ebrtimit, t\u00eb kuptojn\u00eb se si t\u00eb \u00e7elni aplikacionin, nuk \u00ebsht\u00eb e arsyeshme t\u00eb ngarkoni skedar\u00ebt me dor\u00eb p\u00ebrmes FTP-s\u00eb. <\/p>\n

E r\u00ebnd\u00ebsishme \u00ebsht\u00eb sa koh\u00eb do t\u00eb marr\u00eb e gjith\u00eb kjo aktivitet vullnetar i dobish\u00ebm? Nj\u00eb sprint p\u00ebr nj\u00eb zhvillues m\u00eb shum\u00eb ose m\u00eb pak t\u00eb aft\u00eb, p\u00ebr shembull, gjat\u00eb 20%-it t\u00eb borxhit teknik. Dhe sa koh\u00eb u desh p\u00ebr t\u00eb kuptuar gjith\u00eb logjik\u00ebn e thell\u00eb lidhur me komunikimin me ndonj\u00eb sistem shtet\u00ebror, p\u00ebr ta \u00e7uar at\u00eb n\u00eb teknologji m\u00eb t\u00eb reja? Nuk jam i sigurt, ndoshta nj\u00eb muaj, ndoshta edhe dy pun\u00eb ekipore. K\u00ebt\u00eb e them sipas p\u00ebrvoj\u00ebs s\u00eb integrimit aktual me ndonj\u00eb sh\u00ebrbim t\u00eb ri.<\/p>\n

Megjithat\u00eb, nuk ka ndonj\u00eb vler\u00eb p\u00ebr biznesin - asnj\u00eb. Fare. T\u00eb marr\u00ebsh sh\u00ebrbimin n\u00eb mb\u00ebshtetje dhe t\u00eb shpenzosh pak koh\u00eb p\u00ebr t\u00eb \u00ebsht\u00eb normale. Por pas standardeve tona t\u00eb sh\u00ebrbimit, e kemi shtuar at\u00eb n\u00eb tabel\u00eb, kemi shtuar informacion p\u00ebr t\u00eb dhe ndoshta nj\u00eb dit\u00eb do ta rind\u00ebrtojm\u00eb. Por tani, ai p\u00ebrmbush standardet tona p\u00ebr pun\u00ebn e sh\u00ebrbimeve.<\/p>\n

Si pasoj\u00eb, do doja t\u00eb \u00e7oja n\u00eb nj\u00eb plan se \u00e7far\u00eb t\u00eb b\u00ebjm\u00eb me sh\u00ebrbimet Legacy. <\/p>\n

Rind\u00ebrtimi i legacy nga fillimi \u00ebsht\u00eb nj\u00eb ide e keqe.<\/b>
\nSeriozisht, madje as nuk duhet ta mendoni k\u00ebt\u00eb. E qart\u00eb q\u00eb do t\u00eb d\u00ebshironit dhe duken disa p\u00ebrfitime, por zakonisht askush nuk ka nevoj\u00eb p\u00ebr t\u00eb, duke p\u00ebrfshir\u00eb veten tuaj.<\/p>\n

Katalogu<\/b>
\nGjeni kodet burimore t\u00eb aplikacioneve tuaja, b\u00ebni nj\u00eb katalog n\u00eb t\u00eb cilin do t\u00eb tregoni se \u00e7far\u00eb dhe ku ndodhet dhe si funksionon, gjithashtu shkruani p\u00ebrshkrimin e projektit (si nj\u00eb readme.md) p\u00ebr t\u00eb kuptuar shpejt se ku ndodhen log-et dhe metrikat. Programuesi q\u00eb do t\u00eb merret me k\u00ebt\u00eb pas jush do t'i thot\u00eb faleminderit.<\/p>\n

Kuptoni domenin<\/b>
\nN\u00ebse keni ndonj\u00eb domen, p\u00ebrpiquni ta mbani dor\u00ebn mbi puls. Duket klishe, por jo t\u00eb gjith\u00eb i kushtojn\u00eb v\u00ebmendje q\u00eb sh\u00ebrbimet t\u00eb jen\u00eb n\u00eb nj\u00eb linj\u00eb. Dhe n\u00eb t\u00eb v\u00ebrtet\u00eb, t\u00eb punosh n\u00eb nj\u00eb standard \u00ebsht\u00eb ndjesh\u00ebm m\u00eb e leht\u00eb.<\/p>\n

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

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