{"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\/cs\/blog\/administrirovanie\/pro-multitenancy","title":{"rendered":"O multitenanci","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"

Bohu\u017eel, tento term\u00edn nem\u00e1 dobr\u00fd \u010desk\u00fd ekvivalent. \"Wikipedia\" uv\u00e1d\u00ed p\u0159eklad<\/a><\/noindex> \"multi-tenantnost, v\u00edcen\u00e1sobn\u00fd pron\u00e1jem\". N\u011bkdy se tomu \u0159\u00edk\u00e1 \"v\u00edcero\u010dn\u00ed vlastnictv\u00ed\". Tyto term\u00edny mohou b\u00fdt pon\u011bkud matouc\u00ed, proto\u017ee se podstatn\u011b net\u00fdkaj\u00ed ani pron\u00e1jmu, ani vlastnictv\u00ed. Je to ot\u00e1zka architektury softwaru a organizace jeho provozu. A to posledn\u00ed je nem\u00e9n\u011b d\u016fle\u017eit\u00e9. <\/p>\n

Na\u0161e porozum\u011bn\u00ed multitenancy jsme za\u010dali formovat sou\u010dasn\u011b s t\u00edm, jak jsme za\u010dali navrhovat p\u0159\u00edstup k cloudov\u00e9mu (servisn\u00edmu) modelu pr\u00e1ce \"1C:Enterprise\". To bylo p\u0159ed n\u011bkolika lety. A od t\u00e9 doby se na\u0161e ch\u00e1p\u00e1n\u00ed neust\u00e1le roz\u0161i\u0159uje. Neust\u00e1le objevujeme nov\u00e9 a nov\u00e9 aspekty tohoto t\u00e9matu (v\u00fdhody, nev\u00fdhody, slo\u017eitosti, zvl\u00e1\u0161tnosti atd.). <\/p>\n

\"O
\n<\/a><\/noindex>
\nN\u011bkdy v\u00fdvoj\u00e1\u0159i ch\u00e1pou pod multitenancy zcela jednoduchou v\u011bc: \"aby data n\u011bkolika organizac\u00ed byla ulo\u017eena v jedn\u00e9 datab\u00e1zi, je t\u0159eba do v\u0161ech tabulek p\u0159idat sloupec s identifik\u00e1torem organizace a nastavit filtr podle n\u011bj\". My jsme samoz\u0159ejm\u011b tak\u00e9 za\u010dali na\u0161e zpracov\u00e1n\u00ed ot\u00e1zky z tohoto bodu. Ale dost rychle jsme pochopili, \u017ee to je jen jedna \"loukka\" (tak\u00e9, mimochodem, ne jednoduch\u00e1). A v\u016fbec je to \"cel\u00e1 zem\u011b\". <\/p>\n

Hlavn\u00ed my\u0161lenku multitenancy lze popsat p\u0159ibli\u017en\u011b takto. B\u011b\u017en\u00e1 aplikace je jako rodinn\u00fd d\u016fm, ur\u010den\u00fd pro bydlen\u00ed jedn\u00e9 rodiny, kter\u00e1 vyu\u017e\u00edv\u00e1 jeho infrastrukturu (st\u011bny, st\u0159echa, vodovod, topen\u00ed atd.). Naopak multitenancy aplikace je jako bytov\u00fd d\u016fm. V n\u011bm ka\u017ed\u00e1 rodina pou\u017e\u00edv\u00e1 stejnou infrastrukturu, ale samotn\u00e1 infrastruktura je realizov\u00e1na pro cel\u00fd d\u016fm jako celek. <\/p>\n

A je p\u0159\u00edstup multitenancy dobr\u00fd, nebo \u0161patn\u00fd? Na to lze naj\u00edt velmi r\u016fzn\u00e9 n\u00e1zory. Zd\u00e1 se, \u017ee neexistuje \"dobr\u00e9 nebo \u0161patn\u00e9\" v\u016fbec. Je t\u0159eba porovn\u00e1vat v\u00fdhody a nev\u00fdhody v kontextu konkr\u00e9tn\u00edch \u0159e\u0161en\u00fdch \u00fakol\u016f. Ale to je samostatn\u00e9 t\u00e9ma\u2026 <\/p>\n

V nejjednodu\u0161\u0161\u00edm ch\u00e1p\u00e1n\u00ed je c\u00edlem multitenancy sn\u00ed\u017eit n\u00e1klady na \u00fadr\u017ebu aplikace prost\u0159ednictv\u00edm \"sd\u00edlen\u00ed\" n\u00e1klad\u016f na infrastrukturu. Je to stejn\u00e9 hnut\u00ed, jako je sni\u017eov\u00e1n\u00ed n\u00e1klad\u016f na aplikaci pou\u017eit\u00edm s\u00e9riov\u00e9ho \u0159e\u0161en\u00ed (mo\u017en\u00e1 s \u00fapravou a p\u0159izp\u016fsoben\u00edm), a ne vytv\u00e1\u0159en\u00edm \"na m\u00edru\". Jen v jednom p\u0159\u00edpad\u011b se sd\u00edl\u00ed v\u00fdvoj, a v druh\u00e9m \u2013 provoz. <\/p>\n

A opakujeme, zde nen\u00ed p\u0159\u00edm\u00e1 vazba na zp\u016fsob prodeje. Architektura multitenancy m\u016f\u017ee velmi dob\u0159e fungovat i v korpor\u00e1tn\u00ed nebo vl\u00e1dn\u00ed IT infrastruktu\u0159e pro automatizaci velk\u00e9ho mno\u017estv\u00ed homogen\u00edch pobo\u010dek, podnik\u016f holdingu. <\/p>\n

Lze \u0159\u00edci, \u017ee multitenancy nen\u00ed jen ot\u00e1zkou organizace ukl\u00e1d\u00e1n\u00ed dat. Je to model pr\u00e1ce aplikace jako celku (v\u010detn\u011b podstatn\u00e9 \u010d\u00e1sti aspekt\u016f jej\u00ed architektury, modelu nasazen\u00ed a organizace \u00fadr\u017eby). <\/p>\n

Nejd\u016fle\u017eit\u011bj\u0161\u00ed a nejzaj\u00edmav\u011bj\u0161\u00ed na modelu multitenancy, jak se n\u00e1m zd\u00e1, je, \u017ee podstata aplikace se \"rozd\u011bluje\". \u010c\u00e1st funkcionality pracuje s konkr\u00e9tn\u00edmi oblastmi dat (byty) a \"nezaj\u00edm\u00e1 se\" o to, co se d\u011bje s n\u00e1jemn\u00edky v jin\u00fdch bytech. A \u010d\u00e1st vn\u00edm\u00e1 d\u016fm jako celek a pracuje okam\u017eit\u011b pro v\u0161echny n\u00e1jemn\u00edky. P\u0159itom posledn\u011b jmenovan\u00e1 nem\u016f\u017ee abstrahovat od toho, \u017ee p\u0159ece jen jde o jednotliv\u00e9 byty, a je t\u0159eba zajistit nezbytnou \u00farove\u0148 granularity a bezpe\u010dnosti. <\/p>\n

V \"1C:Podnik\u00e1n\u00ed\" je model multitenancy realizov\u00e1n na \u00farovni n\u011bkolika technologi\u00ed. Jsou to mechanismy platformy \"1C:Podnik\u00e1n\u00ed\", mechanismy \"1C:Technologie publikace \u0159e\u0161en\u00ed 1cFresh<\/a><\/noindex>\u201c a \u201e1C:Technologie v\u00fdvoje \u0159e\u0161en\u00ed 1cFresh<\/a><\/noindex>\", mechanismy BSP<\/a><\/noindex> (knihovny standardn\u00edch subsyst\u00e9m\u016f). <\/p>\n

Ka\u017ed\u00fd z t\u011bchto prvk\u016f p\u0159isp\u00edv\u00e1 k budov\u00e1n\u00ed celkov\u00e9 infrastruktury bytov\u00e9ho domu. Pro\u010d je to realizov\u00e1no v n\u011bkolika technologi\u00edch a ne pouze v jedn\u00e9, nap\u0159\u00edklad v platform\u011b? P\u0159edev\u0161\u00edm proto, \u017ee \u010d\u00e1st mechanism\u016f, podle na\u0161eho n\u00e1zoru, je zcela opr\u00e1vn\u011bn\u011b modifikovat p\u0159i konkr\u00e9tn\u00edm zp\u016fsobu nasazen\u00ed. Ale obecn\u011b je to slo\u017eit\u00e1 ot\u00e1zka a neust\u00e1le jsme postaveni p\u0159ed volbu \u2013 na kter\u00e9 \u00farovni je nejlep\u0161\u00ed realizovat ten \u010di onen aspekt multitenancy. <\/p>\n

Je z\u0159ejm\u00e9, \u017ee z\u00e1kladn\u00ed \u010d\u00e1st mechanism\u016f bylo t\u0159eba realizovat v platform\u011b. Nap\u0159\u00edklad samotn\u00e9 odd\u011blen\u00ed dat. To, \u010d\u00edm obvykle za\u010d\u00edn\u00e1 rozhovor o multitenancy. Ale nakonec model multitenancy \"proj\u00ed\u017ed\u011bl\" podstatnou \u010d\u00e1st mechanism\u016f platformy a vy\u017e\u00e1dal si jejich \u00fapravy, a v n\u011bkter\u00fdch p\u0159\u00edpadech i p\u0159epracov\u00e1n\u00ed. <\/p>\n

Na \u00farovni platformy jsme implementovali z\u00e1kladn\u00ed mechanismy. Ty umo\u017e\u0148uj\u00ed vytv\u00e1\u0159et aplikace, kter\u00e9 funguj\u00ed na modelu multitenancy. Aby v\u0161ak aplikace mohly \u201e\u017e\u00edt a fungovat\u201c v tomto modelu, je pot\u0159eba m\u00edt syst\u00e9m pro spr\u00e1vu jejich \u201e\u017eivotnosti\u201c. Za to jsou zodpov\u011bdn\u00e9 technologie 1cFresh a unifikovan\u00e1 vrstvy obchodn\u00ed logiky na \u00farovni BSP. Stejn\u011b jako v bytov\u00e9m dom\u011b infrastruktura zaji\u0161\u0165uje obyvatel\u016fm v\u0161e pot\u0159ebn\u00e9, tak i technologie 1cFresh zaji\u0161\u0165uj\u00ed aplikac\u00edm pot\u0159ebn\u00e9 zdroje pro fungov\u00e1n\u00ed v modelu multitenancy. Aby aplikace mohly komunikovat s touto infrastrukturou (bez podstatn\u00fdch \u00faprav), jsou do nich vlo\u017eeny odpov\u00eddaj\u00edc\u00ed \u201ez\u00e1str\u010dky\u201c ve form\u011b subsyst\u00e9m\u016f BSP. <\/p>\n

Z pohledu mechanism\u016f platformy je snadno patrn\u00e9, \u017ee s nar\u016fstaj\u00edc\u00edmi zku\u0161enostmi a rozvojem cloudov\u00e9 varianty pou\u017e\u00edv\u00e1n\u00ed \u201e1C:Enterprise\u201c roz\u0161i\u0159ujeme soubor mechanism\u016f, kter\u00e9 jsou zapojeny do t\u00e9to architektury. Uve\u010fme jeden p\u0159\u00edklad. V modelu multitenancy se podstatn\u011b m\u011bn\u00ed rozlo\u017een\u00ed rol\u00ed \u00fa\u010dastn\u00edk\u016f \u00fadr\u017eby aplikac\u00ed. Z\u00e1sadn\u011b se zvy\u0161uje \u00faloha (\u00farove\u0148 odpov\u011bdnosti) t\u011bch, kte\u0159\u00ed odpov\u00eddaj\u00ed za provoz aplikac\u00ed. Ti nyn\u00ed pot\u0159ebuj\u00ed m\u00edt siln\u011bj\u0161\u00ed n\u00e1stroje pro kontrolu aplikac\u00ed. Proto\u017ee u\u017eivatel\u00e9 aplikac\u00ed (obyvatel\u00e9) d\u016fv\u011b\u0159uj\u00ed p\u0159edev\u0161\u00edm poskytovateli, se kter\u00fdm spolupracuj\u00ed. K tomu jsme v verzi 8.3 implementovali nov\u00fd mechanismus profil\u016f bezpe\u010dnosti<\/a><\/noindex>. Tento mechanismus umo\u017e\u0148uje administr\u00e1tor\u016fm poskytovatele omezit volnost v\u00fdvoj\u00e1\u0159\u016f aplikac\u00ed na pot\u0159ebnou \u00farove\u0148 bezpe\u010dnosti \u2013 v podstat\u011b izolovat pr\u00e1ci aplikace pro ka\u017ed\u00e9ho obyvatele v ur\u010dit\u00fdch mez\u00edch \u201ep\u00edskovi\u0161t\u011b\u201c (sandbox). <\/p>\n

Architektura pro spr\u00e1vu aplikac\u00ed, kter\u00e9 funguj\u00ed v re\u017eimu multitenancy (tak, jak to realizuj\u00ed technologie 1cFresh a BSP), p\u0159edstavuje zaj\u00edmav\u00fd aspekt. Ve srovn\u00e1n\u00ed s tradi\u010dn\u00edmi modely nasazen\u00ed se zde v\u00fdrazn\u011b zvy\u0161uj\u00ed po\u017eadavky na automatizaci proces\u016f spr\u00e1vy. Takov\u00fdch proces\u016f je des\u00edtky: vytv\u00e1\u0159en\u00ed nov\u00fdch datov\u00fdch oblast\u00ed (\u201ebyt\u016f\u201c), aktualizace aplikac\u00ed, aktualizace normativn\u00edch informac\u00ed, z\u00e1lohov\u00e1n\u00ed atd. A samoz\u0159ejm\u011b se zvy\u0161uj\u00ed po\u017eadavky na \u00farove\u0148 spolehlivosti a dostupnosti. Nap\u0159\u00edklad pro zaji\u0161t\u011bn\u00ed spolehliv\u00e9 interakce aplikac\u00ed s komponenty syst\u00e9mu \u0159\u00edzen\u00ed jsme implementovali technologii asynchronn\u00edho volac\u00edho syst\u00e9mu s garantovan\u00fdm doru\u010den\u00edm. <\/p>\n

Velmi citliv\u00fdm momentem je zp\u016fsob sd\u00edlen\u00ed dat a proces\u016f. Na prvn\u00ed pohled se to m\u016f\u017ee zd\u00e1t jednoduch\u00e9 (pokud to n\u011bkomu p\u0159ipad\u00e1). Nejv\u011bt\u0161\u00ed obt\u00ed\u017e p\u0159edstavuje rovnov\u00e1ha mezi centralizac\u00ed dat a proces\u016f a decentralizac\u00ed. Na jedn\u00e9 stran\u011b umo\u017e\u0148uje centralizace sn\u00ed\u017eit n\u00e1klady (diskov\u00fd prostor, v\u00fdkon procesoru, \u00fasil\u00ed administr\u00e1tor\u016f\u2026). Na druh\u00e9 stran\u011b omezuje svobodu \u201eobyvatel\u201c. To je jeden z aspekt\u016f \u201erozd\u011blen\u00ed\u201c aplikace, kdy se v\u00fdvoj\u00e1\u0159 mus\u00ed zam\u00fd\u0161let nad aplikac\u00ed v \u00fazk\u00e9m smyslu (slou\u017e\u00edc\u00ed jedn\u00e9 \u201ebytov\u00e9 jednotce\u201c) a v \u0161ir\u0161\u00edm smyslu (slou\u017e\u00edc\u00ed v\u0161em \u201eobyvatel\u016fm\u201c). <\/p>\n

Jako p\u0159\u00edklad t\u00e9to \u201edilema\u201c lze uv\u00e9st normativn\u011b-informa\u010dn\u00ed \u00fadaje. Je jasn\u00e9, \u017ee existuje siln\u00e9 poku\u0161en\u00ed u\u010dinit je spole\u010dn\u00fdmi pro v\u0161echny \u201eobyvatele\u201c domu. To umo\u017e\u0148uje uchov\u00e1vat je v jednom exempl\u00e1\u0159i a okam\u017eit\u011b aktualizovat pro v\u0161echny. Ale n\u011bkdy se st\u00e1v\u00e1, \u017ee jednotliv\u00fd obyvatel pot\u0159ebuje specifick\u00e9 \u00fapravy. Jak paradoxn\u00ed to m\u016f\u017ee zn\u00edt, v praxi to nast\u00e1v\u00e1 i pro informace, kter\u00e9 jsou specifikov\u00e1ny regul\u00e1tory (vl\u00e1dn\u00edmi org\u00e1ny). Doch\u00e1z\u00ed k nelehk\u00e9mu probl\u00e9mu: sd\u00edlet nebo nesd\u00edlet? Je l\u00e1kav\u00e9 ud\u011blat spole\u010dn\u00e9 informace pro v\u0161echny a soukrom\u00e9 pro vy\u017eaduj\u00edc\u00ed. To v\u0161ak vede k p\u0159inejmen\u0161\u00edm slo\u017eit\u00e9 realizaci. Ale na tom pracujeme\u2026 <\/p>\n

Dal\u0161\u00edm p\u0159\u00edkladem je n\u00e1vrh implementace pravideln\u00fdch proces\u016f (prov\u00e1d\u011bn\u00fdch podle pl\u00e1nu, zahajovan\u00fdch \u0159\u00eddic\u00edm syst\u00e9mem atd.). Na jedn\u00e9 stran\u011b je mo\u017en\u00e9 je implementovat pro ka\u017edou oblast dat zvl\u00e1\u0161\u0165. Je to jednodu\u0161\u0161\u00ed a pohodln\u011bj\u0161\u00ed. Na druh\u00e9 stran\u011b v\u0161ak takov\u00e1 drobnost vytv\u00e1\u0159\u00ed velkou z\u00e1t\u011b\u017e na syst\u00e9m. Aby se z\u00e1t\u011b\u017e sn\u00ed\u017eila, je t\u0159eba implementovat sd\u00edlen\u00e9 procesy. Ty v\u0161ak vy\u017eaduj\u00ed pe\u010dliv\u011bj\u0161\u00ed zpracov\u00e1n\u00ed. <\/p>\n

Samoz\u0159ejm\u011b vyvst\u00e1v\u00e1 velmi v\u00fdznamn\u00e1 ot\u00e1zka. Jak mohou v\u00fdvoj\u00e1\u0159i aplikac\u00ed zajistit funk\u010dnost v re\u017eimu multitenancy? Co pro to mus\u00ed ud\u011blat? Ur\u010dit\u011b se sna\u017e\u00edme o to, aby t\u00edha technologick\u00fdch a infrastrukturn\u00edch ot\u00e1zek maxim\u00e1ln\u011b le\u017eela na bedrech dod\u00e1van\u00e9 technologie, zat\u00edmco v\u00fdvoj\u00e1\u0159 aplikace by se m\u011bl zab\u00fdvat pouze \u00fakoly obchodn\u00ed logiky. Ale jako u dal\u0161\u00edch d\u016fle\u017eit\u00fdch architektonick\u00fdch ot\u00e1zek, n\u011bjak\u00e9 pov\u011bdom\u00ed o pr\u00e1ci v modelu multitenancy mus\u00ed m\u00edt i v\u00fdvoj\u00e1\u0159i aplikac\u00ed a n\u011bjak\u00e9 \u00fasil\u00ed b\u011bhem v\u00fdvoje aplikac\u00ed bude zapot\u0159eb\u00ed. Pro\u010d? Proto\u017ee existuj\u00ed momenty, kter\u00e9 technologie nem\u016f\u017ee automaticky zajistit bez ohledu na s\u00e9mantiku dat. Nap\u0159\u00edklad definice hranic sd\u00edlen\u00ed informac\u00ed. Ale sna\u017e\u00edme se, aby tyto slo\u017eitosti byly co nejmen\u0161\u00ed. P\u0159\u00edklady implementace takov\u00fdch aplikac\u00ed u\u017e existuj\u00ed. <\/p>\n

D\u016fle\u017eit\u00fdm momentem v kontextu implementace multitenancy v \u201e1C:Enterprise\u201c je, \u017ee vytv\u00e1\u0159\u00edme hybridn\u00ed model, ve kter\u00e9m jedna aplikace m\u016f\u017ee fungovat jak v re\u017eimu multitenancy, tak i v norm\u00e1ln\u00edm re\u017eimu. To je velmi slo\u017eit\u00fd \u00fakol a t\u00e9ma pro samostatnou diskusi.
\n
Zdroj: habr.com<\/a><\/p>","protected":false,"gt_translate_keys":[{"key":"rendered","format":"html"}]},"excerpt":{"rendered":"

\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 […]<\/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\n\t\n\t\n\t\n\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\n","aioseo_head_json":{"title":"\ud83e\udd47O multitenancy | ProHoster","description":"Bohu\u017eel tento term\u00edn nem\u00e1 dobr\u00fd \u010desk\u00fd ekvivalent.","canonical_url":"https:\/\/prohoster.info\/cs\/blog\/administrirovanie\/pro-multitenancy","robots":"max-image-preview:large","keywords":"","webmasterTools":{"miscellaneous":""},"schema":null,"og:locale":"cs_CZ","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\/cs\/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\/cs\/wp-json\/wp\/v2\/posts\/55231","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/prohoster.info\/cs\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/prohoster.info\/cs\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/prohoster.info\/cs\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/prohoster.info\/cs\/wp-json\/wp\/v2\/comments?post=55231"}],"version-history":[{"count":0,"href":"https:\/\/prohoster.info\/cs\/wp-json\/wp\/v2\/posts\/55231\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/prohoster.info\/cs\/wp-json\/wp\/v2\/media\/55232"}],"wp:attachment":[{"href":"https:\/\/prohoster.info\/cs\/wp-json\/wp\/v2\/media?parent=55231"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/prohoster.info\/cs\/wp-json\/wp\/v2\/categories?post=55231"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/prohoster.info\/cs\/wp-json\/wp\/v2\/tags?post=55231"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}