{"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. Aktualisht n\u00eb OTUS \u00ebsht\u00eb hapur regjistrimi p\u00ebr nj\u00eb grup t\u00eb ri t\u00eb kursit \u00abArkitekt Softueri\u00bb<\/a><\/noindex>. Para fillimit t\u00eb kursit dua t\u00eb ndaj me ju artikullin tim autor.<\/i><\/b><\/p>\n

<\/p>\n

Hyrje<\/h2>\n

\nZgjedhja e stilit arkitektonik \u00ebsht\u00eb nj\u00eb nga vendimmarrjet teknike m\u00eb themelore n\u00eb nd\u00ebrtimin e nj\u00eb sistemi informatik. N\u00eb k\u00ebt\u00eb seri artikujsh, propozoj t\u00eb shqyrtojm\u00eb stilet m\u00eb t\u00eb njohura arkitektonike p\u00ebr nd\u00ebrtimin e aplikacioneve dhe t\u00eb p\u00ebrgjigjemi n\u00eb pyetjen se kur cili stil arkitektonik \u00ebsht\u00eb m\u00eb i preferuar. Gjat\u00eb paraqitjes, do t\u00eb p\u00ebrpiqem t\u00eb ndihmoj nj\u00eb zinxhir logjik q\u00eb shpjegon zhvillimin e stil\u00ebve arkitektonik\u00eb nga monolit\u00ebt n\u00eb mikrosh\u00ebrbime.
\n<\/a><\/noindex><\/p>\n

Pak histori<\/h2>\n

\nN\u00ebse provoni t\u00eb b\u00ebni nj\u00eb pyetje zhvilluesve: \"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 n\u00eb histori p\u00ebr t\u00eb kuptuar se \u00e7far\u00eb q\u00ebllimi kishin mikrosh\u00ebrbimet p\u00ebr krijimin e tyre.<\/p>\n

N\u00ebse flasim shkurtimisht, mikrosh\u00ebrbimet n\u00eb kuptimin ton\u00eb aktual u krijuan k\u00ebshtu: n\u00eb vitin 2011, James Lewis, duke analizuar pun\u00ebn e kompanive t\u00eb ndryshme, vuri re shfaqjen e nj\u00eb modeli t\u00eb ri \"micro-app\", i cili optimizoi SOA nga pik\u00ebpamja e shpejt\u00ebsis\u00eb s\u00eb shp\u00ebrndarjes s\u00eb sh\u00ebrbimeve. Disa m\u00eb von\u00eb, n\u00eb vitin 2012, n\u00eb samitin arkitektonik, modeli u riem\u00ebrua n\u00eb mikrosh\u00ebrbim. K\u00ebshtu, q\u00ebllimi fillestar i p\u00ebrdorimit t\u00eb mikrosh\u00ebrbimeve ishte p\u00ebrmir\u00ebsimi i famsh\u00ebm time to market<\/b>.<\/p>\n

N\u00eb \"val\u00ebn e hype-it\" mikrosh\u00ebrbimet ishin n\u00eb vitin 2015. Sipas disa studimeve, asnj\u00eb konferenc\u00eb nuk kalonte pa nj\u00eb raport mbi mikrosh\u00ebrbimet. M\u00eb shum\u00eb se kaq, disa konferenca ishin dedikuar ekskluzivisht mikrosh\u00ebrbimeve. Tani shum\u00eb projekte fillojn\u00eb me p\u00ebrdorimin e k\u00ebtij stili arkitektonik, dhe n\u00ebse projekti p\u00ebrfshin tonelata kodit legacy, me siguri po realizohet aktivisht migrimi n\u00eb mikrosh\u00ebrbime.<\/p>\n

Pavar\u00ebsisht t\u00eb gjitha t\u00eb dh\u00ebnave t\u00eb m\u00ebsip\u00ebrme, numri i zhvilluesve q\u00eb mund t\u00eb p\u00ebrcaktojn\u00eb konceptin e \"mikrosh\u00ebrbim\" \u00ebsht\u00eb ende mjaft i vog\u00ebl. Por p\u00ebr k\u00ebt\u00eb do t\u00eb flasim pak m\u00eb von\u00eb\u2026<\/p>\n

Monolit<\/h2>\n

\nStili arkitektonik q\u00eb kund\u00ebrshtohet me mikrosh\u00ebrbimin \u00ebsht\u00eb monoliti (ose \"t\u00eb gjitha n\u00eb nj\u00eb\"). Nuk ka kuptim t\u00eb flasim p\u00ebr monolitin, prandaj do t\u00eb rendis menj\u00ebher\u00eb disavantazhet e k\u00ebtij stili arkitektonik, t\u00eb cilat nxisin zhvillimin e m\u00ebtejsh\u00ebm t\u00eb stileve arkitektonike: p\u00ebrmasat, lidhshm\u00ebria, shp\u00ebrndarja, shkall\u00ebzueshm\u00ebria, q\u00ebndrueshm\u00ebria dhe ngurt\u00ebsia. M\u00eb posht\u00eb ju propozoj t\u00eb njihemi me \u00e7do nj\u00ebri nga disavantazhet ve\u00e7 e ve\u00e7.<\/p>\n

Madh\u00ebsia<\/h3>\n

\nMonolit \u00ebsht\u00eb shum\u00eb i madh. Ai komunikon zakonisht me nj\u00eb baz\u00eb t\u00eb dh\u00ebnash shum\u00eb t\u00eb madhe. Aplikimi b\u00ebhet tep\u00ebr i madh p\u00ebr t'u kuptuar nga nj\u00eb zhvillues i vet\u00ebm n\u00eb parim. Vet\u00ebm ata q\u00eb kan\u00eb kaluar shum\u00eb koh\u00eb me k\u00ebt\u00eb kod mund ta punojn\u00eb mir\u00eb me monolitin, nd\u00ebrsa fillestar\u00ebt do t\u00eb kalojn\u00eb shum\u00eb koh\u00eb duke u munduar t\u00eb kuptojn\u00eb monolitin dhe nuk \u00ebsht\u00eb e sigurt q\u00eb do t\u00eb arrijn\u00eb ta kuptojn\u00eb. Zakonisht, gjat\u00eb pun\u00ebs me monolitin ka gjithmon\u00eb nj\u00eb \u201csenior\u201d t\u00eb caktuar, i cili e njeh monolitin m\u00eb shum\u00eb ose m\u00eb pak mir\u00eb dhe ndihmon zhvilluesit e rinj p\u00ebr nj\u00eb vit deri n\u00eb nj\u00eb vit e gjysm\u00eb. Natyrisht, ky senior \u00ebsht\u00eb nj\u00eb pik\u00eb e vetme d\u00ebshtimi, dhe largimi i tij mund t\u00eb \u00e7oj\u00eb n\u00eb vdekjen e monolitit. <\/p>\n

P\u00ebrgjegjshm\u00ebria<\/h3>\n

\nMonoliti \u00ebsht\u00eb nj\u00eb \u2018top i madh dhe i pista\u2019 (big ball of mud), dhe ndryshimet n\u00eb t\u00eb 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\u00ebmtoni monolitin n\u00eb nj\u00eb tjet\u00ebr (e nj\u00ebjta gj\u00eb si \u2018kemi b\u00ebr\u00eb nj\u00eb gisht, dhe *@ ra\u2019). Kjo lidhet me faktin se komponent\u00ebt n\u00eb monolit kan\u00eb lidhje shum\u00eb komplekse dhe, m\u00eb e r\u00ebnd\u00ebsishmja, jo t\u00eb qarta.<\/p>\n

Zhvillimi<\/h3>\n

\nZhvillimi i monolitit, p\u00ebr shkak t\u00eb lidhjeve t\u00eb komplikuara midis komponent\u00ebve t\u00eb tij, \u00ebsht\u00eb nj\u00eb proces i gjat\u00eb me nj\u00eb ritual t\u00eb vetin. Ky ritual zakonisht nuk \u00ebsht\u00eb plot\u00ebsisht i standardizuar dhe transmetohet 'nga goja n\u00eb goj\u00eb'. <\/p>\n

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

\nModulet e monolitit mund t\u00eb ken\u00eb k\u00ebrkesa konfliktuoze p\u00ebr burime, p\u00ebr k\u00ebt\u00eb arsye \u00ebsht\u00eb e nevojshme t\u00eb k\u00ebrkohet nj\u00eb kompromis n\u00eb aspektin e harduerit. Imagjinoni se monoliti juaj p\u00ebrb\u00ebhet nga sh\u00ebrbimet A dhe B. Sh\u00ebrbimi A ka nevoj\u00eb p\u00ebr nj\u00eb hard disk t\u00eb madh, nd\u00ebrsa sh\u00ebrbimi B k\u00ebrkon memorie. N\u00eb k\u00ebt\u00eb rast, ose ma\u0161ina ku vendoset monoliti duhet t\u00eb p\u00ebrmbush\u00eb k\u00ebrkesat e t\u00eb dy sh\u00ebrbimeve, ose do t\u00eb duhet t\u00eb \u00e7aktivizoni dorazi nj\u00eb nga sh\u00ebrbimet.<\/p>\n

Nj\u00eb shembull tjet\u00ebr (m\u00eb klasik): sh\u00ebrbimi A \u00ebsht\u00eb shum\u00eb m\u00eb i popullarizuar sesa sh\u00ebrbimi B, k\u00ebshtu q\u00eb d\u00ebshironi q\u00eb t\u00eb keni 100 sh\u00ebrbime A dhe 10 sh\u00ebrbime B. P\u00ebrs\u00ebri, ka dy alternativa: ose zhvilloni 100 monolite t\u00eb plota, ose n\u00eb disa prej tyre do t\u00eb duhet t\u00eb \u00e7aktivizoni dorazi sh\u00ebrbimet B. <\/p>\n

Besueshm\u00ebria<\/h3>\n

\nPasi t\u00eb gjitha sh\u00ebrbimet jan\u00eb s\u00eb bashku, n\u00ebse monoliti d\u00ebshtojn\u00eb, t\u00eb gjitha sh\u00ebrbimet do t\u00eb bien nj\u00ebkoh\u00ebsisht. 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, por nga ana tjet\u00ebr, p\u00ebr shkak t\u00eb nj\u00eb gabimi n\u00eb funksionalitetin q\u00eb e p\u00ebrdor 0.001% e p\u00ebrdoruesve, mund t\u00eb humbni t\u00eb gjith\u00eb p\u00ebrdoruesit e sistemit tuaj. <\/p>\n

Kritik\u00eb<\/h3>\n

\n\u0412\u0432\u0438\u0434\u0443 \u0440\u0430\u0437\u043c\u0435\u0440\u0430 \u043c\u043e\u043d\u043e\u043b\u0438\u0442\u0430 \u0442\u044f\u0436\u0435\u043b\u043e \u043f\u0435\u0440\u0435\u0439\u0442\u0438 \u043d\u0430 \u043d\u043e\u0432\u044b\u0435 \u0442\u0435\u0445\u043d\u043e\u043b\u043e\u0433\u0438\u0438. \u041a\u0430\u043a \u0441\u043b\u0435\u0434\u0441\u0442\u0432\u0438\u0435, \u043e\u0442\u0434\u0435\u043b\u044c\u043d\u043e\u0439 \u0437\u0430\u0434\u0430\u0447\u0435\u0439 \u0432\u044b\u0440\u0438\u0441\u043e\u0432\u044b\u0432\u0430\u0435\u0442 \u0443\u0434\u0435\u0440\u0436\u0430\u043d\u0438\u0435 \u0442\u043e\u0433\u043e \u0441\u0430\u043c\u043e\u0433\u043e \u0443\u0441\u043b\u043e\u0432\u043d\u043e\u0433\u043e senior’\u0430. \u0412\u044b\u0431\u0440\u0430\u043d\u043d\u044b\u0439 \u043d\u0430 \u0441\u0442\u0430\u0440\u0442\u0435 \u043f\u0440\u043e\u0435\u043a\u0442\u0430 \u0442\u0435\u0445\u043d\u043e\u043b\u043e\u0433\u0438\u0447\u0435\u0441\u043a\u0438\u0439 \u0441\u0442\u0435\u043a \u043c\u043e\u0436\u0435\u0442 \u0441\u0442\u0430\u0442\u044c \u0431\u043b\u043e\u043a\u043e\u043c, \u043f\u0440\u0435\u043f\u044f\u0442\u0441\u0442\u0432\u0443\u044e\u0449\u0438\u043c \u0440\u0430\u0437\u0432\u0438\u0442\u0438\u044e \u043f\u0440\u043e\u0434\u0443\u043a\u0442\u0430. <\/p>\n

P\u00ebrfundim<\/h2>\n

\nHer\u00ebn tjet\u00ebr do t\u00eb flasim p\u00ebr m\u00ebnyrat se si njer\u00ebzit u p\u00ebrpoq\u00ebn t\u00eb zgjidhnin k\u00ebto probleme duke kaluar n\u00eb komponente dhe SOA.<\/p>\n

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

\n

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

<\/p>\n