{"id":38981,"date":"2019-10-31T22:27:10","date_gmt":"2019-10-31T19:27:10","guid":{"rendered":"https:\/\/prohoster.info\/blog\/servisy-siroty-obratnaya-storona-mikro-servisnoj-arhitektury\/"},"modified":"2019-10-31T22:27:10","modified_gmt":"2019-10-31T19:27:10","slug":"servisy-siroty-obratnaya-storona-mikro-servisnoj-arhitektury","status":"publish","type":"post","link":"https:\/\/prohoster.info\/sq\/blog\/administrirovanie\/servisy-siroty-obratnaya-storona-mikro-servisnoj-arhitektury","title":{"rendered":"Sh\u00ebrbime-origjin\u00eb: Ana tjet\u00ebr e arkitektur\u00ebs (mikro) sh\u00ebrbimore","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"

Drejtori i operacioneve t\u00eb portalit Banki.ru, Andrei Nikolsky, foli n\u00eb konferenc\u00ebn e vitit t\u00eb kaluar DevOpsDays Moscow<\/a><\/noindex> p\u00ebr sh\u00ebrbimet jetim\u00eb: si t\u00eb identifikoni nj\u00eb jetim n\u00eb infrastruktur\u00eb, \u00e7far\u00eb jan\u00eb t\u00eb k\u00ebqija sh\u00ebrbimet jetim\u00eb, \u00e7far\u00eb t\u00eb b\u00ebni me to dhe si t\u00eb veproni n\u00ebse asgj\u00eb nuk ndihmon.<\/p>\n

Posht\u00eb \u00ebsht\u00eb versione tekstuale e raportit. <\/p>\n

\r\n \"Luaj\r\n
<\/div>\r\n <\/div><\/center><\/a><\/noindex>
\nP\u00ebrsh\u00ebndetje koleg\u00eb! Emri im \u00ebsht\u00eb Andrei, udh\u00ebheq operacionet n\u00eb kompanin\u00eb Banki.ru.<\/p>\n

Ne kemi sh\u00ebrbime t\u00eb m\u00ebdha, kjo \u00ebsht\u00eb si monolitsh\u00ebrbime, kemi sh\u00ebrbime n\u00eb nj\u00eb kuptim m\u00eb klasik, dhe kemi t\u00eb vogla t\u00ebr\u00ebsisht. N\u00eb terminologjin\u00eb time t\u00eb pun\u00ebs, them q\u00eb n\u00ebse nj\u00eb sh\u00ebrbim \u00ebsht\u00eb i thjesht\u00eb dhe i vog\u00ebl, at\u00ebher\u00eb ai \u00ebsht\u00eb mikro, dhe n\u00ebse ai nuk \u00ebsht\u00eb shum\u00eb i thjesht\u00eb dhe nuk \u00ebsht\u00eb i vog\u00ebl, at\u00ebher\u00eb ai \u00ebsht\u00eb thjesht nj\u00eb sh\u00ebrbim. <\/p>\n

Pikat pozitive t\u00eb sh\u00ebrbimeve<\/b><\/h3>\n

\nDo t\u00eb kaloj shpejt mbi pikat pozitive t\u00eb sh\u00ebrbimeve. <\/p>\n

\"Sh\u00ebrbime-origjin\u00eb:
\n
\nE para \u2014 shkall\u00ebzimi. Mund t\u00eb b\u00ebni di\u00e7ka shpejt n\u00eb sh\u00ebrbim dhe t\u00eb nisni n\u00eb prodhim. Ju erdh\u00ebn trafiku, e klonuat sh\u00ebrbimin. Ju erdh\u00ebn edhe m\u00eb shum\u00eb trafik, e klonuat p\u00ebrs\u00ebri dhe me k\u00ebt\u00eb jetoni. Ky \u00ebsht\u00eb nj\u00eb bonus i shk\u00eblqyer, dhe, n\u00eb thelb, kur filluam, ai konsiderohej nga ne si m\u00eb i r\u00ebnd\u00ebsishmi, p\u00ebrse e b\u00ebjm\u00eb t\u00eb gjith\u00eb k\u00ebt\u00eb.<\/p>\n

\"Sh\u00ebrbime-origjin\u00eb:
\n
\nN\u00eb t\u00eb dyt\u00ebn, zhvillimi i izoluar, kur keni disa ekipe zhvillimi, disa zhvillues t\u00eb ndrysh\u00ebm n\u00eb \u00e7do ekip, dhe \u00e7do ekip punon p\u00ebr sh\u00ebrbimin e vet.<\/p>\n

Ka nj\u00eb nuanc\u00eb me ekipet. Zhvilluesit jan\u00eb t\u00eb ndrysh\u00ebm. Disa jan\u00eb, p\u00ebr shembull, njer\u00ebz t\u00eb ve\u00e7ant\u00eb<\/a><\/noindex>. E kam par\u00eb p\u00ebr her\u00eb t\u00eb par\u00eb tek Maksim Dorofeev. Ndonj\u00ebher\u00eb njer\u00ebzit e ve\u00e7ant\u00eb jan\u00eb n\u00eb disa ekipe, nd\u00ebrsa n\u00eb disa t\u00eb tjera nuk jan\u00eb. Kjo e b\u00ebn sh\u00ebrbimet e ndryshme q\u00eb p\u00ebrdoren n\u00eb kompani paksa t\u00eb papajtueshme. <\/p>\n

\"Sh\u00ebrbime-origjin\u00eb:
\n
\nShikoni k\u00ebt\u00eb imazh: ky \u00ebsht\u00eb nj\u00eb zhvillues i mir\u00eb, ka duar t\u00eb m\u00ebdha, mund t\u00eb b\u00ebj\u00eb shum\u00eb. Problemi kryesor \u00ebsht\u00eb se nga e kan\u00eb k\u00ebto duar. <\/p>\n

\"Sh\u00ebrbime-origjin\u00eb:
\n
\nSh\u00ebrbimet ofrojn\u00eb mund\u00ebsin\u00eb p\u00ebr t\u00eb p\u00ebrdorur gjuh\u00eb t\u00eb ndryshme programimi, m\u00eb t\u00eb p\u00ebrshtatshme p\u00ebr detyra t\u00eb ndryshme. Disa sh\u00ebrbime n\u00eb Go, disa n\u00eb Erlang, disa n\u00eb Ruby, disa n\u00eb PHP, disa n\u00eb Python. N\u00eb p\u00ebrgjith\u00ebsi, mund t\u00eb zhvilloni nj\u00eb shum\u00ebllojshm\u00ebri t\u00eb gjer\u00eb. K\u00ebtu gjithashtu ka nuanca.<\/p>\n

\"Sh\u00ebrbime-origjin\u00eb:
\n
\nArkitektura e orientuar nga sh\u00ebrbimet \u2014 p\u00ebr t\u00eb gjith\u00eb befasin\u00eb e devops. K\u00ebshtu q\u00eb, n\u00ebse nuk keni automatizim, nuk keni proces deploji, dhe n\u00ebse konfigurimet tuaja ndryshojn\u00eb nga instanca n\u00eb instanc\u00eb manualisht, ju ndiheni si n\u00eb ferr. <\/p>\n

P\u00ebr shembull, n\u00ebse keni 20 sh\u00ebrbime dhe duhet t'i depiloni manualisht, do t\u00eb keni 20 konsola, duke shtypur \u00abenter\u00bb n\u00eb t\u00eb nj\u00ebjt\u00ebn koh\u00eb si ninja. Kjo nuk \u00ebsht\u00eb shum\u00eb mir\u00eb. <\/p>\n

N\u00ebse sh\u00ebrbimi juaj ka kaluar testimin (n\u00ebse ka testim, natyrisht), dhe duhet ta p\u00ebrmir\u00ebsoni q\u00eb t\u00eb funksionoj\u00eb n\u00eb prodhim, kam edhe disa lajme t\u00eb k\u00ebqija p\u00ebr ju. <\/p>\n

N\u00ebse mb\u00ebshteteni n\u00eb sh\u00ebrbime specifike t\u00eb Amazonit dhe punoni n\u00eb Rusi, at\u00ebher\u00eb dy muaj m\u00eb par\u00eb, ndoshta keni th\u00ebn\u00eb: \u00abT\u00eb gjitha rreth meje po digjen, un\u00eb jam mir\u00eb, gjith\u00e7ka \u00ebsht\u00eb shk\u00eblqyese\u00bb.<\/p>\n

\"Sh\u00ebrbime-origjin\u00eb:
\n
\nNe p\u00ebrdorim Ansible p\u00ebr automatizimin e nd\u00ebrtimit, Puppet p\u00ebr ngushtimin, Bamboo p\u00ebr automatizimin e depolit, dhe Confluence p\u00ebr t\u00eb gjitha k\u00ebto dokumentuar disi.<\/p>\n

Nuk do t\u00eb ndalem n\u00eb k\u00ebt\u00eb tem\u00eb sepse prezantimi \u00ebsht\u00eb m\u00eb shum\u00eb rreth praktikave t\u00eb bashk\u00ebpunimit dhe jo p\u00ebr realizimin teknik. <\/p>\n

\"Sh\u00ebrbime-origjin\u00eb:
\n
\nNj\u00eb her\u00eb kemi pasur probleme, ku Puppet n\u00eb server punon me Ruby 2, nd\u00ebrsa nj\u00eb aplikacion \u00ebsht\u00eb shkruar p\u00ebr Ruby 1.8, dhe ata nuk funksionojn\u00eb s\u00eb bashku. Ndodhin disa probleme. Kur ju nevojitet t\u00eb mbani disa versione t\u00eb Ruby n\u00eb nj\u00eb makin\u00eb, zakonisht filloni t\u00eb hasni probleme. <\/p>\n

Ne, p\u00ebr shembull, japim nj\u00eb ambient p\u00ebr \u00e7do zhvillues, ku ka p\u00ebraf\u00ebrsisht gjith\u00e7ka q\u00eb kemi, t\u00eb gjitha sh\u00ebrbimet q\u00eb mund t\u00eb zhvillohen, n\u00eb m\u00ebnyr\u00eb q\u00eb ai t\u00eb ket\u00eb nj\u00eb ambient t\u00eb izoluar, ku mund t\u00eb b\u00ebj\u00eb eksperimente dhe ta nd\u00ebrtoj\u00eb ashtu si\u00e7 d\u00ebshiron. <\/p>\n

Ndonj\u00ebher\u00eb, nevojitet ndonj\u00eb paket\u00eb e p\u00ebrpiluar posa\u00e7\u00ebrisht me mb\u00ebshtetje p\u00ebr di\u00e7ka t\u00eb ve\u00e7ant\u00eb. Kjo \u00ebsht\u00eb mjaft e komplikuar. D\u00ebgjova nj\u00eb prezantim ku nj\u00eb imazh Docker ka pesh\u00eb 45 GB. N\u00eb Linux \u00ebsht\u00eb pak m\u00eb e leht\u00eb, \u00ebsht\u00eb m\u00eb pak, por p\u00ebr t\u00eb gjitha raste, nuk do t\u00eb ket\u00eb vend t\u00eb mjaftuesh\u00ebm. <\/p>\n

Po ashtu, hasen var\u00ebsi kontradiktore, kur nj\u00eb pjes\u00eb e projektit varet nga nj\u00eb bibliotek\u00eb me nj\u00eb version, nd\u00ebrsa nj\u00eb pjes\u00eb tjet\u00ebr nga nj\u00eb version tjet\u00ebr, dhe bibliotekat nuk instalohen dot s\u00eb bashku. <\/p>\n

\"Sh\u00ebrbime-origjin\u00eb:
\n
\nKemi faqet dhe sh\u00ebrbimet n\u00eb PHP 5.6, na vjen turp p\u00ebr to, por \u00e7far\u00eb mund t\u00eb b\u00ebjm\u00eb. Kjo \u00ebsht\u00eb nj\u00eb platform\u00eb e p\u00ebrbashk\u00ebt p\u00ebr ne. Kemi fqinj\u00eb dhe sh\u00ebrbime n\u00eb PHP 7, m\u00eb shum\u00eb se ato, p\u00ebr to nuk ndiejm\u00eb turp. Dhe \u00e7do zhvillues ka baz\u00ebn e tij, ku ai g\u00ebzohet q\u00eb punon. <\/p>\n

N\u00ebse shkruani n\u00eb kompani n\u00eb nj\u00eb gjuh\u00eb, at\u00ebher\u00eb tre virtuale p\u00ebr zhvilluesin ting\u00ebllojn\u00eb normal. N\u00ebse keni gjuh\u00eb t\u00eb ndryshme programimi, situata b\u00ebhet m\u00eb e komplikuar.<\/p>\n

\"Sh\u00ebrbime-origjin\u00eb:
\n
\nJu shfaqen faqet dhe sh\u00ebrbimet n\u00eb k\u00ebt\u00eb gjuh\u00eb, n\u00eb k\u00ebt\u00eb tjet\u00ebr, pastaj nj\u00eb platform\u00eb p\u00ebr Go, nj\u00eb tjet\u00ebr p\u00ebr Ruby, ndonj\u00eb Redis m\u00eb vete. E gjith\u00eb kjo p\u00ebrfundon si nj\u00eb fush\u00eb e madhe p\u00ebr mb\u00ebshtetje, dhe gjithnj\u00eb di\u00e7ka nga k\u00ebto mund t\u00eb prishet.<\/p>\n

\"Sh\u00ebrbime-origjin\u00eb:
\n
\nPrandaj ne z\u00ebvend\u00ebsuam mund\u00ebsit\u00eb e gjuh\u00ebs s\u00eb programimit me p\u00ebrdorimin e framework-\u00ebve t\u00eb ndrysh\u00ebm, sepse framework-\u00ebt n\u00eb PHP jan\u00eb mjaft t\u00eb ndrysh\u00ebm, ata kan\u00eb mund\u00ebsi t\u00eb ndryshme, komunitete t\u00eb ndryshme, mb\u00ebshtetje t\u00eb ndryshme. Dhe mund t\u00eb shkruani nj\u00eb sh\u00ebrbim n\u00eb m\u00ebnyr\u00eb q\u00eb t\u00eb keni di\u00e7ka t\u00eb gatshme p\u00ebr t\u00eb. <\/p>\n

\u00c7do sh\u00ebrbim ka ekipin e tij<\/b><\/h3>\n

\n\"Sh\u00ebrbime-origjin\u00eb:
\n
\nAvantazhi yn\u00eb kryesor, i cili \u00ebsht\u00eb kristalizuar gjat\u00eb disa viteve, \u00ebsht\u00eb se \u00e7do sh\u00ebrbim ka ekipin e tij. Kjo \u00ebsht\u00eb e p\u00ebrshtatshme p\u00ebr projekte t\u00eb m\u00ebdha dhe mund t\u00eb kursej\u00eb koh\u00eb n\u00eb dokumentim, menaxher\u00ebt e njohin mir\u00eb projektin e tyre. <\/p>\n

Detyrat nga mb\u00ebshtetja mund t\u00eb shp\u00ebrndahen leht\u00ebsisht. P\u00ebr shembull, n\u00ebse sh\u00ebrbimi i sigurimeve ka probleme. Menj\u00ebher\u00eb ekipi q\u00eb merret me sigurimet do t\u00eb shkoj\u00eb p\u00ebr ta riparuar. <\/p>\n

Tipare t\u00eb reja realizohen shpejt, sepse kur keni nj\u00eb sh\u00ebrbim t\u00eb atomar, mund t\u00eb integjoni di\u00e7ka operativisht brenda tij. <\/p>\n

Dhe kur e prisni sh\u00ebrbimin tuaj, gj\u00eb q\u00eb ndodh padyshim, nuk e preken sh\u00ebrbimet e t\u00eb tjer\u00ebve; zhvilluesit nga ekipet e tjera nuk ju vijn\u00eb me shkopinj dhe nuk thon\u00eb: 'Ah, ah, jo k\u00ebshtu'. <\/p>\n

\"Sh\u00ebrbime-origjin\u00eb:
\n
\nSi gjithmon\u00eb, ka nuanca. Ne kemi ekipe t\u00eb stabilizuara, menaxher\u00ebt jan\u00eb fort t\u00eb lidhur me ekipin. Ka dokumente t\u00eb qarta, menaxher\u00ebt e mbik\u00ebqyrin k\u00ebt\u00eb proces ngusht\u00ebsisht. \u00c7do ekip me menaxherin ka disa sh\u00ebrbime dhe ka nj\u00eb pik\u00eb t\u00eb sakt\u00eb t\u00eb kompetenc\u00ebs. <\/p>\n

N\u00ebse ekipet jan\u00eb t\u00eb l\u00ebvizshme (kjo p\u00ebrdoret ndonj\u00ebher\u00eb), ka nj\u00eb metod\u00eb t\u00eb mir\u00eb q\u00eb quhet 'harta yjore'.<\/p>\n

\"Sh\u00ebrbime-origjin\u00eb:
\n
\nJu keni nj\u00eb list\u00eb sh\u00ebrbimesh dhe njer\u00ebzish. Ylli do t\u00eb thot\u00eb se personi \u00ebsht\u00eb ekspert n\u00eb k\u00ebt\u00eb sh\u00ebrbim, nd\u00ebrsa libri do t\u00eb thot\u00eb se personi po studion k\u00ebt\u00eb sh\u00ebrbim. Detyra e personit \u00ebsht\u00eb t\u00eb marr\u00eb librin dhe ta kthej\u00eb n\u00eb yll. N\u00ebse p\u00ebrkundrejt sh\u00ebrbimit nuk ka asgj\u00eb t\u00eb shkruar, at\u00ebher\u00eb fillojn\u00eb problemet, p\u00ebr t\u00eb cilat do t\u00eb flas m\u00eb von\u00eb. <\/p>\n

Si shfaqen sh\u00ebrbimet jetim\u00eb?<\/b><\/h3>\n

\n\"Sh\u00ebrbime-origjin\u00eb:
\n
\nProblemi i par\u00eb, m\u00ebnyra e par\u00eb p\u00ebr t\u00eb pasur nj\u00eb sh\u00ebrbim jetim n\u00eb infrastruktur\u00ebn tuaj \u2014 \u00ebsht\u00eb largimi i njer\u00ebzve. A ka ndodhur ndonj\u00ebher\u00eb q\u00eb afatet t\u00eb vijn\u00eb n\u00eb biznes para se t\u00eb vler\u00ebsohen detyrat? Nd sometimes ndodhin her\u00eb q\u00eb afatet jan\u00eb t\u00eb ngurta dhe nuk ka koh\u00eb p\u00ebr dokumentacionin. \"Duhet ta dor\u00ebzojm\u00eb sh\u00ebrbimin n\u00eb prodhim, pastaj do ta shkruajm\u00eb m\u00eb tej.\" <\/p>\n

N\u00ebse ekipi \u00ebsht\u00eb i vog\u00ebl, ndonj\u00ebher\u00eb ndodh q\u00eb n\u00eb t\u00eb ket\u00eb nj\u00eb zhvillues i cili shkruan gjith\u00e7ka, t\u00eb tjer\u00ebt jan\u00eb n\u00eb mb\u00ebshtetje. \"Un\u00eb kam shkruar arkitektur\u00ebn baz\u00eb, ti tani l\u00ebr\u00ebs interface-t\u00eb.\" Pastaj n\u00eb nj\u00eb moment, p\u00ebr shembull, menaxheri ik\u00ebn. Dhe n\u00eb k\u00ebt\u00eb periudh\u00eb, kur menaxheri ka ikur dhe nuk \u00ebsht\u00eb em\u00ebruar nj\u00eb i ri, zhvilluesit vet\u00eb vendosin se n\u00eb cilin drejtim shkon sh\u00ebrbimi, \u00e7far\u00eb ndodh. Dhe si\u00e7 e dim\u00eb (kthehemi disa diapozitiva mbrapa), n\u00eb disa ekipe ka njer\u00ebz t\u00eb ve\u00e7ant\u00eb, ndonj\u00ebher\u00eb nj\u00eb lider ekipi i till\u00eb. Pastaj ai jep dor\u00ebheqjen, dhe ne marrim nj\u00eb sh\u00ebrbim jetim. <\/p>\n

\"Sh\u00ebrbime-origjin\u00eb:
\n
\nN\u00eb t\u00eb nj\u00ebjt\u00ebn koh\u00eb, detyrat nga mb\u00ebshtetje dhe nga biznesi nuk zhduken, ato mbeten n\u00eb bllokun e pun\u00ebve. N\u00ebse gjat\u00eb zhvillimit t\u00eb sh\u00ebrbimit ka pasur ndonj\u00eb gabim arkitekturor, ato gjithashtu mbeten n\u00eb bllokun e pun\u00ebve. Sh\u00ebrbimi po degradon ngadal\u00eb. <\/p>\n

Si ta identifikosh nj\u00eb jetim?<\/b> <\/h3>\n

\nKy list e p\u00ebrshkruan mir\u00eb situat\u00ebn. Kush ka gjetur ndonj\u00eb gj\u00eb n\u00eb infrastruktur\u00ebn e vet?<\/p>\n

\"Sh\u00ebrbime-origjin\u00eb:
\n
\nP\u00ebr workaround t\u00eb dokumentuar: ka nj\u00eb sh\u00ebrbim dhe, n\u00eb p\u00ebrgjith\u00ebsi, ai funksionon, ai ka nj\u00eb manual me dy faqe p\u00ebr si t\u00eb punosh me t\u00eb, por si funksionon brenda, askush nuk e di. <\/p>\n

Ose, p.sh., ka ndonj\u00eb shkurtes\u00eb t\u00eb lidhjeve. Ne, p\u00ebr shembull, tani kemi n\u00eb p\u00ebrdorim tre shkurtesa lidhjesh p\u00ebr q\u00ebllime t\u00eb ndryshme n\u00eb sh\u00ebrbime t\u00eb ndryshme. K\u00ebto jan\u00eb pasojat e k\u00ebtij procesi. <\/p>\n

\"Sh\u00ebrbime-origjin\u00eb:
\n
\nTani do t\u00eb jem kapiteni i evident\u00ebs. \u00c7far\u00eb duhet t\u00eb b\u00ebni? S\u00eb pari, duhet ta kaloni sh\u00ebrbimin te nj\u00eb menaxher tjet\u00ebr, nj\u00eb ekip tjet\u00ebr. N\u00ebse lideri i ekipit tuaj nuk \u00ebsht\u00eb pushuar ende, at\u00ebher\u00eb n\u00eb k\u00ebt\u00eb ekip tjet\u00ebr, kur e kuptoni se sh\u00ebrbimi \u00ebsht\u00eb si nj\u00eb jetim, duhet t\u00eb p\u00ebrfshini dik\u00eb q\u00eb e kupton di\u00e7ka n\u00eb t\u00eb. <\/p>\n

Gj\u00ebrat kryesore: ju duhet t\u00eb keni procedura t\u00eb shkruara me gjak p\u00ebr kalimin e sh\u00ebrbimit. N\u00eb rastin ton\u00eb, k\u00ebshtu e ndjek zakonisht un\u00eb, sepse m\u00eb duhet q\u00eb gjith\u00e7ka t\u00eb funksionoj\u00eb. Menaxher\u00ebt duan q\u00eb kjo t\u00eb dor\u00ebzohet shpejt, dhe \u00e7far\u00eb do t\u00eb ndodh\u00eb me t\u00eb pas k\u00ebsaj, nuk \u00ebsht\u00eb kaq e r\u00ebnd\u00ebsishme p\u00ebr ta. <\/p>\n

\"Sh\u00ebrbime-origjin\u00eb:
\n
\nNj\u00eb m\u00ebnyr\u00eb tjet\u00ebr p\u00ebr ta b\u00ebr\u00eb nj\u00eb sh\u00ebrbim jetim \u00ebsht\u00eb: \"Do ta b\u00ebjm\u00eb n\u00eb aoutsourcing, k\u00ebshtu do t\u00eb jet\u00eb m\u00eb shpejt, dhe m\u00eb pas do ta kalojm\u00eb n\u00eb ekip.\" \u00cbsht\u00eb e qart\u00eb se t\u00eb gjith\u00eb kan\u00eb ndonj\u00eb plan n\u00eb ekip, radh\u00eb. Shpesh klienti biznesor mendon se n\u00eb aoutsourcing do t\u00eb b\u00ebjn\u00eb ashtu si\u00e7 b\u00ebn ekipi teknik q\u00eb \u00ebsht\u00eb n\u00eb kompanin\u00eb. Megjithat\u00eb, motivator\u00ebt e tyre jan\u00eb t\u00eb ndrysh\u00ebm. N\u00eb aoutsourcing ndodhin zgjidhje teknologjike t\u00eb \u00e7uditshme dhe zgjidhje algoritmike t\u00eb \u00e7uditshme.<\/p>\n

\"Sh\u00ebrbime-origjin\u00eb:
\n
\nP\u00ebr shembull, ne kishim nj\u00eb sh\u00ebrbim ku Sphinx ishte n\u00eb vende t\u00eb ndryshme t\u00eb papritura. M\u00eb von\u00eb do t\u00eb tregoj se \u00e7far\u00eb duhej t\u00eb b\u00ebja. <\/p>\n

Te outsourcer-\u00ebt ndodhin framework-e t\u00eb shkruara vet\u00eb. Kjo \u00ebsht\u00eb thjesht PHP i past\u00ebr me kopim e ngjitje nga projekti i m\u00ebparsh\u00ebm, ku mund t\u00eb gjesh \u00e7do gj\u00eb. Kosto t\u00eb m\u00ebdha n\u00eb skriptet e deploy-it, kur ju nevojiten disa skripte t\u00eb komplikuara Bash p\u00ebr t\u00eb nd\u00ebrruar disa rreshta n\u00eb ndonj\u00eb skedar, dhe n\u00eb t\u00eb nj\u00ebjt\u00ebn koh\u00eb k\u00ebto skripte deploy-i thirren nga ndonj\u00eb skript tjet\u00ebr. N\u00eb p\u00ebrfundim, ju nd\u00ebrroni sistemin e deploy-it, zgjidhni di\u00e7ka tjet\u00ebr, dhe hup, sh\u00ebrbimi juaj nuk punon. Sepse aty duhej t\u00eb vendosni edhe 8 lidhje mes dosjeve t\u00eb ndryshme. Ose ndodhin raste kur nj\u00eb mij\u00eb regjistrime punojn\u00eb, nd\u00ebrsa nj\u00ebqind mij\u00eb nuk funksionojn\u00eb m\u00eb. <\/p>\n

Do t\u00eb vazhdoj t\u00eb udh\u00ebheq. Pranimi i sh\u00ebrbimit nga outsourci \u00ebsht\u00eb nj\u00eb procedur\u00eb e domosdoshme. A ka pasur ndok\u00ebnd q\u00eb sh\u00ebrbimi nga outsourci vjen dhe askush nuk e pranon? Nuk \u00ebsht\u00eb aq popullor, sigurisht, sa sh\u00ebrbimi jetim, por prap\u00eb. <\/p>\n

\"Sh\u00ebrbime-origjin\u00eb:
\n
\nSh\u00ebrbimi duhet kontrolluar, sh\u00ebrbimi duhet shqyrtuar, duhet t\u00eb ndryshohen fjal\u00ebkalimet. Kemi pasur nj\u00eb rast kur na kan\u00eb ofruar nj\u00eb sh\u00ebrbim, ku admini ishte \u00abif login == \u2018admin\u2019 && password == \u2018admin\u2019...\u00bb, shkruar direkt n\u00eb kod. Ne po mendojm\u00eb, dhe k\u00ebt\u00eb e shkruajn\u00eb njer\u00ebzit n\u00eb vitin 2018?<\/p>\n

Testimi i kapacitetit t\u00eb ruajtjes \u2014 gjithashtu nj\u00eb gj\u00eb e nevojshme. Duhet t\u00eb shikoni se \u00e7far\u00eb do ndodh\u00eb me nj\u00ebqind mij\u00eb regjistrime, edhe para se ta lansoni k\u00ebt\u00eb sh\u00ebrbim n\u00eb prodhim. <\/p>\n

\"Sh\u00ebrbime-origjin\u00eb:
\n
\nT\u00eb d\u00ebrgoni sh\u00ebrbimin p\u00ebr rieditje nuk duhet t\u00eb jet\u00eb nj\u00eb turp. Kur thoni: \"Ne nuk do ta pranojm\u00eb k\u00ebt\u00eb sh\u00ebrbim, kemi 20 detyra, b\u00ebni ato, pastaj do ta pranojm\u00eb\", \u00ebsht\u00eb n\u00eb rregull. Ndjenja e fajit nuk duhet t\u00eb ju b\u00ebj\u00eb t\u00eb ndiheni keq p\u00ebr t'i vendosur menaxherit nj\u00eb barr\u00eb, ose q\u00eb biznesi do t\u00eb shpenzoj\u00eb para. Biznesi do t\u00eb shpenzoj\u00eb m\u00eb shum\u00eb m\u00eb von\u00eb.<\/p>\n

Kemi pasur nj\u00eb rast kur vendos\u00ebm t\u00eb realizojm\u00eb nj\u00eb projekt pilot n\u00eb outsourcim.<\/p>\n

\"Sh\u00ebrbime-origjin\u00eb:
\n
\nAi u dor\u00ebzua n\u00eb koh\u00eb, dhe ky ishte kriteri i vet\u00ebm i cil\u00ebsis\u00eb. Prandaj b\u00ebm\u00eb nj\u00eb projekt pilot t\u00eb ri, tashm\u00eb madje jo krejt pilot. K\u00ebto sh\u00ebrbime u pranuan, n\u00eb m\u00ebnyr\u00eb administrative than\u00eb, ja kodi juaj, ja ekipi, ja menaxheri juaj. Sh\u00ebrbimet n\u00eb t\u00eb v\u00ebrtet\u00eb filluan t\u00eb sillnin fitim. P\u00ebr m\u00eb tep\u00ebr, ata mbet\u00ebn ende si jetim\u00eb, askush nuk e kupton se si funksionojn\u00eb, dhe menaxher\u00ebt p\u00ebrpiqen t\u00eb largohet nga detyrat e tyre. <\/p>\n

\"Sh\u00ebrbime-origjin\u00eb:
\n
\nKa edhe nj\u00eb koncept t\u00eb shk\u00eblqyer \u2014 zhvillimi gueril. Kur ndonj\u00eb departament, zakonisht ky \u00ebsht\u00eb departamenti i marketingut, d\u00ebshiron t\u00eb testoj\u00eb nj\u00eb hipotez\u00eb dhe porosit nj\u00eb sh\u00ebrbim t\u00eb t\u00ebr\u00eb n\u00eb outsourcing. Nj\u00eb trafik fillon t\u00eb v\u00ebrshoj\u00eb, ata mbyllin dokumentet, n\u00ebnshkruajn\u00eb aktet me kontraktorin, hyjn\u00eb n\u00eb funksionim dhe thon\u00eb: \u00abDjem, kemi nj\u00eb sh\u00ebrbim k\u00ebtu, tashm\u00eb ka trafik, na sjell para, le ta pranojm\u00eb\u00bb. Ne themi: \u00abOop, si ndodhi kjo\u00bb.<\/p>\n

\"Sh\u00ebrbime-origjin\u00eb:
\n
\nDhe nj\u00eb m\u00ebnyr\u00eb tjet\u00ebr p\u00ebr t\u00eb marr\u00eb sh\u00ebrbimin jetim: kur nj\u00eb skuad\u00ebr papritmas \u00ebsht\u00eb e ngarkuar, menaxhmenti thot\u00eb: \"Le t\u00eb kalojm\u00eb sh\u00ebrbimin e k\u00ebsaj skuadre te nj\u00eb skuad\u00ebr tjet\u00ebr, sepse ka m\u00eb pak ngarkes\u00eb\". Pastaj e kalojm\u00eb te skuadra e tret\u00eb dhe ndryshojm\u00eb menaxherin. Dhe p\u00ebrfundimisht, na del p\u00ebrs\u00ebri si jetim.<\/p>\n

Cila \u00ebsht\u00eb problema me jetim\u00ebt?<\/b><\/h3>\n

\n\"Sh\u00ebrbime-origjin\u00eb:
\n
\nKush nuk e di, \u00ebsht\u00eb anija e ngritur n\u00eb Suedi Wasa, e famshme p\u00ebr at\u00eb q\u00eb u mbyt pes\u00eb minuta pas daljes n\u00eb uj\u00eb. Dhe mbretit t\u00eb Suedis\u00eb, p\u00ebrve\u00e7 k\u00ebsaj, nuk i hodhi ask\u00ebnd n\u00eb burg p\u00ebr k\u00ebt\u00eb. Ajo u nd\u00ebrtua nga dy breza inxhinier\u00ebsh q\u00eb nuk dinin t\u00eb ndanin anije t\u00eb tilla. Efekti i ligjsh\u00ebm.<\/p>\n

Anija mund t\u00eb ishte mbytur, p\u00ebr shembull, kur mbreti po udh\u00ebtonte diku n\u00eb nj\u00eb stuhi. Por k\u00ebshtu, u mbyt menj\u00ebher\u00eb, sipas metodologjis\u00eb agile \u00ebsht\u00eb mir\u00eb \u2014 t\u00eb d\u00ebshtosh her\u00ebt. <\/p>\n

N\u00ebse d\u00ebshtuam her\u00ebt, zakonisht nuk ka probleme. P\u00ebr shembull, gjat\u00eb pranimit d\u00ebrguam p\u00ebr p\u00ebrmir\u00ebsim. Por n\u00ebse d\u00ebshtuam tashm\u00eb n\u00eb prodhim, kur jan\u00eb investuar para, at\u00ebher\u00eb mund t\u00eb ket\u00eb probleme. Pasojat, si\u00e7 quhen n\u00eb biznes.<\/p>\n

Cfar\u00eb rrezikshm\u00ebrie kan\u00eb sh\u00ebrbimet jetim\u00eb:<\/p>\n