{"id":34140,"date":"2019-10-31T21:56:35","date_gmt":"2019-10-31T18:56:35","guid":{"rendered":"https:\/\/prohoster.info\/blog\/printsipy-razrabotki-sovremennyh-prilozhenij-ot-nginx-chast-1\/"},"modified":"2019-10-31T21:56:35","modified_gmt":"2019-10-31T18:56:35","slug":"printsipy-razrabotki-sovremennyh-prilozhenij-ot-nginx-chast-1","status":"publish","type":"post","link":"https:\/\/prohoster.info\/sq\/blog\/administrirovanie\/printsipy-razrabotki-sovremennyh-prilozhenij-ot-nginx-chast-1","title":{"rendered":"Parimet e zhvillimit t\u00eb aplikacioneve moderne nga NGINX. Pjesa 1","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"

P\u00ebrsh\u00ebndetje, miq. N\u00eb prag t\u00eb nisjes s\u00eb kursit \u00abZhvilluesi Backend n\u00eb PHP\u00bb<\/a><\/noindex>, tradicionalisht ndaje me ju p\u00ebrkthimin e materialit t\u00eb dobish\u00ebm.<\/p>\n

Softueri zgjidh gjithnj\u00eb e m\u00eb shum\u00eb detyra t\u00eb p\u00ebrditshme, duke u b\u00ebr\u00eb gjithnj\u00eb e m\u00eb i komplikuar. Si\u00e7 tha nj\u00eb her\u00eb Mark Andreessen, ai po p\u00ebrthith bot\u00ebn. <\/p>\n

\"Parimet
\n
\nSi rezultat, gjat\u00eb disa viteve t\u00eb fundit, qasjet ndaj zhvillimit dhe shp\u00ebrndarjes s\u00eb aplikacioneve jan\u00eb ndryshuar ndjesh\u00ebm. K\u00ebto ishin l\u00ebvizje t\u00eb m\u00ebdha, t\u00eb cilat \u00e7uan n\u00eb shfaqjen e nj\u00eb grupi parimesh. K\u00ebto parime kan\u00eb rezultuar t\u00eb dobishme n\u00eb formimin e ekipit, dizajnimin, zhvillimin dhe shp\u00ebrndarjen e aplikacionit tuaj p\u00ebr p\u00ebrdoruesit p\u00ebrfundimtar\u00eb. <\/a><\/noindex><\/p>\n

Parimet mund t\u00eb p\u00ebrmblidheshin si m\u00eb posht\u00eb: aplikacioni duhet t\u00eb jet\u00eb i vog\u00ebl, rrjetor dhe t\u00eb ket\u00eb nj\u00eb arkitektur\u00eb t\u00eb orientuar ndaj zhvilluesit<\/i>. Duke u mb\u00ebshtetur n\u00eb k\u00ebto tre parime, mund t\u00eb krijoni nj\u00eb aplikacion t\u00eb besuesh\u00ebm, komplekse, q\u00eb mund t\u00eb shp\u00ebrndahet shpejt dhe sigurt p\u00ebr p\u00ebrdoruesin p\u00ebrfundimtar, si dhe t\u00eb shkall\u00ebzohet dhe zgjerohet leht\u00ebsisht.<\/p>\n

\"Parimet
\n
\n\u00c7do nj\u00eb nga parimet e propozuara ka nj\u00eb s\u00ebr\u00eb aspektesh, t\u00eb cilat ne do t'i diskutojm\u00eb p\u00ebr t\u00eb treguar se si \u00e7do parim kontribuon n\u00eb arritjen e q\u00ebllimit p\u00ebrfundimtar, q\u00eb \u00ebsht\u00eb shp\u00ebrndarja e shpejt\u00eb e aplikacioneve t\u00eb besueshme q\u00eb jan\u00eb t\u00eb lehta p\u00ebr t'u mbajtur dhe p\u00ebrdorur. Ne do t\u00eb shqyrtojm\u00eb parimet n\u00eb krahasim me kund\u00ebrshtit\u00eb e tyre, p\u00ebr t\u00eb sqaruar se \u00e7far\u00eb do t\u00eb thot\u00eb, p\u00ebr shembull, \u00abSigurohuni q\u00eb t\u00eb p\u00ebrdorni parimin e vog\u00eblsis\u00eb<\/i>\u00bb.<\/p>\n

Shpresojm\u00eb se ky artikull do t'ju nxis\u00eb t\u00eb p\u00ebrdorni parimet e propozuara p\u00ebr nd\u00ebrtimin e aplikacioneve moderne, t\u00eb cilat do t\u00eb sigurojn\u00eb nj\u00eb qasje t\u00eb nj\u00ebtrajtshme n\u00eb dizajn n\u00eb kontekstin e nj\u00eb grumbulli teknologjish q\u00eb vazhdon t\u00eb rritet. <\/p>\n

Duke aplikuar k\u00ebto parime, do t\u00eb zbuloni se po shfryt\u00ebzoni tendencat m\u00eb t\u00eb fundit n\u00eb zhvillimin e softuerit, p\u00ebrfshir\u00eb qasjen DevOps<\/a><\/noindex> n\u00eb zhvillimin dhe shp\u00ebrndarjen e aplikacioneve, p\u00ebrdorimin e konteiner\u00ebve (p.sh., Docker<\/a><\/noindex>) dhe framework-eve p\u00ebr orkestrimin e konteiner\u00ebve (p.sh., Kubernetes<\/a><\/noindex>), p\u00ebrdorimin e mikrosh\u00ebrbimeve (duke p\u00ebrfshir\u00eb Arkitektur\u00ebn e Mikrosh\u00ebrbimeve NGINX<\/noindex> dhe arkitektur\u00ebn e komunikimit n\u00eb rrjet<\/a><\/noindex> p\u00ebr aplikacionet mikrosh\u00ebrbimore.<\/p>\n

\u00c7far\u00eb \u00ebsht\u00eb nj\u00eb aplikacion modern?<\/b><\/p>\n

Aplikacionet moderne? Grumbulli modern? \u00c7far\u00eb sakt\u00ebsisht do t\u00eb thot\u00eb \u00abmodern\u00bb? <\/p>\n

Shumica e zhvilluesve kan\u00eb vet\u00ebm nj\u00eb kuptim t\u00eb p\u00ebrgjithsh\u00ebm t\u00eb asaj q\u00eb p\u00ebrb\u00ebn nj\u00eb aplikacion modern, prandaj \u00ebsht\u00eb e nevojshme t\u00eb jepet nj\u00eb p\u00ebrcaktim i qart\u00eb i k\u00ebtij koncepti.<\/p>\n

Nj\u00eb aplikacion modern mb\u00ebshtet disa klient\u00eb, qofshin ato nj\u00eb nd\u00ebrfaqe p\u00ebrdoruesi n\u00eb bibliotek\u00ebn JavaScript React, nj\u00eb aplikacion celular p\u00ebr Android ose iOS, ose nj\u00eb aplikacion q\u00eb lidhet me nj\u00eb tjet\u00ebr p\u00ebrmes API. Nj\u00eb aplikacion modern n\u00ebnkupton pranin\u00eb e nj\u00eb numri t\u00eb pap\u00ebrcaktuar klient\u00ebsh, p\u00ebr t\u00eb cil\u00ebt ofron t\u00eb dh\u00ebna ose sh\u00ebrbime.<\/p>\n

Nj\u00eb aplikacion modern ofron nj\u00eb API p\u00ebr qasje n\u00eb t\u00eb dh\u00ebnat dhe sh\u00ebrbimet e k\u00ebrkuara. API duhet t\u00eb jet\u00eb e pandryshueshme dhe e q\u00ebndrushme, dhe jo e shkruar specifikisht p\u00ebr nj\u00eb k\u00ebrkes\u00eb t\u00eb caktuar nga ndonj\u00eb klient t\u00eb ve\u00e7ant\u00eb. API \u00ebsht\u00eb e aksesueshme p\u00ebrmes HTTP(S) dhe siguron qasje n\u00eb t\u00eb gjith\u00eb funksionalitetin q\u00eb ka GUI ose CLI. <\/p>\n

T\u00eb dh\u00ebnat duhet t\u00eb jen\u00eb t\u00eb aksesueshme n\u00eb nj\u00eb format t\u00eb pranuar, t\u00eb p\u00ebrputhsh\u00ebm, si\u00e7 \u00ebsht\u00eb JSON. API ofron objekte dhe sh\u00ebrbime n\u00eb nj\u00eb form\u00eb t\u00eb kuptueshme dhe t\u00eb organizuar, p\u00ebr shembull, API-t\u00eb RESTful ose GraphQL ofrojn\u00eb nj\u00eb nd\u00ebrfaqe t\u00eb p\u00ebrshtatshme.<\/p>\n

Aplikacionet moderne nd\u00ebrtohen mbi nj\u00eb stak modern, dhe nj\u00eb stak modern \u00ebsht\u00eb ai stak q\u00eb mb\u00ebshtet k\u00ebto aplikacione p\u00ebrkat\u00ebse. Ky stak lejon zhvilluesin t\u00eb krijoj\u00eb me leht\u00ebsi nj\u00eb aplikacion me nj\u00eb nd\u00ebrfaqe HTTP dhe pika t\u00eb qarta API. Qasja e zgjedhur do t'i lejoj\u00eb aplikacionit tuaj t\u00eb pranoj\u00eb dhe d\u00ebrgoj\u00eb t\u00eb dh\u00ebna n\u00eb formatin JSON. N\u00eb tjera fjal\u00eb, staku modern p\u00ebrmbush element\u00ebt e aplikacionit Nj\u00ebmb\u00ebdhjet\u00eb-Faktor. mikrosh\u00ebrbimeve<\/a><\/noindex>. <\/p>\n

Versionet popullore t\u00eb k\u00ebtij lloji staku bazohen n\u00eb Java<\/a><\/noindex>, Python<\/a><\/noindex>, Nyja<\/a><\/noindex>, Ruby<\/a><\/noindex>, PHP<\/a><\/noindex> dhe Go<\/a><\/noindex>. Arkitektura Mikroservizore NGINX<\/a><\/noindex> p\u00ebrfaq\u00ebson nj\u00eb shembull t\u00eb stakut modern, t\u00eb implementuar n\u00eb \u00e7do nj\u00eb nga gjuh\u00ebt e p\u00ebrmendura.<\/p>\n

Vini re se ne nuk promovojm\u00eb ekskluzivisht qasjen mikroservizore. Shum\u00eb nga ju punoni me monolite q\u00eb duhet t\u00eb evoluojn\u00eb, nd\u00ebrsa t\u00eb tjer\u00eb kan\u00eb t\u00eb b\u00ebjn\u00eb me aplikacionet SOA q\u00eb zgjaten dhe zhvillohen n\u00eb aplikacione mikroservizore. T\u00eb tjer\u00eb po e ndjekin drejtimin e aplikacioneve pa server (serverless), dhe disa implementojn\u00eb kombinime t\u00eb asaj q\u00eb u p\u00ebrmend m\u00eb par\u00eb. Parimet e paraqitura n\u00eb k\u00ebt\u00eb artikull jan\u00eb t\u00eb aplikueshme p\u00ebr \u00e7do nj\u00eb nga k\u00ebto sisteme me disa ndryshime t\u00eb vogla. <\/p>\n

Parimet<\/b><\/p>\n

Tani, kur arrit\u00ebm nj\u00eb kuptim t\u00eb p\u00ebrbashk\u00ebt p\u00ebr \u00e7far\u00eb jan\u00eb aplikacionet moderne dhe stoku modern, tani \u00ebsht\u00eb koha t\u00eb thellohemi n\u00eb parimet e arkitektur\u00ebs dhe zhvillimit q\u00eb do t'ju sh\u00ebrbejn\u00eb mir\u00eb n\u00eb zhvillimin, implementimin dhe mb\u00ebshtetjes s\u00eb nj\u00eb aplikacioni modern.<\/p>\n

Nj\u00eb nga parimet \u00ebsht\u00eb \"krijoni aplikacione t\u00eb vogla\", le ta quajm\u00eb thjesht principi i voglis\u00eb<\/i>. Ekzistojn\u00eb aplikacione jasht\u00ebzakonisht komplekse q\u00eb p\u00ebrb\u00ebhen nga shum\u00eb komponent\u00eb t\u00eb l\u00ebvizsh\u00ebm. Nga ana tjet\u00ebr, nd\u00ebrtimi i nj\u00eb aplikacioni nga komponente t\u00eb vogla dhe diskrete e thjeshton projektimin, mir\u00ebmbajtjen dhe funksionimin e tij n\u00eb p\u00ebrgjith\u00ebsi. (Vini re, ne tham\u00eb \"thjeshton\" dhe jo \"b\u00ebn t\u00eb thjesht\u00eb\").<\/p>\n

Parimi i dyt\u00eb \u00ebsht\u00eb se ne mund t\u00eb rrisim produktivitetin e zhvilluesve duke i ndihmuar ata t\u00eb p\u00ebrqendrohen n\u00eb funksionalitetet q\u00eb ata po zhvillojn\u00eb, duke i \u00e7liruar nga shqet\u00ebsimet p\u00ebr infrastruktur\u00ebn dhe CI\/CD gjat\u00eb implementimit. Pra, n\u00eb dy fjal\u00eb, qasja jon\u00eb \u00ebsht\u00eb orientuar ndaj zhvilluesve<\/i>.<\/p>\n

N\u00eb fund, gjith\u00e7ka q\u00eb ka t\u00eb b\u00ebj\u00eb me aplikacionin tuaj duhet t\u00eb jet\u00eb e lidhur me rrjetin. Gjat\u00eb 20 viteve t\u00eb fundit, ne kemi avancuar shum\u00eb drejt nj\u00eb t\u00eb ardhmeje rrjetore, pasi rrjetet kan\u00eb b\u00ebr\u00eb p\u00ebrparime t\u00eb m\u00ebdha dhe aplikacionet jan\u00eb b\u00ebr\u00eb m\u00eb komplekse. Si\u00e7 e kemi kuptuar, nj\u00eb aplikacion modern duhet t\u00eb p\u00ebrdoret n\u00eb rrjet nga shum\u00eb klient\u00eb t\u00eb ndrysh\u00ebm. Aplikimi i mendimit t\u00eb rrjetit n\u00eb arkitektur\u00eb ka p\u00ebrfitime t\u00eb r\u00ebnd\u00ebsishme q\u00eb p\u00ebrshtaten mir\u00eb me principi i voglis\u00eb<\/i> dhe konceptin e qasjes, orientuar ndaj zhvilluesve<\/i>.<\/p>\n

N\u00ebse gjat\u00eb zhvillimit dhe implementimit t\u00eb aplikacionit mbani mend parimet e p\u00ebrmendura, do t\u00eb keni nj\u00eb avantazh t\u00eb pakund\u00ebrshtuesh\u00ebm n\u00eb zhvillimin dhe dor\u00ebzimin e produktit tuaj.<\/p>\n

Le t\u00eb shqyrtojm\u00eb k\u00ebto tri parime m\u00eb n\u00eb detaje.<\/p>\n

Principi i voglis\u00eb<\/b><\/p>\n

Mendja njer\u00ebzore ka v\u00ebshtir\u00ebsi t\u00eb perceptoj\u00eb nj\u00eb sasi t\u00eb madhe informacioni nj\u00ebkoh\u00ebsisht. N\u00eb psikologji, termi ngarkesa kognitive i referohet sasis\u00eb s\u00eb p\u00ebrgjithshme t\u00eb p\u00ebrpjekjeve mendore t\u00eb nevojshme p\u00ebr t\u00eb mbajtur informacionin n\u00eb memorie. Reduktimi i ngarkes\u00ebs kognitive p\u00ebr zhvilluesit \u00ebsht\u00eb nj\u00eb prioritet, pasi n\u00eb k\u00ebt\u00eb rast ata mund t\u00eb p\u00ebrqendrohen n\u00eb zgjidhjen e problemeve, n\u00eb vend q\u00eb t\u00eb mbajn\u00eb n\u00eb mend modelin kompleks aktual t\u00eb gjith\u00eb aplikacionit dhe funksionalitetet q\u00eb po zhvillohen. <\/p>\n

\"Parimet
\n
\nAplikacionet \u00e7antarizohen p\u00ebr arsyet e m\u00ebposhtme:<\/p>\n