{"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\u00ebrbimet jetim\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 Nikolskyi, fol n\u00eb konferenc\u00ebn e vitit t\u00eb kaluar. DevOpsDays Moscow<\/a><\/noindex> p\u00ebr sh\u00ebrbimet jetimore: si t\u00eb identifikoni nj\u00eb jetimore n\u00eb infrastruktur\u00eb, \u00e7far\u00eb \u00ebsht\u00eb keq p\u00ebr sh\u00ebrbimet jetimore, \u00e7far\u00eb t\u00eb b\u00ebni me to, dhe si t\u00eb veproni n\u00ebse asgj\u00eb tjet\u00ebr nuk ndihmon.<\/p>\n

Posht\u00eb \u00ebsht\u00eb versioni tekstual i 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, drejtoj operacionet n\u00eb kompanin\u00eb Banki.ru.<\/p>\n

Kemi sh\u00ebrbime t\u00eb m\u00ebdha, q\u00eb jan\u00eb sh\u00ebrbime monolite, kemi sh\u00ebrbime n\u00eb nj\u00eb kuptim m\u00eb klasik, gjithashtu dhe shum\u00eb t\u00eb vogla. N\u00eb terminologjin\u00eb time punuese, them se n\u00ebse sh\u00ebrbimi \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

Avantazhet e sh\u00ebrbimeve<\/b><\/h3>\n

\nDo t\u00eb kaloj\u00eb shpejt p\u00ebr avantazhet e sh\u00ebrbimeve. <\/p>\n

\"Sh\u00ebrbimet
\n
\nE para \u2014 shkall\u00ebzimi. Mund t\u00eb b\u00ebni shpejt dicka n\u00eb sh\u00ebrbim dhe t\u00eb filloni n\u00eb prodhim. Ju erdhi trafiku, ju e klonuat sh\u00ebrbimin. Ju erdhi edhe nj\u00eb trafik, ju e klonuat p\u00ebrs\u00ebri dhe me k\u00ebt\u00eb jetoni. Ky \u00ebsht\u00eb nj\u00eb bonus i mir\u00eb, dhe, n\u00eb parim, kur filluam, ai konsiderohej nga ne si m\u00eb i r\u00ebnd\u00ebsishmi, pse e b\u00ebjm\u00eb k\u00ebt\u00eb gjith\u00eb.<\/p>\n

\"Sh\u00ebrbimet
\n
\nE dyta, zhvillimi i izoluar, kur keni disa ekipe zhvillimi, disa zhvillues t\u00eb ndrysh\u00ebm n\u00eb \u00e7do ekip, dhe \u00e7do ekip punon n\u00eb sh\u00ebrbimin e vet.<\/p>\n

Me ekipet ndodhin nuanca. \u00c7do zhvillues \u00ebsht\u00eb i ndrysh\u00ebm. Dhe ekzistojn\u00eb, p\u00ebr shembull, njer\u00ebz-mushk\u00eb<\/a><\/noindex>. E pash\u00eb p\u00ebr her\u00eb t\u00eb par\u00eb k\u00ebt\u00eb nga Maksim Dorofeev. Ndonj\u00ebher\u00eb njer\u00ebz-mushk\u00eb ka n\u00eb disa ekipe, dhe n\u00eb disa nuk ka. Kjo i b\u00ebn sh\u00ebrbimet e ndryshme q\u00eb p\u00ebrdoren n\u00eb kompanin\u00eb m\u00eb pak t\u00eb barabarta. <\/p>\n

\"Sh\u00ebrbimet
\n
\nShikoni imazhin: ky \u00ebsht\u00eb nj\u00eb zhvillues i shk\u00eblqyer, ai ka duar t\u00eb m\u00ebdha, mund t\u00eb b\u00ebj\u00eb shum\u00eb. Problemi kryesor \u00ebsht\u00eb nga vijn\u00eb k\u00ebto duar. <\/p>\n

\"Sh\u00ebrbimet
\n
\nSh\u00ebrbimet ofrojn\u00eb mund\u00ebsin\u00eb p\u00ebr t\u00eb p\u00ebrdorur gjuh\u00eb t\u00eb ndryshme programuese, m\u00eb t\u00eb p\u00ebrshtatshme p\u00ebr detyra t\u00eb ndryshme. Nj\u00eb sh\u00ebrbim n\u00eb Go, ndonj\u00eb n\u00eb Erlang, ndonj\u00eb n\u00eb Ruby, di\u00e7ka n\u00eb PHP, di\u00e7ka n\u00eb Python. N\u00eb p\u00ebrgjith\u00ebsi, mund t\u00eb shtriheni shum\u00eb gjer\u00eb. K\u00ebtu ka disa nuanca.<\/p>\n

\"Sh\u00ebrbimet
\n
\nArkitektura e orientuar ndaj sh\u00ebrbimeve \u2014 kjo \u00ebsht\u00eb para s\u00eb gjithash p\u00ebr devops. Pra, n\u00ebse nuk keni automatizim, nuk keni procesin e vendosjes, n\u00ebse e konfiguroni manualisht, konfigurimet tuaja mund t\u00eb ndryshojn\u00eb nga instanca e sh\u00ebrbimit n\u00eb instanc\u00ebn tjet\u00ebr, dhe ju duhet t\u00eb shkoni atje t\u00eb b\u00ebni di\u00e7ka, at\u00ebher\u00eb jeni n\u00eb ferr. <\/p>\n

P\u00ebr shembull, n\u00ebse keni 20 sh\u00ebrbime dhe duhet t'i publikoni manualisht, do t\u00eb keni 20 konsola dhe do t\u00eb shtypni \"enter\" nj\u00ebkoh\u00ebsisht, si ninja. Kjo nuk \u00ebsht\u00eb shum\u00eb mir\u00eb. <\/p>\n

N\u00ebse keni nj\u00eb sh\u00ebrbim pas testimit (n\u00ebse ka testim, natyrisht), dhe duhet ta p\u00ebrmir\u00ebsoni pak q\u00eb t\u00eb funksionoj\u00eb n\u00eb prodhim, kam edhe p\u00ebr ju lajme t\u00eb k\u00ebqija. <\/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 keni th\u00ebn\u00eb po ashtu: \"Gjith\u00e7ka po digjet, un\u00eb jam mir\u00eb, gjith\u00e7ka \u00ebsht\u00eb n\u00eb rregull.\"<\/p>\n

\"Sh\u00ebrbimet
\n
\nNe p\u00ebrdorim Ansible p\u00ebr automatizimin e deploy-it, Puppet p\u00ebr konvergjenc\u00eb, Bamboo p\u00ebr automatizimin e publikimit dhe Confluence p\u00ebr ta dokumentuar gjith\u00e7ka n\u00eb nj\u00ebfar\u00eb m\u00ebnyre.<\/p>\n

Nuk do t\u00eb ndalem shum\u00eb n\u00eb k\u00ebt\u00eb tem\u00eb, sepse raporti \u00ebsht\u00eb m\u00eb shum\u00eb p\u00ebr praktikat e bashk\u00ebpunimit se sa p\u00ebr zbatimin teknik. <\/p>\n

\"Sh\u00ebrbimet
\n
\nNa ka ndodhur, p\u00ebr shembull, problemi q\u00eb Puppet n\u00eb server punon me Ruby 2, nd\u00ebrsa nj\u00eb aplikacion \u00ebsht\u00eb shkruar p\u00ebr Ruby 1.8, dhe ata nuk punojn\u00eb s\u00eb bashku. Kjo ndodh p\u00ebr shkak t\u00eb ndonj\u00eb defekti. Dhe kur ju nevojitet t\u00eb mbani disa versione t\u00eb Ruby n\u00eb nj\u00eb makin\u00eb, zakonisht fillojn\u00eb problemet. <\/p>\n

P\u00ebr shembull, ne i japim \u00e7do zhvilluesi nj\u00eb platform\u00eb n\u00eb t\u00eb cil\u00ebn ka gjith\u00e7ka q\u00eb ne kemi, t\u00eb gjitha sh\u00ebrbimet q\u00eb mund t\u00eb zhvillohen, p\u00ebr t\u00eb pasur nj\u00eb ambient t\u00eb izoluar ku ai mund ta prish\u00eb dhe ta nd\u00ebrtoj\u00eb sipas d\u00ebshir\u00ebs. <\/p>\n

Ndonj\u00ebher\u00eb, nevojitet ndonj\u00eb paket\u00eb e kompiluar ve\u00e7mas me mb\u00ebshtetje p\u00ebr ndonj\u00eb funksionalitet aty. Kjo \u00ebsht\u00eb mjaft serioze. Ndiqa nj\u00eb raport ku imazhi i docker-it pesha 45 GB. N\u00eb Linux, sigurisht, \u00ebsht\u00eb m\u00eb e leht\u00eb, aty \u00ebsht\u00eb m\u00eb e vog\u00ebl, por prap\u00ebseprap\u00eb, nuk do t\u00eb ket\u00eb hap\u00ebsir\u00eb t\u00eb mjaftueshme. <\/p>\n

Po, ndodhin ndonj\u00ebher\u00eb var\u00ebsi kontradiktore, kur nj\u00eb pjes\u00eb e projektit varet nga nj\u00eb version i nj\u00eb biblioteke, nd\u00ebrsa nj\u00eb pjes\u00eb tjet\u00ebr nga nj\u00eb version tjet\u00ebr, dhe bibliotekat nuk instalohen s\u00eb bashku n\u00eb asnj\u00eb m\u00ebnyr\u00eb. <\/p>\n

\"Sh\u00ebrbimet
\n
\nNe kemi faqe dhe sh\u00ebrbime n\u00eb PHP 5.6, p\u00ebr t\u00eb cilat ndjehemi t\u00eb turp\u00ebruar, por \u00e7far\u00eb t\u00eb b\u00ebjm\u00eb? Kjo \u00ebsht\u00eb nj\u00eb platform\u00eb p\u00ebr ne. Ka faqe dhe sh\u00ebrbime n\u00eb PHP 7, ato jan\u00eb m\u00eb t\u00eb shumta dhe p\u00ebr to nuk ndjehemi t\u00eb turp\u00ebruar. \u00c7do zhvillues ka baz\u00ebn e tij ku g\u00ebzohet duke punuar. <\/p>\n

N\u00ebse punoni n\u00eb nj\u00eb kompani me nj\u00eb gjuh\u00eb, at\u00ebher\u00eb tri maqin\u00eb virtuale p\u00ebr \u00e7do zhvillues \u00ebsht\u00eb nj\u00eb gj\u00eb normale. N\u00ebse keni gjuh\u00eb programimi t\u00eb ndryshme, situata b\u00ebhet m\u00eb e komplikuar.<\/p>\n

\"Sh\u00ebrbimet
\n
\nJu njohni se juaj faqet dhe sh\u00ebrbimet e lidhura krijojn\u00eb nj\u00eb hap\u00ebsir\u00eb p\u00ebr mb\u00ebshtetje, dhe gjithmon\u00eb ka di\u00e7ka q\u00eb mund t\u00eb prish\u00ebt nga ato.<\/p>\n

\"Sh\u00ebrbimet
\n
\nPrandaj ne z\u00ebvend\u00ebsuam karakteristikat e gjuh\u00ebs s\u00eb programimit me p\u00ebrdorimin e framework-eve t\u00eb ndryshme, pasi framework-et p\u00ebr PHP jan\u00eb mjaft t\u00eb ndryshme dhe ofrojn\u00eb mund\u00ebsi t\u00eb ndryshme, komunitet t\u00eb ndrysh\u00ebm, dhe mb\u00ebshtetje t\u00eb ndryshme. K\u00ebshtu mund t\u00eb shkruani nj\u00eb sh\u00ebrbim n\u00eb m\u00ebnyr\u00eb q\u00eb t\u00eb keni tashm\u00eb di\u00e7ka t\u00eb gatshme p\u00ebr t\u00eb. <\/p>\n

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

\n\"Sh\u00ebrbimet
\n
\nAvantazhi yn\u00eb kryesor, i cili \u00ebsht\u00eb formuar gjat\u00eb disa viteve, \u00ebsht\u00eb se \u00e7do sh\u00ebrbim ka ekipin e vet. Kjo \u00ebsht\u00eb e dobishme p\u00ebr nj\u00eb projekt t\u00eb madh, sepse mund t\u00eb kurseni koh\u00eb n\u00eb dokumentacion, menaxher\u00ebt e njohin mir\u00eb projektin e tyre. <\/p>\n

Detyrat e mb\u00ebshtetjes mund t\u00eb shp\u00ebrndahen leht\u00ebsisht. P\u00ebr shembull, n\u00ebse nj\u00eb sh\u00ebrbim sigurie prishet. Menj\u00ebher\u00eb ekipi q\u00eb merret me sigurimin fillon ta riparoj\u00eb. <\/p>\n

Funksionet e reja krijohen shpejt, sepse kur keni nj\u00eb sh\u00ebrbim atomar, mund t\u00eb rishikoni di\u00e7ka me shpejt\u00ebsi. <\/p>\n

Dhe kur prishet sh\u00ebrbimi juaj, q\u00eb \u00ebsht\u00eb e pashmangshme, nuk ndikon n\u00eb sh\u00ebrbimet e tjera, dhe zhvilluesit nga ekipet e tjera nuk vijn\u00eb te ju me shkopinj dhe nuk thon\u00eb: \u201cO jo, mos e b\u00ebj k\u00ebshtu\u201d. <\/p>\n

\"Sh\u00ebrbimet
\n
\nSi gjithmon\u00eb, ka nuanca. Ne kemi ekipe t\u00eb stabilizuara, menaxher\u00ebt jan\u00eb t\u00eb angazhuar ngusht\u00eb me ekipet. Ka dokumente t\u00eb qarta, menaxher\u00ebt e ndjekin ngusht\u00ebsisht t\u00eb gjitha ato. \u00c7do ekip me menaxherin ka disa sh\u00ebrbime, dhe ka nj\u00eb pik\u00eb t\u00eb caktuar kompetence. <\/p>\n

N\u00ebse ekipet jan\u00eb t\u00eb l\u00ebvizshme (ndodhin edhe k\u00ebto ndonj\u00ebher\u00eb), ka nj\u00eb metod\u00eb t\u00eb mir\u00eb e quajtur \"hart\u00eb yjesh\".<\/p>\n

\"Sh\u00ebrbimet
\n
\nJu keni nj\u00eb list\u00eb sh\u00ebrbimesh dhe njer\u00ebzish. Ylli do t\u00eb thot\u00eb q\u00eb nj\u00eb person \u00ebsht\u00eb ekspert n\u00eb k\u00ebt\u00eb sh\u00ebrbim, libri do t\u00eb thot\u00eb q\u00eb nj\u00eb person po studion k\u00ebt\u00eb sh\u00ebrbim. Detyra e personit \u2013 \u00ebsht\u00eb t\u00eb ndryshoj\u00eb librin p\u00ebr nj\u00eb yll. Dhe n\u00ebse ndaj sh\u00ebrbimit nuk \u00ebsht\u00eb shkruar asgj\u00eb, at\u00ebher\u00eb fillojn\u00eb problemet, mbi t\u00eb cilat do t\u00eb flas m\u00eb tej. <\/p>\n

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

\n\"Sh\u00ebrbimet
\n
\nProblemi i par\u00eb, m\u00ebnyra e par\u00eb p\u00ebr t\u00eb krijuar nj\u00eb sh\u00ebrbim jetim n\u00eb infrastruktur\u00eb \u00ebsht\u00eb shkarkimi i punonj\u00ebsve. A ndodhi ndonj\u00ebher\u00eb q\u00eb afatet t\u00eb vijn\u00eb nga biznesi p\u00ebrpara se t\u00eb vler\u00ebsoheshin detyrat? Ndonj\u00ebher\u00eb ndodh q\u00eb afatet jan\u00eb t\u00eb ngurta dhe nuk ka koh\u00eb p\u00ebr dokumentacion. \"Duhet t\u00eb dor\u00ebzojm\u00eb sh\u00ebrbimin n\u00eb prodhim, pastaj do ta shkruajm\u00eb m\u00eb shum\u00eb.\" <\/p>\n

N\u00ebse ekipi \u00ebsht\u00eb i vog\u00ebl, ndodh q\u00eb n\u00eb t\u00eb ket\u00eb nj\u00eb zhvillues q\u00eb shkruan gjith\u00e7ka, nd\u00ebrsa t\u00eb tjer\u00ebt jan\u00eb n\u00eb mb\u00ebshtetje. \"Un\u00eb kam shkruar arkitektur\u00ebn kryesore, q\u00eb ti t\u00eb b\u00ebsh nd\u00ebrfaqet.\" Pastaj, n\u00eb ndonj\u00eb moment, menaxheri, p\u00ebr shembull, largohet. Dhe n\u00eb k\u00ebt\u00eb periudh\u00eb, kur menaxheri \u00ebsht\u00eb larguar dhe nuk \u00ebsht\u00eb caktuar ende nj\u00eb i ri, zhvilluesit vet\u00eb vendosin se ku po shkon sh\u00ebrbimi, \u00e7far\u00eb po ndodh atje. Si\u00e7 e dim\u00eb (t\u00eb kthehemi disa faqe mbrapa), n\u00eb disa ekipe ka njer\u00ebz q\u00eb jan\u00eb t\u00eb ve\u00e7ant\u00eb, ndonj\u00ebher\u00eb ndonj\u00eb udh\u00ebheq\u00ebs i ekipit si \"njeri i ve\u00e7ant\u00eb\". Pastaj ai largohet, dhe ne p\u00ebrfundojm\u00eb me nj\u00eb sh\u00ebrbim jetim. <\/p>\n

\"Sh\u00ebrbimet
\n
\nMegjithat\u00eb, detyrat nga mb\u00ebshtetja dhe biznesi nuk zhduken, ato grumbullohen n\u00eb bllokun e prapmbarimit. N\u00ebse gjat\u00eb zhvillimit t\u00eb sh\u00ebrbimit kishte ndonj\u00eb gabim arkitekturor, ato gjithashtu grumbullohen n\u00eb bllokun e prapmbarimit. Sh\u00ebrbimi po degredon ngadal\u00eb. <\/p>\n

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

\nKy list\u00eb e p\u00ebrshkruan mir\u00eb situat\u00ebn. Kushprekuar di\u00e7ka t\u00eb njohur n\u00eb infrastruktur\u00ebn e tij?<\/p>\n

\"Sh\u00ebrbimet
\n
\nP\u00ebr workaround-et e dokumentuara: ka nj\u00eb sh\u00ebrbim dhe, n\u00eb t\u00ebr\u00ebsi, ai funksionon, ka nj\u00eb manual dy faqesh se si t\u00eb punoni me t\u00eb, por si funksionon brenda, askush nuk e di. <\/p>\n

Ose, p\u00ebr shembull, ka ndonj\u00eb redh\u00eb linkesh. N\u00eb rastin ton\u00eb, tani po p\u00ebrdorim tre redha linkesh p\u00ebr q\u00ebllime t\u00eb ndryshme n\u00eb sh\u00ebrbime t\u00eb ndryshme. K\u00ebto jan\u00eb pasojat e k\u00ebsaj. <\/p>\n

\"Sh\u00ebrbimet
\n
\nTani do t\u00eb jem kapiteni i duksh\u00ebm. \u00c7far\u00eb duhet t\u00eb nd\u00ebrmerret? S\u00eb pari, sh\u00ebrbimi duhet t'i kaloj\u00eb nj\u00eb menaxheri tjet\u00ebr, nj\u00eb ekipi tjet\u00ebr. N\u00ebse lideri juaj i ekipit nuk ka dh\u00ebn\u00eb dor\u00ebheqje akoma, at\u00ebher\u00eb n\u00eb k\u00ebt\u00eb ekip tjet\u00ebr, kur e kuptoni se sh\u00ebrbimi i ngjan nj\u00eb jetimi, duhet t\u00eb p\u00ebrfshihet ndonj\u00eb q\u00eb t\u00eb pakt\u00ebn di di\u00e7ka p\u00ebr t\u00eb. <\/p>\n

Gj\u00ebja kryesore: duhet t\u00eb keni procedura t\u00eb shkruara me gjak p\u00ebr kalimin. N\u00eb rastin ton\u00eb, zakonisht p\u00ebrkujdesem p\u00ebr k\u00ebt\u00eb, sepse duhet q\u00eb gjith\u00e7ka t\u00eb funksionoj\u00eb. Menaxher\u00ebve iu nevojitet q\u00eb kjo t\u00eb dor\u00ebzohet shpejt, dhe se \u00e7far\u00eb do t\u00eb ndodh\u00eb m\u00eb pas, nuk \u00ebsht\u00eb m\u00eb aq e r\u00ebnd\u00ebsishme p\u00ebr ta. <\/p>\n

\"Sh\u00ebrbimet
\n
\nNj\u00eb m\u00ebnyr\u00eb tjet\u00ebr p\u00ebr t\u00eb krijuar nj\u00eb sh\u00ebrbim t\u00eb pamatur \u00ebsht\u00eb, \"Do ta b\u00ebjm\u00eb n\u00eb outsourc\u00eb, do t\u00eb jet\u00eb m\u00eb shpejt, dhe m\u00eb pas do t'ia kalojm\u00eb ekipit\". \u00cbsht\u00eb e qart\u00eb q\u00eb t\u00eb gjith\u00eb kan\u00eb ndonj\u00eb plan n\u00eb ekip, nj\u00eb radh\u00eb. Shpesh klienti biznesor mendon se outsourcing-u do t\u00eb b\u00ebj\u00eb pun\u00ebn si departamenti teknik q\u00eb ka kompania. Megjithat\u00eb, motivet e tyre jan\u00eb t\u00eb ndryshme. N\u00eb outsourcing ka zgjidhje teknologjike dhe algoritmike t\u00eb \u00e7uditshme.<\/p>\n

\"Sh\u00ebrbimet
\n
\nNe, p\u00ebr shembull, kishim nj\u00eb sh\u00ebrbim ku kishte Sphinx n\u00eb vende t\u00eb papritura. Do flas m\u00eb von\u00eb p\u00ebr at\u00eb q\u00eb na u detyrua t\u00eb b\u00ebjm\u00eb. <\/p>\n

Oferuesit e outsourcing-ut shpesh kan\u00eb framework t\u00eb shkruar vet\u00eb. \u00cbsht\u00eb thjesht PHP i past\u00ebr me kopjen e kodit nga projekti i kaluar, ku mund t\u00eb gjesh \u00e7do lloj. Ka nj\u00eb num\u00ebr t\u00eb madh \"patchesh\" n\u00eb skriptet e d\u00ebrgimit, kur ju nevojitet t\u00eb ndryshoni disa rreshta n\u00eb ndonj\u00eb skedar me skripta t\u00eb komplikuara Bash, nd\u00ebrkoh\u00eb q\u00eb k\u00ebto skripta d\u00ebrgimi thirren nga ndonj\u00eb skript tjet\u00ebr. N\u00eb fund, ndryshoni sistemin e d\u00ebrgimit, zgjidhni di\u00e7ka tjet\u00ebr, dhe papritmas sh\u00ebrbimi juaj nuk funksionon. Sepse duhej vendosur ende 8 lidhje midis dosjeve t\u00eb ndryshme. Ose ndodh q\u00eb nj\u00eb mij\u00eb regjistrime funksionojn\u00eb, por nj\u00ebqind mij\u00eb nuk funksionojn\u00eb. <\/p>\n

Do t\u00eb vazhdoj t\u00eb udh\u00ebheq. Pranimi i sh\u00ebrbimit nga outsourcing \u00ebsht\u00eb nj\u00eb procedur\u00eb e detyrueshme. A ka pasur ndokush q\u00eb sh\u00ebrbimi nga outsourcing arrin dhe nuk pranohet? Nuk \u00ebsht\u00eb kaq e njohur si sh\u00ebrbimi i pamatur, por megjithat\u00eb. <\/p>\n

\"Sh\u00ebrbimet
\n
\nSh\u00ebrbimi duhet t\u00eb kontrollohet, sh\u00ebrbimi duhet t\u00eb rishikohet, duhet t\u00eb ndryshohen fjal\u00ebkalimet. Kishim nj\u00eb rast kur na ofruan nj\u00eb sh\u00ebrbim, ku admin paneli kishte \u2018if login == \u2018admin\u2019 && password == \u2018admin\u2019\u2026\u2019 shkruar direkt n\u00eb kod. Po mendojm\u00eb, dhe kjo \u00ebsht\u00eb shkruar nga njer\u00ebz n\u00eb vitin 2018?<\/p>\n

Testimi i kapacitetit t\u00eb ruajtjes \u00ebsht\u00eb gjithashtu di\u00e7ka e nevojshme. Duhet t\u00eb shikoni se \u00e7far\u00eb do t\u00eb ndodh\u00eb me nj\u00ebqind mij\u00eb regjistrime, para se ta l\u00ebshoni k\u00ebt\u00eb sh\u00ebrbim diku n\u00eb prodhim. <\/p>\n

\"Sh\u00ebrbimet
\n
\nT\u00eb d\u00ebrgosh sh\u00ebrbimin p\u00ebr rregullim nuk duhet t\u00eb jet\u00eb di\u00e7ka p\u00ebr t'u turp\u00ebruar. Kur thoni: \"Ne nuk do ta pranojm\u00eb k\u00ebt\u00eb sh\u00ebrbim, kemi 20 detyrime, b\u00ebni ato, pastaj do ta pranojm\u00eb\", \u00ebsht\u00eb normale. Konsensusi nuk duhet t\u00eb ndiej\u00eb faj q\u00eb do t\u00eb vendos\u00eb menaxherin n\u00eb siklet, apo q\u00eb biznesi do t\u00eb harxhoj\u00eb para. N\u00eb fakt, biznesi do t\u00eb harxhoj\u00eb m\u00eb shum\u00eb m\u00eb von\u00eb.<\/p>\n

Kemi pasur nj\u00eb rast kur vendos\u00ebm t\u00eb b\u00ebjm\u00eb nj\u00eb projekt pilot n\u00eb outsourcing.<\/p>\n

\"Sh\u00ebrbimet
\n
\nAi u dor\u00ebzua n\u00eb koh\u00eb, dhe kjo ishte kriteri i vet\u00ebm i cil\u00ebsis\u00eb. Prandaj b\u00ebn\u00eb nj\u00eb tjet\u00ebr projekt pilot, tashm\u00eb jo krejt\u00ebsisht pilot. K\u00ebto sh\u00ebrbime u miratuan, u tha n\u00eb m\u00ebnyr\u00eb administrative, ja kodo juaj, ja ekipi juaj, ja menaxheri juaj. Sh\u00ebrbimet me t\u00eb v\u00ebrtet\u00eb filluan t\u00eb sjellin fitim. Megjithat\u00eb, n\u00eb fakt ato mbet\u00ebn s\u00ebrish jetima, askush nuk e kupton se si funksionojn\u00eb, dhe menaxher\u00ebt me \u00e7do m\u00ebnyr\u00eb distancohen nga detyrat e tyre. <\/p>\n

\"Sh\u00ebrbimet
\n
\nKa nj\u00eb koncept tjet\u00ebr t\u00eb shk\u00eblqyer - zhvillimi partizanik. Kur nj\u00eb departament, zakonisht ai i marketingut, d\u00ebshiron t\u00eb verifikoj\u00eb nj\u00eb hipotez\u00eb dhe porosit nj\u00eb sh\u00ebrbim krejt\u00ebsisht n\u00eb outsorcing. Ai fillon t\u00eb t\u00ebrheq\u00eb trafik, ata p\u00ebrfundojn\u00eb dokumentet, n\u00ebnshkruajn\u00eb aktet me kontraktuesin, shkojn\u00eb n\u00eb funksionim dhe thon\u00eb: \"Djem, kemi nj\u00eb sh\u00ebrbim k\u00ebtu, ka trafik, na sjell para, le t\u00eb pranojm\u00eb at\u00eb\". Ne themi: \"Oh, si ka mund\u00ebsi k\u00ebshtu?\".<\/p>\n

\"Sh\u00ebrbimet
\n
\nDhe nj\u00eb tjet\u00ebr m\u00ebnyr\u00eb p\u00ebr t\u00eb marr\u00eb nj\u00eb sh\u00ebrbim jetim: kur nj\u00eb ekip papritmas ngarkohet, drejtoria thot\u00eb: \"Le t\u00eb kalojm\u00eb sh\u00ebrbimin e k\u00ebtij ekipi tek nj\u00eb ekip tjet\u00ebr, q\u00eb ka nj\u00eb ngarkes\u00eb m\u00eb t\u00eb vog\u00ebl\". Pastaj e kalojm\u00eb tek ekipi i tret\u00eb, dhe menaxherin e ndryshojm\u00eb. Dhe p\u00ebrfundimisht, kemi p\u00ebrs\u00ebri nj\u00eb jetim.<\/p>\n

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

\n\"Sh\u00ebrbimet
\n
\nKush nuk e di, kjo \u00ebsht\u00eb anija linjare Wasa, e cila u nd\u00ebrtua n\u00eb Suedi, e famshme p\u00ebr faktin se u mbyt 5 minuta pas lan\u00ebs. Dhe mbreti i Suedis\u00eb, p\u00ebr siguri, nuk ekzekutoi ask\u00ebnd p\u00ebr k\u00ebt\u00eb. Ajo u nd\u00ebrtua nga dy breza inxhinier\u00ebsh q\u00eb nuk dinin t\u00eb nd\u00ebrtonin anije t\u00eb till\u00eb. Nj\u00eb efekt i natyrsh\u00ebm.<\/p>\n

Anija mund t\u00eb ishte mbytur, p\u00ebr shembull, shum\u00eb m\u00eb keq, n\u00ebse do t\u00eb kishte pasur mbretin duke udh\u00ebtuar diku n\u00eb nj\u00eb stuhi. Por k\u00ebshtu, u mbyt menj\u00ebher\u00eb, sipas metod\u00ebs Agile kjo \u00ebsht\u00eb mir\u00eb - d\u00ebshtimi i hersh\u00ebm. <\/p>\n

N\u00ebse kemi d\u00ebshtuar her\u00ebt, zakonisht nuk ka probleme. P\u00ebr shembull, gjat\u00eb pranimitt, e d\u00ebrgojm\u00eb p\u00ebr p\u00ebrmir\u00ebsim. Por n\u00ebse d\u00ebshtojm\u00eb tashm\u00eb n\u00eb prodhim, kur jan\u00eb investuar para, mund t\u00eb ken\u00eb probleme. Pasojat, si\u00e7 i quajn\u00eb ata n\u00eb biznes.<\/p>\n

Cilat jan\u00eb rreziqet e sh\u00ebrbimeve jetim\u00eb:<\/p>\n