{"id":55231,"date":"2020-01-16T00:00:00","date_gmt":"2020-01-15T21:00:00","guid":{"rendered":"https:\/\/prohoster.info\/blog\/blog_prohoster\/pro-multitenancy"},"modified":"2020-02-18T14:03:19","modified_gmt":"2020-02-18T11:03:19","slug":"pro-multitenancy","status":"publish","type":"post","link":"https:\/\/prohoster.info\/sq\/blog\/administrirovanie\/pro-multitenancy","title":{"rendered":"Rreth multitenancy","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"<p>Fatkeq\u00ebsisht, ky term nuk ka nj\u00eb ekuivalent t\u00eb mir\u00eb n\u00eb gjuh\u00ebn shqipe. \u00abWikipedia\u00bb jep <noindex><a rel=\"nofollow\" href=\"http:\/\/ru.wikipedia.org\/wiki\/%D0%9C%D1%83%D0%BB%D1%8C%D1%82%D0%B8%D0%B0%D1%80%D0%B5%D0%BD%D0%B4%D0%BD%D0%BE%D1%81%D1%82%D1%8C\">p\u00ebrkthim<\/a><\/noindex> \u00abmultiarendim, qira e shumfisht\u00eb\u00bb. Ndonj\u00ebher\u00eb quhet edhe \u00abpron\u00ebsi e shumfisht\u00eb\u00bb. K\u00ebto terma mund t\u00eb jen\u00eb paksa t\u00eb ngat\u00ebrruar, sepse subjekti nuk lidhet n\u00eb thelb as me qiradh\u00ebnien dhe as me pron\u00ebsin\u00eb. Kjo \u00ebsht\u00eb nj\u00eb \u00e7\u00ebshtje e arkitektur\u00ebs s\u00eb softuerit dhe organizat\u00ebs s\u00eb tij operuese. Kjo e fundit \u00ebsht\u00eb po aq e r\u00ebnd\u00ebsishme. <\/p>\n<p>Ne filluam t\u00eb formojm\u00eb kuptimin ton\u00eb t\u00eb multitenancy nd\u00ebrsa filluam t\u00eb projektin qasjen drejt modelit t\u00eb pun\u00ebs me sh\u00ebrbim n\u00eb \u00ab1C:Sip\u00ebrmarrja\u00bb. Kjo ndodhi disa vite m\u00eb par\u00eb. Dhe q\u00eb at\u00ebher\u00eb kuptimi yn\u00eb \u00ebsht\u00eb zgjeruar vazhdimisht. Ne vazhdimisht zbulojm\u00eb aspekte t\u00eb reja (p\u00ebrfitimet, disavantazhet, v\u00ebshtir\u00ebsit\u00eb, ve\u00e7orit\u00eb, etj.) lidhur me k\u00ebt\u00eb tem\u00eb. <\/p>\n<p><img decoding=\"async\" alt=\"Rreth multitenancy\" src=\"\/wp-content\/uploads\/2020\/01\/a14e60822b948ecd079722ed828f853f.jpg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<noindex><a rel=\"nofollow\" name=\"habracut\"><\/a><\/noindex><br \/>\nNdonj\u00ebher\u00eb zhvilluesit e kuptojn\u00eb multitenancy si nj\u00eb \u00e7\u00ebshtje mjaft t\u00eb thjesht\u00eb: \u00abp\u00ebr t\u00eb ruajtur t\u00eb dh\u00ebnat e disa organizatave n\u00eb nj\u00eb baz\u00eb t\u00eb vetme, \u00ebsht\u00eb e nevojshme t\u00eb shtoni nj\u00eb kolon\u00eb me identifikuesin e organizat\u00ebs n\u00eb t\u00eb gjitha tabelat dhe t\u00eb vendosni nj\u00eb filtrin mbi t\u00eb\u00bb. Ne gjithashtu, sigurisht, filluam pun\u00ebn ton\u00eb mbi k\u00ebt\u00eb \u00e7\u00ebshtje nga ky moment. Por shpejt e kuptuam se kjo \u00ebsht\u00eb vet\u00ebm nj\u00eb prej hap\u00ebsirave (po ashtu, e nd\u00ebrlikuar). N\u00eb t\u00eb v\u00ebrtet\u00eb, kjo \u00ebsht\u00eb nj\u00eb \u00abvendi i t\u00ebr\u00eb\u00bb. <\/p>\n<p>Ideja kryesore e multitenancy mund t\u00eb p\u00ebrshkruhet n\u00eb m\u00ebnyr\u00eb t\u00eb thjesht\u00eb. Nj\u00eb aplikacion i zakonsh\u00ebm \u00ebsht\u00eb nj\u00eb sht\u00ebpi, e cila \u00ebsht\u00eb e destinuar p\u00ebr jetes\u00ebn e nj\u00eb familjeje q\u00eb p\u00ebrdor infrastruktur\u00ebn e saj (muret, \u00e7atia, furnizimi me uj\u00eb, ngrohja, etj.). Nj\u00eb aplikacion multitenancy \u00ebsht\u00eb nj\u00eb nd\u00ebrtes\u00eb me apartamente. N\u00eb t\u00eb, \u00e7do familje p\u00ebrdor t\u00eb nj\u00ebjt\u00ebn infrastruktur\u00eb, por infrastruktura \u00ebsht\u00eb e nd\u00ebrtuar p\u00ebr gjith\u00eb nd\u00ebrtes\u00ebn si nj\u00eb entitet t\u00eb vet\u00ebm. <\/p>\n<p>A \u00ebsht\u00eb qasja e multitenancy e mir\u00eb apo e keqe? N\u00eb k\u00ebt\u00eb pik\u00eb, mund t\u00eb gjenden mendime shum\u00eb t\u00eb ndryshme. Duke u dukur, nuk ka \u00abmir\u00eb apo keq\u00bb n\u00eb terma absolute. Duhet t\u00eb krahasohen p\u00ebrfitimet dhe disavantazhet n\u00eb kontekstin e detyrave specifike q\u00eb zgjidhen. Por kjo \u00ebsht\u00eb nj\u00eb tem\u00eb e ve\u00e7ant\u00eb... <\/p>\n<p>N\u00eb kuptimin m\u00eb t\u00eb thjesht\u00eb, q\u00ebllimi i multitenancy \u00ebsht\u00eb t\u00eb zvog\u00ebloj\u00eb shpenzimet p\u00ebr mb\u00ebshtetje t\u00eb aplikacionit p\u00ebrmes \"shp\u00ebrndarjes\" s\u00eb shpenzimeve p\u00ebr infrastruktur\u00ebn. Kjo \u00ebsht\u00eb nj\u00eb l\u00ebvizje e ngjashme me uljen e kostos s\u00eb aplikacionit p\u00ebrmes p\u00ebrdorimit t\u00eb nj\u00eb zgjidhjeje t\u00eb p\u00ebrdorur (ndoshta me konfiguroj\u00eb dhe modifikim), n\u00eb vend t\u00eb shkruarjes \"sip\u00ebr porosi\". N\u00eb nj\u00eb rast shoq\u00ebrohet zhvillimi, e n\u00eb tjetrin \u2013 operimi. <\/p>\n<p>Nd\u00ebrsa, t\u00eb p\u00ebrs\u00ebrisim, k\u00ebtu nuk ka nj\u00eb lidhje t\u00eb drejtp\u00ebrdrejt\u00eb me m\u00ebnyr\u00ebn e shitjes. Arkitektura e multitenancy mund t\u00eb aplikohet gjithashtu n\u00eb infrastruktur\u00ebn e IT korporative ose t\u00eb institucioneve p\u00ebr automatizimin e nj\u00eb numri t\u00eb madh t\u00eb filialeve, nd\u00ebrmarrjeve t\u00eb grupit. <\/p>\n<p>Mund t\u00eb thuhet se multitenancy \u00ebsht\u00eb jo vet\u00ebm nj\u00eb \u00e7\u00ebshtje e organizimit t\u00eb ruajtjes s\u00eb t\u00eb dh\u00ebnave. Kjo \u00ebsht\u00eb nj\u00eb model pune i aplikacionit t\u00ebr\u00ebsisht (duke p\u00ebrfshir\u00eb nj\u00eb pjes\u00eb t\u00eb konsiderueshme t\u00eb aspekteve t\u00eb arkitektur\u00ebs s\u00eb tij, modelin e implementimit, dhe organizimin e sh\u00ebrbimit). <\/p>\n<p>Ajo q\u00eb \u00ebsht\u00eb m\u00eb e komplikuar dhe interesante n\u00eb modelin e multitenancy, si\u00e7 na duket, \u00ebsht\u00eb se thelbi i aplikacionit \"ndahen\". Nj\u00eb pjes\u00eb e funksionalitetit punon me fusha specifike t\u00eb t\u00eb dh\u00ebnave (apartamentet) dhe \"nuk ka interes\" p\u00ebr at\u00eb q\u00eb ndodhet n\u00eb apartamentet e tjera. Nd\u00ebrsa nj\u00eb pjes\u00eb e percepton nd\u00ebrtes\u00ebn si nj\u00eb t\u00ebr\u00ebsi dhe punon menj\u00ebher\u00eb p\u00ebr t\u00eb gjith\u00eb banor\u00ebt. Megjithat\u00eb, kjo e fundit nuk mund t\u00eb abstenoj\u00eb nga fakti se k\u00ebto jan\u00eb apartamente t\u00eb ve\u00e7anta, dhe duhet t\u00eb sigurohet nj\u00eb nivel i nevojsh\u00ebm granulariteti dhe sigurie. <\/p>\n<p>N\u00eb \u00ab1C:Sip\u00ebrmarrja\u00bb, modeli i multitenancy implementohet n\u00eb nivelin e disa teknologjive. K\u00ebto jan\u00eb mekanizmat e platform\u00ebs \u00ab1C: Sip\u00ebrmarrja\u00bb, mekanizmat e \u00ab<noindex><a rel=\"nofollow\" href=\"http:\/\/www.1c.ru\/news\/info.jsp?id=16065\">1C: Teknologjia e publikimit t\u00eb zgjidhjeve 1cFresh<\/a><\/noindex>\u00bb dhe \u00ab<noindex><a rel=\"nofollow\" href=\"http:\/\/www.1c.ru\/news\/info.jsp?id=15382\">1C: Teknologjia e zhvillimit t\u00eb zgjidhjeve 1cFresh<\/a><\/noindex>\u00bb, mekanizmat <noindex><a rel=\"nofollow\" href=\"http:\/\/v8.1c.ru\/libraries\/ssl\/index.htm\">BSP<\/a><\/noindex> (bibliotekat e sistemeve standarde). <\/p>\n<p>\u00c7do nj\u00eb nga k\u00ebto elemente kontribuon n\u00eb nd\u00ebrtimin e infrastruktur\u00ebs s\u00eb p\u00ebrgjithshme t\u00eb nd\u00ebrtes\u00ebs me apartamente. Pse implementohet kjo n\u00eb disa teknologji dhe jo n\u00eb nj\u00eb t\u00eb vetme, p\u00ebr shembull, n\u00eb platform\u00eb? Para s\u00eb gjithash, sepse disa mekanizma, sipas mendimit ton\u00eb, jan\u00eb mjaft t\u00eb p\u00ebrshtatsh\u00ebm p\u00ebr t'u modifikuar n\u00eb var\u00ebsi t\u00eb varianti konkret t\u00eb implementimit. Por n\u00eb p\u00ebrgjith\u00ebsi, kjo \u00ebsht\u00eb nj\u00eb \u00e7\u00ebshtje e nd\u00ebrlikuar dhe ne vazhdimisht kemi p\u00ebrpara zgjedhjen \u2013 n\u00eb cilin nivel \u00ebsht\u00eb m\u00eb e mir\u00eb t\u00eb realizohet nj\u00eb aspekt i till\u00eb i multitenancy. <\/p>\n<p>E qart\u00eb se pjesa themelore e mekanizmave duhet t\u00eb implementohet n\u00eb platform\u00eb. Nj\u00eb shembull, ndarja e t\u00eb dh\u00ebnave. Kjo \u00ebsht\u00eb ajo nga e cila zakonisht fillon biseda p\u00ebr multitenancy. Por n\u00eb fund, modelin e multitenancy \"kaloi\" n\u00eb nj\u00eb pjes\u00eb t\u00eb konsiderueshme t\u00eb mekanizmave t\u00eb platform\u00ebs dhe k\u00ebrkoi p\u00ebrmir\u00ebsime t\u00eb tyre, ndonj\u00ebher\u00eb madje edhe rishqyrtim. <\/p>\n<p>N\u00eb nivelin e platform\u00ebs, ne kemi zhvilluar mekanizmat baz\u00eb. K\u00ebta lejojn\u00eb krijimin e aplikacioneve q\u00eb funksionojn\u00eb n\u00eb modelin multitenancy. Por p\u00ebr t\u00eb siguruar q\u00eb aplikacionet \"t\u00eb jetojn\u00eb dhe funksionojn\u00eb\" n\u00eb nj\u00eb model t\u00eb till\u00eb, \u00ebsht\u00eb e nevojshme t\u00eb kemi nj\u00eb sistem menaxhimi t\u00eb \"jet\u00ebs\" s\u00eb tyre. Teknologjit\u00eb 1cFresh dhe shtresa e unifikuar e logjik\u00ebs s\u00eb biznesit n\u00eb nivelin e BSP jan\u00eb p\u00ebrgjegj\u00ebse p\u00ebr k\u00ebt\u00eb. Ashtu si infrastruktura q\u00eb siguron banor\u00ebt me gjith\u00e7ka t\u00eb nevojshme n\u00eb nj\u00eb nd\u00ebrtes\u00eb shum\u00ebkat\u00ebshe, teknologjit\u00eb 1cFresh ofrojn\u00eb gjith\u00e7ka t\u00eb nevojshme p\u00ebr aplikacionet q\u00eb operojn\u00eb n\u00eb modelin multitenancy. Dhe p\u00ebr t'i lejuar aplikacionet t\u00eb komunikojn\u00eb me k\u00ebt\u00eb infrastruktur\u00eb (pa nevoj\u00ebn e ndryshimeve t\u00eb m\u00ebdha), ato p\u00ebrfshijn\u00eb \"portet\" p\u00ebrkat\u00ebse n\u00eb form\u00ebn e subsistemeve BSP. <\/p>\n<p>Nga k\u00ebndv\u00ebshtrimi i mekanizmave t\u00eb platform\u00ebs, \u00ebsht\u00eb e leht\u00eb t\u00eb vihet re se nd\u00ebrsa ne marrim p\u00ebrvoj\u00eb dhe zhvillojm\u00eb versionin cloud t\u00eb \"1C:Enterprise\", ne zgjedhim mekanizmat q\u00eb p\u00ebrfshihen n\u00eb k\u00ebt\u00eb arkitektur\u00eb. Le t\u00eb japim nj\u00eb shembull. N\u00eb modelin multitenancy, rolet e pjes\u00ebmarr\u00ebsve t\u00eb sh\u00ebrbimit t\u00eb aplikacioneve ndryshojn\u00eb ndjesh\u00ebm. Rol m\u00eb t\u00eb madh (nivel p\u00ebrgjegj\u00ebsie) ka ai q\u00eb p\u00ebrgjigjet p\u00ebr funksionimin e aplikacioneve. Ata tani kan\u00eb nevoj\u00eb p\u00ebr mjete m\u00eb t\u00eb fuqishme p\u00ebr kontrollin e aplikacioneve. Sepse p\u00ebrdoruesit e aplikacioneve (banor\u00ebt) i besojn\u00eb para s\u00eb gjithash ofruesit me t\u00eb cilin punojn\u00eb. P\u00ebr k\u00ebt\u00eb, ne realizuam n\u00eb versionin 8.3 nj\u00eb <noindex><a rel=\"nofollow\" href=\"https:\/\/wonderland.v8.1c.ru\/blog\/profili-bezopasnosti\/?sphrase_id=12972\">mekaniz\u00ebm t\u00eb profileve t\u00eb siguris\u00eb<\/a><\/noindex>. Ky mekaniz\u00ebm lejon administrator\u00ebt e ofruesve t\u00eb kufizojn\u00eb lirin\u00eb e zhvilluesve t\u00eb aplikacioneve me nivelin e nevojsh\u00ebm t\u00eb siguris\u00eb \u2013 n\u00eb thelb, t\u00eb izolojn\u00eb pun\u00ebn e aplikacionit p\u00ebr \u00e7do banor brenda kufijve t\u00eb caktuar t\u00eb \"sandbox\". <\/p>\n<p>Arkitektura p\u00ebr menaxhimin e aplikacioneve q\u00eb funksionojn\u00eb n\u00eb modin multitenancy (\u00e7ka realizohet n\u00eb teknologjit\u00eb 1cFresh dhe BSP) \u00ebsht\u00eb gjithashtu shum\u00eb interesante. K\u00ebtu, krahasuar me modelin e zakonsh\u00ebm t\u00eb implementimit, k\u00ebrkesat p\u00ebr automatizimin e proceseve t\u00eb menaxhimit rriten ndjesh\u00ebm. Ka dhjet\u00ebra nga k\u00ebto procese: krijimi i hap\u00ebsirave t\u00eb reja t\u00eb t\u00eb dh\u00ebnave (\"apartamente\"), p\u00ebrdit\u00ebsimi i aplikacioneve, p\u00ebrdit\u00ebsimi i informacionit rregullator, kopjimi i rezerv\u00ebs etj. Dhe, sigurisht, k\u00ebrkesat p\u00ebr nivelin e besueshm\u00ebris\u00eb dhe disponueshm\u00ebris\u00eb rriten. P\u00ebr shembull, p\u00ebr t\u00eb siguruar nj\u00eb komunikim t\u00eb besuesh\u00ebm t\u00eb aplikacioneve me komponent\u00ebt e sistemit t\u00eb menaxhimit, ne realizuam teknologjin\u00eb e sistemit t\u00eb thirrjeve asinkrone me dor\u00ebzimin e garantuar. <\/p>\n<p>Nj\u00eb moment shum\u00eb delikat \u00ebsht\u00eb m\u00ebnyra e shoq\u00ebrimit t\u00eb t\u00eb dh\u00ebnave dhe proceseve. Kjo duket e thjesht\u00eb (n\u00ebse dikujt i duket) vet\u00ebm n\u00eb shikim t\u00eb par\u00eb. Balanca midis centralizimit t\u00eb t\u00eb dh\u00ebnave dhe proceseve dhe decentralizimit paraqet v\u00ebshtir\u00ebsin\u00eb m\u00eb t\u00eb madhe. Nga nj\u00ebra an\u00eb, centralizimi lejon reduktimin e kostove (hap\u00ebsir\u00ebs s\u00eb diskut, burimeve t\u00eb procesor\u00ebve, p\u00ebrpjekjeve t\u00eb administrator\u00ebve\u2026). Nga ana tjet\u00ebr, kufizon lirin\u00eb e \"banor\u00ebve\". Kjo \u00ebsht\u00eb pik\u00ebrisht nj\u00eb nga momentet e \"ndarjes\" s\u00eb aplikacionit, kur zhvilluesi duhet t\u00eb mendoj\u00eb nj\u00ebher\u00ebsh p\u00ebr aplikacionin n\u00eb kuptimin e ngusht\u00eb (p\u00ebr sh\u00ebrbimin e nj\u00eb \"apartamenti\") dhe n\u00eb kuptimin e gjer\u00eb (p\u00ebr sh\u00ebrbimin e t\u00eb gjith\u00eb \"banor\u00ebve\"). <\/p>\n<p>Nj\u00eb shembull i till\u00eb i \"dilem\u00ebs\" mund t\u00eb merret nga informacioni rregullator dhe referues. Sigurisht, ka nj\u00eb t\u00ebrheqje t\u00eb madhe p\u00ebr ta b\u00ebr\u00eb at\u00eb t\u00eb p\u00ebrgjithsh\u00ebm p\u00ebr t\u00eb gjith\u00eb \"banor\u00ebt\" e sht\u00ebpis\u00eb. Kjo lejon t\u00eb ruhen n\u00eb nj\u00eb kopje, dhe t\u00eb p\u00ebrdit\u00ebsohen menj\u00ebher\u00eb p\u00ebr t\u00eb gjith\u00eb. Por ndodh q\u00eb nj\u00eb banor i caktuar ka nevoj\u00eb p\u00ebr ndryshime specifike. \u00c7udit\u00ebrisht, kjo ndodh n\u00eb praktik\u00eb, madje edhe p\u00ebr informacionin q\u00eb \u00ebsht\u00eb specifikuar nga rregullator\u00ebt (autoritetet shtet\u00ebrore). K\u00ebshtu del nj\u00eb pyetje e v\u00ebshtir\u00eb: a duhet t\u00eb b\u00ebhet informacioni i zakonsh\u00ebm apo jo? Natyrisht, \u00ebsht\u00eb t\u00ebrheq\u00ebse t\u00eb b\u00ebsh informacionin e p\u00ebrbashk\u00ebt p\u00ebr t\u00eb gjith\u00eb dhe t\u00eb ve\u00e7ant\u00eb p\u00ebr ata q\u00eb d\u00ebshirojn\u00eb. Dhe kjo \u00e7on n\u00eb nj\u00eb implementim shum\u00eb t\u00eb komplikuar. Por mbi k\u00ebt\u00eb ne po punojm\u00eb... <\/p>\n<p>Nj\u00eb shembull tjet\u00ebr \u00ebsht\u00eb projektimi i realizimit t\u00eb proceseve t\u00eb rregullta (t\u00eb kryera sipas nj\u00eb plani, t\u00eb iniciuara nga sistemi menaxhues etj.). Nga nj\u00ebra an\u00eb, ato mund t\u00eb realizohen p\u00ebr \u00e7do hap\u00ebsir\u00eb t\u00eb dh\u00ebnash ve\u00e7mas. Kjo \u00ebsht\u00eb m\u00eb e thjesht\u00eb dhe m\u00eb e p\u00ebrshtatshme. Por, nga ana tjet\u00ebr, granulariteti i till\u00eb i vog\u00ebl krijon nj\u00eb ngarkes\u00eb t\u00eb madhe p\u00ebr sistemin. P\u00ebr t\u00eb zbutur ngarkes\u00ebn, ne duam t\u00eb realizojm\u00eb procese t\u00eb p\u00ebrgjithshme. Por ato k\u00ebrkojn\u00eb nj\u00eb pun\u00eb m\u00eb t\u00eb kujdesshme. <\/p>\n<p>Natyrisht, lind nj\u00eb pyetje shum\u00eb t\u00eb r\u00ebnd\u00ebsishme. Si mund t\u00eb sigurojn\u00eb zhvilluesit e aplikacioneve funksionimin n\u00eb nj\u00eb m\u00ebnyr\u00eb multitenance? \u00c7far\u00eb duhet t\u00eb b\u00ebjn\u00eb p\u00ebr k\u00ebt\u00eb? Sigurisht, ne synojm\u00eb q\u00eb ngarkesa e \u00e7\u00ebshtjeve teknologjike dhe infrastrukturore t\u00eb bjer\u00eb sa m\u00eb shum\u00eb mbi teknologjin\u00eb e ofruar, nd\u00ebrsa zhvilluesi i aplikacionit t\u00eb mendoj\u00eb vet\u00ebm p\u00ebr detyrat e logjik\u00ebs biznesore. Por ashtu si me \u00e7\u00ebshtje t\u00eb tjera t\u00eb r\u00ebnd\u00ebsishme arkitekturore, zhvilluesit e aplikacioneve duhet t\u00eb ken\u00eb nj\u00ebfar\u00eb p\u00ebrvoje mbi funksionimin n\u00eb modelin multitenance dhe disa p\u00ebrpjekje do t\u00eb k\u00ebrkohen gjat\u00eb zhvillimit t\u00eb aplikacioneve. Pse? Sepse ekzistojn\u00eb momente, t\u00eb cilat teknologjia nuk mund t'i siguroj\u00eb automatikisht pa marr\u00eb parasysh semantik\u00ebn e t\u00eb dh\u00ebnave. P\u00ebr shembull, p\u00ebrcaktimi i kufijve t\u00eb ndarjes s\u00eb informacionit. Por ne p\u00ebrpiqemi q\u00eb k\u00ebto v\u00ebshtir\u00ebsi t\u00eb jen\u00eb t\u00eb vogla. Shembuj t\u00eb zbatimeve t\u00eb tilla aplikacionesh ekzistojn\u00eb tashm\u00eb. <\/p>\n<p>Nj\u00eb aspekt i r\u00ebnd\u00ebsish\u00ebm n\u00eb kontekstin e zbatimit t\u00eb multitenance n\u00eb \u00ab1C:Enterprise\u00bb \u00ebsht\u00eb se ne krijojm\u00eb nj\u00eb model hibrid, n\u00eb t\u00eb cilin nj\u00eb aplikacion mund t\u00eb funksionoj\u00eb si n\u00eb m\u00ebnyr\u00eb multitenance, ashtu edhe n\u00eb m\u00ebnyr\u00eb t\u00eb zakonshme. Kjo \u00ebsht\u00eb nj\u00eb detyr\u00eb mjaft e komplikuar dhe \u00ebsht\u00eb nj\u00eb tem\u00eb p\u00ebr nj\u00eb diskutim t\u00eb ve\u00e7ant\u00eb.<br \/>\n<br \/>Burimi: <a content=\"nofollow\" rel=\"nofollow\" href=\"https:\/\/habr.com\/ru\/company\/1c\/blog\/326654\/\">habr.com<\/a><\/p>","protected":false,"gt_translate_keys":[{"key":"rendered","format":"html"}]},"excerpt":{"rendered":"<p>\u041a \u0441\u043e\u0436\u0430\u043b\u0435\u043d\u0438\u044e, \u0443 \u044d\u0442\u043e\u0433\u043e \u0442\u0435\u0440\u043c\u0438\u043d\u0430 \u043d\u0435\u0442 \u0445\u043e\u0440\u043e\u0448\u0435\u0433\u043e \u0440\u0443\u0441\u0441\u043a\u043e\u044f\u0437\u044b\u0447\u043d\u043e\u0433\u043e \u0430\u043d\u0430\u043b\u043e\u0433\u0430. \u00ab\u0412\u0438\u043a\u0438\u043f\u0435\u0434\u0438\u044f\u00bb \u0434\u0430\u0435\u0442 \u043f\u0435\u0440\u0435\u0432\u043e\u0434 \u00ab\u043c\u0443\u043b\u044c\u0442\u0438\u0430\u0440\u0435\u043d\u0434\u043d\u043e\u0441\u0442\u044c, \u043c\u043d\u043e\u0436\u0435\u0441\u0442\u0432\u0435\u043d\u043d\u0430\u044f \u0430\u0440\u0435\u043d\u0434\u0430\u00bb. \u0418\u043d\u043e\u0433\u0434\u0430 \u044d\u0442\u043e \u043d\u0430\u0437\u044b\u0432\u0430\u044e\u0442 \u00ab\u043c\u043d\u043e\u0436\u0435\u0441\u0442\u0432\u0435\u043d\u043d\u044b\u043c \u0432\u043b\u0430\u0434\u0435\u043d\u0438\u0435\u043c\u00bb. \u042d\u0442\u0438 \u0442\u0435\u0440\u043c\u0438\u043d\u044b \u043c\u043e\u0433\u0443\u0442 \u043d\u0435\u0441\u043a\u043e\u043b\u044c\u043a\u043e \u043f\u0443\u0442\u0430\u0442\u044c, \u0442\u0430\u043a \u043a\u0430\u043a \u043f\u0440\u0435\u0434\u043c\u0435\u0442 \u043d\u0435 \u0441\u0432\u044f\u0437\u0430\u043d \u043f\u043e \u0441\u0443\u0442\u0438 \u043d\u0438 \u0441 \u0430\u0440\u0435\u043d\u0434\u043e\u0439, \u043d\u0438 \u0441 \u0432\u043b\u0430\u0434\u0435\u043d\u0438\u0435\u043c. \u042d\u0442\u043e \u0432\u043e\u043f\u0440\u043e\u0441 \u0438\u043c\u0435\u043d\u043d\u043e \u0430\u0440\u0445\u0438\u0442\u0435\u043a\u0442\u0443\u0440\u044b \u043f\u0440\u043e\u0433\u0440\u0430\u043c\u043c\u043d\u043e\u0433\u043e \u043e\u0431\u0435\u0441\u043f\u0435\u0447\u0435\u043d\u0438\u044f \u0438 \u043e\u0440\u0433\u0430\u043d\u0438\u0437\u0430\u0446\u0438\u0438 \u0435\u0433\u043e \u044d\u043a\u0441\u043f\u043b\u0443\u0430\u0442\u0430\u0446\u0438\u0438. \u041f\u0440\u0438\u0447\u0435\u043c \u043f\u043e\u0441\u043b\u0435\u0434\u043d\u0435\u0435 \u043d\u0435 \u043c\u0435\u043d\u0435\u0435 \u0432\u0430\u0436\u043d\u043e. \u041c\u044b \u043d\u0430\u0447\u0430\u043b\u0438 [&hellip;]<\/p>\n","protected":false,"gt_translate_keys":[{"key":"rendered","format":"html"}]},"author":1,"featured_media":55232,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[688],"tags":[],"class_list":["post-55231","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-administrirovanie"],"aioseo_notices":[],"aioseo_head":"\n\t\t<!-- All in One SEO 5.0.0.1 - aioseo.com -->\n\t<meta name=\"description\" content=\"\u041a \u0441\u043e\u0436\u0430\u043b\u0435\u043d\u0438\u044e, \u0443 \u044d\u0442\u043e\u0433\u043e \u0442\u0435\u0440\u043c\u0438\u043d\u0430 \u043d\u0435\u0442 \u0445\u043e\u0440\u043e\u0448\u0435\u0433\u043e \u0440\u0443\u0441\u0441\u043a\u043e\u044f\u0437\u044b\u0447\u043d\u043e\u0433\u043e \u0430\u043d\u0430\u043b\u043e\u0433\u0430.\" \/>\n\t<meta name=\"robots\" content=\"max-image-preview:large\" \/>\n\t<meta name=\"author\" content=\"Yuri Gagarin\"\/>\n\t<link rel=\"canonical\" href=\"https:\/\/prohoster.info\/sq\/blog\/administrirovanie\/pro-multitenancy\" \/>\n\t<meta name=\"generator\" content=\"All in One SEO (AIOSEO) 5.0.0.1\" \/>\n\t\t<meta property=\"og:locale\" content=\"sq_AL\" \/>\n\t\t<meta property=\"og:site_name\" content=\"ProHoster | \u041a\u0443\u043f\u0438\u0442\u044c \u043d\u0430\u0434\u0435\u0436\u043d\u044b\u0439 \u0445\u043e\u0441\u0442\u0438\u043d\u0433 \u0434\u043b\u044f \u0441\u0430\u0439\u0442\u043e\u0432 \u0441 \u0437\u0430\u0449\u0438\u0442\u043e\u0439 \u043e\u0442 DDoS, VPS VDS \u0441\u0435\u0440\u0432\u0435\u0440\u044b\" \/>\n\t\t<meta property=\"og:type\" content=\"article\" \/>\n\t\t<meta property=\"og:title\" content=\"\ud83e\udd47\u041f\u0440\u043e multitenancy | ProHoster\" \/>\n\t\t<meta property=\"og:description\" content=\"\u041a \u0441\u043e\u0436\u0430\u043b\u0435\u043d\u0438\u044e, \u0443 \u044d\u0442\u043e\u0433\u043e \u0442\u0435\u0440\u043c\u0438\u043d\u0430 \u043d\u0435\u0442 \u0445\u043e\u0440\u043e\u0448\u0435\u0433\u043e \u0440\u0443\u0441\u0441\u043a\u043e\u044f\u0437\u044b\u0447\u043d\u043e\u0433\u043e \u0430\u043d\u0430\u043b\u043e\u0433\u0430.\" \/>\n\t\t<meta property=\"og:url\" content=\"https:\/\/prohoster.info\/sq\/blog\/administrirovanie\/pro-multitenancy\" \/>\n\t\t<meta property=\"og:image\" content=\"https:\/\/prohoster.info\/wp-content\/uploads\/2021\/11\/logo-350.jpg\" \/>\n\t\t<meta property=\"og:image:secure_url\" content=\"https:\/\/prohoster.info\/wp-content\/uploads\/2021\/11\/logo-350.jpg\" \/>\n\t\t<meta property=\"og:image:width\" content=\"350\" \/>\n\t\t<meta property=\"og:image:height\" content=\"350\" \/>\n\t\t<meta property=\"article:published_time\" content=\"2020-01-15T21:00:00+00:00\" \/>\n\t\t<meta property=\"article:modified_time\" content=\"2020-02-18T11:03:19+00:00\" \/>\n\t\t<meta property=\"article:publisher\" content=\"https:\/\/www.facebook.com\/prohoster\" \/>\n\t\t<meta property=\"article:author\" content=\"https:\/\/www.facebook.com\/prohoster\" \/>\n\t\t<!-- All in One SEO -->\n\n","aioseo_head_json":{"title":"\ud83e\udd47P\u00ebr multitenancy | ProHoster","description":"Fatkeq\u00ebsisht, ky term nuk ka nj\u00eb ekuivalent t\u00eb mir\u00eb n\u00eb gjuh\u00ebn ruse.","canonical_url":"https:\/\/prohoster.info\/sq\/blog\/administrirovanie\/pro-multitenancy","robots":"max-image-preview:large","keywords":"","webmasterTools":{"miscellaneous":""},"schema":null,"og:locale":"sq_AL","og:site_name":"ProHoster | \u041a\u0443\u043f\u0438\u0442\u044c \u043d\u0430\u0434\u0435\u0436\u043d\u044b\u0439 \u0445\u043e\u0441\u0442\u0438\u043d\u0433 \u0434\u043b\u044f \u0441\u0430\u0439\u0442\u043e\u0432 \u0441 \u0437\u0430\u0449\u0438\u0442\u043e\u0439 \u043e\u0442 DDoS, VPS VDS \u0441\u0435\u0440\u0432\u0435\u0440\u044b","og:type":"article","og:title":"\ud83e\udd47\u041f\u0440\u043e multitenancy | ProHoster","og:description":"\u041a \u0441\u043e\u0436\u0430\u043b\u0435\u043d\u0438\u044e, \u0443 \u044d\u0442\u043e\u0433\u043e \u0442\u0435\u0440\u043c\u0438\u043d\u0430 \u043d\u0435\u0442 \u0445\u043e\u0440\u043e\u0448\u0435\u0433\u043e \u0440\u0443\u0441\u0441\u043a\u043e\u044f\u0437\u044b\u0447\u043d\u043e\u0433\u043e \u0430\u043d\u0430\u043b\u043e\u0433\u0430.","og:url":"https:\/\/prohoster.info\/sq\/blog\/administrirovanie\/pro-multitenancy","og:image":"https:\/\/prohoster.info\/wp-content\/uploads\/2021\/11\/logo-350.jpg","og:image:secure_url":"https:\/\/prohoster.info\/wp-content\/uploads\/2021\/11\/logo-350.jpg","og:image:width":350,"og:image:height":350,"article:published_time":"2020-01-15T21:00:00+00:00","article:modified_time":"2020-02-18T11:03:19+00:00","article:publisher":"https:\/\/www.facebook.com\/prohoster","article:author":"https:\/\/www.facebook.com\/prohoster"},"aioseo_meta_data":{"post_id":"55231","title":null,"description":null,"keywords":null,"keyphrases":null,"primary_term":null,"canonical_url":null,"og_title":null,"og_description":null,"og_object_type":"default","og_image_type":"default","og_image_url":null,"og_image_width":null,"og_image_height":null,"og_image_custom_url":null,"og_image_custom_fields":null,"og_video":null,"og_custom_url":null,"og_article_section":null,"og_article_tags":null,"twitter_use_og":false,"twitter_card":"default","twitter_image_type":"default","twitter_image_url":null,"twitter_image_custom_url":null,"twitter_image_custom_fields":null,"twitter_title":null,"twitter_description":null,"schema":{"blockGraphs":[],"customGraphs":[],"default":{"data":{"Article":[],"Course":[],"Dataset":[],"FAQPage":[],"Movie":[],"Person":[],"Product":[],"ProductReview":[],"Car":[],"Recipe":[],"Service":[],"SoftwareApplication":[],"WebPage":[]},"graphName":"","isEnabled":true},"graphs":[]},"schema_type":null,"schema_type_options":null,"pillar_content":false,"robots_default":true,"robots_noindex":false,"robots_noarchive":false,"robots_nosnippet":false,"robots_nofollow":false,"robots_noimageindex":false,"robots_noodp":false,"robots_notranslate":false,"robots_max_snippet":null,"robots_max_videopreview":null,"robots_max_imagepreview":"large","priority":null,"frequency":null,"local_seo":null,"seo_analyzer_scan_date":null,"breadcrumb_settings":null,"limit_modified_date":false,"reviewed_by":null,"ai":null,"created":"2021-02-28 19:47:39","updated":"2022-09-29 20:30:21","focus_keyword":null,"additional_keywords":null,"truseo_locale":null},"gt_translate_keys":[{"key":"link","format":"url"}],"_links":{"self":[{"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/posts\/55231","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/comments?post=55231"}],"version-history":[{"count":0,"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/posts\/55231\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/media\/55232"}],"wp:attachment":[{"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/media?parent=55231"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/categories?post=55231"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/tags?post=55231"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}