{"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 lansimit t\u00eb kursit \u00abZhvillues Backend n\u00eb PHP\u00bb<\/a><\/noindex>, tradicionalisht ndajem me ju p\u00ebrkthimin e materialit t\u00eb dobish\u00ebm.<\/p>\n

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

\"Parimet
\n
\nSi rezultat, gjat\u00eb disa viteve t\u00eb fundit, qasjet ndaj zhvillimit dhe ofrimit t\u00eb aplikacioneve kan\u00eb ndryshuar seriozisht. K\u00ebto ishin l\u00ebvizje t\u00eb m\u00ebdha q\u00eb \u00e7uan n\u00eb formimin e nj\u00eb grupi parimesh. K\u00ebto parime ishin t\u00eb dobishme n\u00eb formimin e ekipit, dizajnimin, zhvillimin dhe shp\u00ebrndarjen e aplikacionit tuaj tek p\u00ebrdoruesit p\u00ebrfundimtar\u00eb. <\/a><\/noindex><\/p>\n

Parimet mund t\u00eb p\u00ebrmbledhen si m\u00eb posht\u00eb: aplikacioni duhet t\u00eb jet\u00eb i vog\u00ebl, i lidhur me rrjetin dhe t\u00eb ket\u00eb nj\u00eb arkitektur\u00eb t\u00eb orientuar nga zhvilluesi<\/i>. Duke u mb\u00ebshtetur n\u00eb k\u00ebto tri parime, mund t\u00eb krijoni nj\u00eb aplikacion t\u00eb besuesh\u00ebm dhe t\u00eb plot\u00eb, i cili mund t\u00eb shp\u00ebrndahet shpejt dhe n\u00eb m\u00ebnyr\u00eb t\u00eb sigurt tek p\u00ebrdoruesit p\u00ebrfundimtar\u00eb, si dhe t\u00eb jet\u00eb i leht\u00eb p\u00ebr t'u skalier dhe zgjeruar.<\/p>\n

\"Parimet
\n
\nSecili nga parimet e propozuara ka nj\u00eb num\u00ebr aspektesh q\u00eb ne do t'i diskutojm\u00eb p\u00ebr t\u00eb treguar se si secili parim kontribuon n\u00eb arritjen e q\u00ebllimit p\u00ebrfundimtar, i cili \u00ebsht\u00eb t\u00eb ofrojm\u00eb aplikacione 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 se p\u00ebrdorni parimin e vog\u00eblsis\u00eb<\/i>\u00bb.<\/p>\n

Shpresojm\u00eb se ky artikull do t'ju inkurajoj\u00eb t\u00eb p\u00ebrdorni parimet e propozuara p\u00ebr nd\u00ebrtimin e aplikacioneve moderne, t\u00eb cilat do ta sigurojn\u00eb nj\u00eb qasje t\u00eb p\u00ebrbashk\u00ebt n\u00eb dizajnin n\u00eb kontekstin e nj\u00eb grumbulli teknologjish q\u00eb rritet vazhdimisht. <\/p>\n

Duke aplikuar k\u00ebto parime, do t\u00eb zbuloni se po shfryt\u00ebzoni tendencat e fundit n\u00eb zhvillimin e software-it, duke p\u00ebrfshir\u00eb qasjen DevOps<\/a><\/noindex> n\u00eb zhvillimin dhe shp\u00ebrndarjen e aplikacioneve, p\u00ebrdorimin e en\u00ebve (p.sh., Docker<\/a><\/noindex>) dhe kornizave p\u00ebr orkestrimin e en\u00ebve (p.sh., Kubernetes<\/a><\/noindex>), p\u00ebrdorimin e mikrosh\u00ebrbimeve (p\u00ebrfshir\u00eb Arkitektur\u00ebn Mikrosh\u00ebrbimore NGINX<\/noindex> dhe arkitektura e rrjetit<\/a><\/noindex> p\u00ebr aplikacionet mikrosh\u00ebrbimore.<\/p>\n

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

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

Shumica e zhvilluesve kan\u00eb vet\u00ebm nj\u00eb p\u00ebrceptim 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 definicion i qart\u00eb p\u00ebr k\u00ebt\u00eb koncept.<\/p>\n

Nj\u00eb aplikacion modern mb\u00ebshtet disa klient\u00eb, qofshin ato nd\u00ebrfaqe p\u00ebrdoruesi n\u00eb bibliotek\u00ebn JavaScript React, nj\u00eb aplikacion mobil p\u00ebr Android ose iOS, ose nj\u00eb aplikacion q\u00eb lidhet me nj\u00eb tjet\u00ebr p\u00ebrmes API-s\u00eb. Nj\u00eb aplikacion modern n\u00ebnkupton pranin\u00eb e nj\u00eb numri t\u00eb pacaktuar klient\u00ebsh, p\u00ebr t\u00eb cil\u00ebt ai 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 q\u00eb k\u00ebrkohen. API duhet t\u00eb jet\u00eb e pandryshueshme dhe e q\u00ebndrueshme, dhe jo e shkruar posa\u00e7\u00ebrisht p\u00ebr ndonj\u00eb k\u00ebrkes\u00eb specifike nga ndonj\u00eb klient t\u00eb caktuar. API \u00ebsht\u00eb e aksesueshme p\u00ebrmes HTTP(S) dhe siguron qasje n\u00eb t\u00eb gjith\u00eb funksionalitetin q\u00eb ka nd\u00ebrfaqja GUI ose CLI. <\/p>\n

T\u00eb dh\u00ebnat duhet t\u00eb jen\u00eb t\u00eb aksesueshme n\u00eb nj\u00eb format t\u00eb njohur dhe t\u00eb p\u00ebrshtatsh\u00ebm, si 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 dukshme.<\/p>\n

Aplikacionet moderne nd\u00ebrtohen mbi nj\u00eb grup modern, dhe nj\u00eb grup modern \u00ebsht\u00eb ai q\u00eb mb\u00ebshtet aplikacione t\u00eb tilla, p\u00ebr rrjedhoj\u00eb. Ky grup e lejon zhvilluesin t\u00eb krijoj\u00eb me leht\u00ebsi nj\u00eb aplikacion me 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 me leht\u00ebsi. Me fjal\u00eb t\u00eb tjera, grupi modern p\u00ebrputhet me elementet e Aplikasi-it t\u00eb Dymb\u00ebdhjet\u00eb-Faktor\u00ebsh p\u00ebr mikrosherbimesh<\/a><\/noindex>. <\/p>\n

Versionet m\u00eb t\u00eb njohura t\u00eb k\u00ebtij lloji t\u00eb grupit bazohen n\u00eb Java<\/a><\/noindex>, Python<\/a><\/noindex>, Node<\/a><\/noindex>, Ruby<\/a><\/noindex>, PHP<\/a><\/noindex> dhe Go<\/a><\/noindex>. Arkitektura Mikrosh\u00ebrbimore NGINX<\/a><\/noindex> p\u00ebrfaq\u00ebson nj\u00eb shembull t\u00eb grupit modern, i realizuar n\u00eb secilin prej gjuh\u00ebve t\u00eb p\u00ebrmendura.<\/p>\n

Vini re se ne nuk po propagandojm\u00eb ekskluzivisht qasjen mikrosh\u00ebrbimore. Shum\u00eb prej jush punojn\u00eb me monolite q\u00eb duhet t\u00eb zhvillohen, nd\u00ebrsa t\u00eb tjer\u00eb po merren me aplikacione SOA q\u00eb zgjerohen dhe zhvillohen p\u00ebr t'u b\u00ebr\u00eb aplikacione mikrosh\u00ebrbimore. T\u00eb tret\u00ebt po l\u00ebvizin n\u00eb drejtimin e aplikacioneve pa server (serverless), nd\u00ebrsa disa po implementojn\u00eb kombinime t\u00eb asaj q\u00eb \u00ebsht\u00eb p\u00ebrmendur m\u00eb lart. Parimet e p\u00ebrshkruara n\u00eb artikull jan\u00eb t\u00eb aplikueshme p\u00ebr secil\u00ebn nga k\u00ebto sisteme me disa ndryshime t\u00eb vogla. <\/p>\n

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

Tani q\u00eb arrit\u00ebm nj\u00eb kuptim t\u00eb p\u00ebrbashk\u00ebt p\u00ebr at\u00eb se \u00e7far\u00eb jan\u00eb aplikacionet moderne dhe staku modern, \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, zbatimin dhe mb\u00ebshtetje t\u00eb nj\u00eb aplikacioni modern.<\/p>\n

Nj\u00eb nga parimet \u00ebsht\u00eb \"krijo aplikacione t\u00eb vogla\", le t\u00eb e quajm\u00eb thjesht principi i vogl\u00ebsis\u00eb<\/i>. Ekzistojn\u00eb aplikacione tep\u00ebr t\u00eb nd\u00ebrlikuara, t\u00eb p\u00ebrb\u00ebr\u00eb nga shum\u00eb komponent\u00eb l\u00ebviz\u00ebs. Nga ana tjet\u00ebr, nd\u00ebrtimi i nj\u00eb aplikacioni nga komponente t\u00eb vogla dhe discrete leht\u00ebson projektimin, mir\u00ebmbajtjen dhe funksionimin e tij n\u00eb p\u00ebrgjith\u00ebsi. (Vini re, ne tham\u00eb \"leht\u00ebson\", dhe jo \"b\u00ebn t\u00eb leht\u00eb\").<\/p>\n

Princi i dyt\u00eb \u00ebsht\u00eb se ne mund t\u00eb rrisim produktivitetin e zhvilluesve duke i ndihmuar ata t\u00eb p\u00ebrq\u00ebndrohen n\u00eb funksionalitetet q\u00eb po zhvillojn\u00eb, dhe n\u00eb t\u00eb nj\u00ebjt\u00ebn koh\u00eb duke i liruar ata nga shqet\u00ebsimet p\u00ebr infrastruktur\u00ebn dhe CI\/CD gjat\u00eb zbatimit. Pra, me pak fjal\u00eb, qasja jon\u00eb \u00ebsht\u00eb e orientuar drejt zhvilluesve<\/i>.<\/p>\n

N\u00eb fund, gjith\u00e7ka q\u00eb lidhet me aplikacionin tuaj duhet t\u00eb jet\u00eb e lidhur me rrjetin. Gjat\u00eb 20 viteve t\u00eb fundit kemi b\u00ebr\u00eb p\u00ebrparime t\u00eb konsiderueshme drejt s\u00eb ardhmes rrjetore, pasi rrjetet kan\u00eb b\u00ebr\u00eb m\u00eb t\u00eb shpejt\u00eb, nd\u00ebrsa aplikacionet jan\u00eb b\u00ebr\u00eb m\u00eb t\u00eb nd\u00ebrlikuara. Si\u00e7 e kemi zbuluar, nj\u00eb aplikacion modern duhet t\u00eb p\u00ebrdoret n\u00ebp\u00ebrmjet rrjetit nga shum\u00eb klient\u00eb t\u00eb ndrysh\u00ebm. Aplikimi i mendimit rrjetor n\u00eb arkitektur\u00eb ka p\u00ebrpar\u00ebsi t\u00eb m\u00ebdha, t\u00eb cilat lidhen mir\u00eb me principi i vogl\u00ebsis\u00eb<\/i> dhe konceptin e qasjes, t\u00eb orientuar drejt zhvilluesve<\/i>.<\/p>\n

N\u00ebse gjat\u00eb zhvillimit dhe zbatimit t\u00eb aplikacionit mbani mend k\u00ebto principe, do t\u00eb keni nj\u00eb avantazh t\u00eb padiskutuesh\u00ebm n\u00eb zhvillimin dhe dor\u00ebzimin e produktit tuaj.<\/p>\n

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

Principi i vogl\u00ebsis\u00eb<\/b><\/p>\n

Truri i njeriut ka v\u00ebshtir\u00ebsi t\u00eb perceptoj\u00eb nj\u00eb sasi t\u00eb madhe informacioni nj\u00ebkoh\u00ebsisht. N\u00eb psikologji, termi ngarkesa kogitative p\u00ebrshkruan sasin\u00eb e p\u00ebrgjithshme t\u00eb p\u00ebrpjekjeve mendore q\u00eb nevojiten p\u00ebr t\u00eb mbajtur informacionin n\u00eb memorie. Reduktimi i ngarkes\u00ebs kogitative p\u00ebr zhvilluesit \u00ebsht\u00eb prioritet, pasi k\u00ebshtu ata mund t\u00eb p\u00ebrq\u00ebndrohen n\u00eb zgjidhjen e problemeve, p\u00ebrve\u00e7se t\u00eb mbajn\u00eb mend modelin kompleks aktual t\u00eb gjith\u00eb aplikacionit dhe funksionalitetet q\u00eb po zhvillojn\u00eb. <\/p>\n

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