{"id":92810,"date":"2020-08-31T07:42:09","date_gmt":"2020-08-31T05:42:09","guid":{"rendered":"https:\/\/prohoster.info\/blog\/administrirovanie\/vybor-arhitekturnogo-stilya-chast-1"},"modified":"2020-08-31T07:42:09","modified_gmt":"2020-08-31T05:42:09","slug":"vybor-arhitekturnogo-stilya-chast-1","status":"publish","type":"post","link":"https:\/\/prohoster.info\/sq\/blog\/administrirovanie\/vybor-arhitekturnogo-stilya-chast-1","title":{"rendered":"Zgjedhja e stilit arkitektonik (pjesa 1)","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"

P\u00ebrsh\u00ebndetje, Habr. Tani \u00ebsht\u00eb hapur regjistrimi p\u00ebr nj\u00eb grup t\u00eb ri kursi n\u00eb OTUS. \u00abArkitekt i Softuerit\u00bb<\/a><\/noindex>. N\u00eb prag t\u00eb fillimit t\u00eb kursit, dua t\u00eb ndaj me ju artikullin tim t\u00eb autorit.<\/i><\/b><\/p>\n

<\/p>\n

Hyrje<\/h2>\n

\nZgjedhja e stilit arkitektonik \u00ebsht\u00eb nj\u00eb nga vendimet thelb\u00ebsore teknike kur zhvillohet nj\u00eb sistem informacioni. N\u00eb k\u00ebt\u00eb seri artikujsh, propozoj t\u00eb shqyrtoj stil\u00ebt m\u00eb t\u00eb njohur arkitektonik\u00eb p\u00ebr nd\u00ebrtimin e aplikacioneve dhe t\u00eb p\u00ebrgjigjem n\u00eb pyetjen se kur cili stil arkitektonik \u00ebsht\u00eb m\u00eb i preferuar. Gjat\u00eb trajtimit, do t\u00eb p\u00ebrpiqem t\u00eb p\u00ebr\u00e7oj nj\u00eb lidhje logjike q\u00eb shpjegon zhvillimin e stil\u00ebve arkitektonik\u00eb nga monolit\u00ebt tek mikro-sh\u00ebrbimet.
\n<\/a><\/noindex><\/p>\n

Pak histori<\/h2>\n

\nN\u00ebse p\u00ebrpiqeni t\u00eb pyesni zhvilluesit: \"Pse jan\u00eb t\u00eb nevojshme mikrosh\u00ebrbimet?\", do t\u00eb merrni p\u00ebrgjigje t\u00eb ndryshme. Do t\u00eb d\u00ebgjoni se mikrosh\u00ebrbimet p\u00ebrmir\u00ebsojn\u00eb shkall\u00ebzimin, leht\u00ebsojn\u00eb kuptimin e kodit, p\u00ebrmir\u00ebsojn\u00eb q\u00ebndrueshm\u00ebrin\u00eb, ndonj\u00ebher\u00eb mund t\u00eb d\u00ebgjoni se ato lejojn\u00eb \"pastrimin e kodit\". Le t\u00eb kthehemi pas n\u00eb histori, p\u00ebr t\u00eb kuptuar se cila ishte q\u00ebllimi i krijimit t\u00eb mikrosh\u00ebrbimeve.<\/p>\n

P\u00ebr ta th\u00ebn\u00eb shkurt, mikrosh\u00ebrbimet sipas kuptimit ton\u00eb aktual u shfaq\u00ebn si m\u00eb posht\u00eb: n\u00eb vitin 2011, James Lewis, duke analizuar pun\u00ebn e ndryshme t\u00eb kompanive, vuri re shfaqjen e nj\u00eb modeli t\u00eb ri \"micro-app\", i cili optimizonte SOA nga pik\u00ebpamja e shpejt\u00ebsis\u00eb s\u00eb shp\u00ebrndarjes s\u00eb sh\u00ebrbimeve. Nj\u00eb koh\u00eb m\u00eb von\u00eb, n\u00eb vitin 2012, n\u00eb nj\u00eb samit arkitektonik, modeli u rinomua mikrosh\u00ebrbim. K\u00ebshtu, q\u00ebllimi fillestar i zbatuar mikrosh\u00ebrbimeve ishte p\u00ebrmir\u00ebsimi i t\u00eb ashtuquajturit time to market<\/b>.<\/p>\n

Mikrosh\u00ebrbimet ishin n\u00eb \"val\u00ebn e hype-it\" n\u00eb vitin 2015. Sipas disa hulumtimeve, asnj\u00eb konferenc\u00eb nuk kalonte pa nj\u00eb prezantim mbi mikrosh\u00ebrbimet. P\u00ebr m\u00eb tep\u00ebr, disa konferenca ishin t\u00eb dedikuara p\u00ebr mikrosh\u00ebrbimet. Tani, shum\u00eb projekte fillojn\u00eb me p\u00ebrdorimin e k\u00ebtij stili arkitektonik, dhe n\u00ebse nj\u00eb projekt p\u00ebrmban shum\u00eb kod t\u00eb vjet\u00ebr, pa dyshim q\u00eb migrimi n\u00eb mikrosh\u00ebrbime po realizohet aktivisht.<\/p>\n

Megjithat\u00eb, pavar\u00ebsisht t\u00eb gjitha k\u00ebtyre, ende ka nj\u00eb num\u00ebr t\u00eb vog\u00ebl zhvilluesish q\u00eb mund t\u00eb p\u00ebrcaktojn\u00eb konceptin e \"mikrosh\u00ebrbimit\". Por p\u00ebr k\u00ebt\u00eb do t\u00eb flasim m\u00eb von\u00eb...<\/p>\n

Monolit<\/h2>\n

\nStili arkitektonik q\u00eb \u00ebsht\u00eb n\u00eb opozit\u00eb me mikrosh\u00ebrbimin \u00ebsht\u00eb monolit (ose \"t\u00eb gjitha n\u00eb nj\u00eb\"). Nuk ka shum\u00eb kuptim t\u00eb flas\u00ebsh p\u00ebr monolit, prandaj do t\u00eb p\u00ebrmend menj\u00ebher\u00eb disavantazhet e k\u00ebtij stili arkitektonik q\u00eb nxit\u00ebn zhvillimin e m\u00ebtejsh\u00ebm t\u00eb stileve arkitektonike: madh\u00ebsia, lidhshm\u00ebria, shp\u00ebrndarja, shkall\u00ebzimi, q\u00ebndrueshm\u00ebria dhe ngurt\u00ebsia. M\u00eb posht\u00eb do t\u00eb paraqes \u00e7do disavantazh n\u00eb ve\u00e7anti.<\/p>\n

Madh\u00ebsia<\/h3>\n

\nMonoliti \u00ebsht\u00eb shum\u00eb i madh. Ai zakonisht komunikon me nj\u00eb baz\u00eb t\u00eb dh\u00ebnash shum\u00eb t\u00eb madhe. Aplikacioni b\u00ebhet shum\u00eb i madh p\u00ebr ta kuptuar nga nj\u00eb zhvillues i vet\u00ebm n\u00eb parim. Vet\u00ebm ata q\u00eb kan\u00eb kaluar mjaft koh\u00eb me k\u00ebt\u00eb kod mund t\u00eb punojn\u00eb mir\u00eb me monolitin, nd\u00ebrsa fillestar\u00ebt do t\u00eb shpenzojn\u00eb shum\u00eb koh\u00eb duke u p\u00ebrpjekur t\u00eb kuptojn\u00eb monolitin dhe nuk \u00ebsht\u00eb e sigurt q\u00eb do t\u00eb arrijn\u00eb ta b\u00ebjn\u00eb k\u00ebt\u00eb. Zakonisht, kur pune me monolitin, ka gjithmon\u00eb nj\u00eb \"senior\" t\u00eb kushteve, i cili e njeh monolitin m\u00eb shum\u00eb ose m\u00eb pak mir\u00eb dhe i ndihmon zhvilluesit e rinj p\u00ebr nj\u00eb vit ose m\u00eb shum\u00eb. Sigurisht q\u00eb ky senior \u00ebsht\u00eb nj\u00eb pik\u00eb e vetme d\u00ebshtimi, dhe largimi i tij mund t\u00eb \u00e7oj\u00eb n\u00eb shkat\u00ebrrimin e monolitit. <\/p>\n

Lidhshm\u00ebria<\/h3>\n

\nMonoliti paraqet nj\u00eb \"gjurm\u00eb t\u00eb madhe dhe t\u00eb nd\u00ebrlikuar\" (big ball of mud), ndryshimet n\u00eb t\u00eb cilin mund t\u00eb \u00e7ojn\u00eb n\u00eb pasoja t\u00eb paparashikueshme. Duke b\u00ebr\u00eb ndryshime n\u00eb nj\u00eb vend, mund t\u00eb d\u00ebmtohet monoliti n\u00eb nj\u00eb tjet\u00ebr (ajo q\u00eb quhet \"k\u00ebmba e lajthitur, dhe doli n\u00eb m\u00ebnyr\u00eb t\u00eb paparashikuar\"). Kjo ndodh sepse komponent\u00ebt n\u00eb monolit kan\u00eb lidhshm\u00ebri shum\u00eb komplekse dhe, m\u00eb e r\u00ebnd\u00ebsishmja, t\u00eb paqarta.<\/p>\n

Zhvillimi<\/h3>\n

\nShp\u00ebrndarja e monolitit p\u00ebr shkak t\u00eb lidhjeve t\u00eb komplikuara nd\u00ebrmjet komponenteve t\u00eb tij \u00ebsht\u00eb nj\u00eb proces i gjat\u00eb dhe me ritet e veta. Ky ritual zakonisht nuk \u00ebsht\u00eb p\u00ebrfundimisht i standardizuar dhe transmetohet \"goj\u00eb m\u00eb goj\u00eb\". <\/p>\n

Shkall\u00ebzueshm\u00ebria<\/h3>\n

\nModulet e monolitit mund t\u00eb ken\u00eb k\u00ebrkesa t\u00eb konfliktuara p\u00ebr burime, prandaj \u00ebsht\u00eb e nevojshme t\u00eb k\u00ebrkohet nj\u00eb kompromis nga pik\u00ebpamja e harduerit. Imagjinoni se monoliti juaj \u00ebsht\u00eb i p\u00ebrb\u00ebr\u00eb nga sh\u00ebrbimet A dhe B. Sh\u00ebrbimi A ka nevoja t\u00eb larta p\u00ebr hap\u00ebsir\u00eb n\u00eb disk, nd\u00ebrsa sh\u00ebrbimi B ka nevoja p\u00ebr memorie t\u00eb p\u00ebrkohshme. N\u00eb k\u00ebt\u00eb rast, ose makina q\u00eb ka monolitin duhet t\u00eb mb\u00ebshtes\u00eb k\u00ebrkesat e t\u00eb dy sh\u00ebrbimeve, ose do t\u00eb duhet t\u00eb dezaktivoni ndonj\u00eb nga sh\u00ebrbimet manualisht.<\/p>\n

Nj\u00eb shembull tjet\u00ebr (m\u00eb klasik): sh\u00ebrbimi A \u00ebsht\u00eb shum\u00eb m\u00eb i popullarizuar se sh\u00ebrbimi B, prandaj d\u00ebshironi q\u00eb t\u00eb keni 100 sh\u00ebrbime A dhe 10 sh\u00ebrbime B. Edhe nj\u00eb her\u00eb, ka dy mund\u00ebsi: ose shp\u00ebrndani 100 monolite t\u00eb plot\u00eb, ose do t\u00eb duhet t\u00eb q\u00ebndroni manualisht disa nga sh\u00ebrbimet B. <\/p>\n

Besueshm\u00ebria<\/h3>\n

\nPasi t\u00eb gjitha sh\u00ebrbimet jan\u00eb s\u00eb bashku, n\u00ebse monoliti bie, t\u00eb gjitha sh\u00ebrbimet bien p\u00ebrnj\u00ebher\u00ebsh. N\u00eb t\u00eb v\u00ebrtet\u00eb, ndoshta kjo nuk \u00ebsht\u00eb aq e keqe, t\u00eb pakt\u00ebn nuk do t\u00eb ket\u00eb d\u00ebshtime t\u00eb pjesshme n\u00eb nj\u00eb sistem t\u00eb shp\u00ebrndar\u00eb, megjithat\u00eb, anasjelltas, p\u00ebr shkak t\u00eb nj\u00eb gabimi n\u00eb funksionalitetin q\u00eb p\u00ebrdoret nga 0.001% e p\u00ebrdoruesve, mund t\u00eb humbni t\u00eb gjith\u00eb p\u00ebrdoruesit e sistemit tuaj. <\/p>\n

Ngurt\u00ebsia<\/h3>\n

\nP\u00ebr shkak t\u00eb madh\u00ebsis\u00eb s\u00eb monolitit, \u00ebsht\u00eb e v\u00ebshtir\u00eb t\u00eb kalosh n\u00eb teknologji t\u00eb reja. Si pasoj\u00eb, nj\u00eb detyr\u00eb e ve\u00e7ant\u00eb \u00ebsht\u00eb mbajtja e atij senior-i t\u00eb mundsh\u00ebm. Stack-u teknologjik i zgjedhur n\u00eb fillim t\u00eb projektit mund t\u00eb b\u00ebhet nj\u00eb bllokad\u00eb q\u00eb pengon zhvillimin e produktit. <\/p>\n

P\u00ebrfundimi<\/h2>\n

\nHer\u00ebn tjet\u00ebr do t\u00eb flasim p\u00ebr m\u00ebnyrat se si njer\u00ebzit p\u00ebrpoqen t\u00eb zgjidhin k\u00ebto probleme, duke kaluar n\u00eb komponent\u00eb dhe SOA.<\/p>\n

\"Zgjedhja<\/a><\/noindex><\/p>\n

\n

Lexoni m\u00eb shum\u00eb:<\/h4>\n

<\/p>\n