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

Diem\u017e\u0113l \u0161im terminam nav laba latvie\u0161u valodas ekvivalenta. \"Vikip\u0113dija\" nor\u0101da tulkot<\/a><\/noindex> \"multientit\u0101te, vair\u0101ku nomu\". Da\u017ereiz to d\u0113v\u0113 ar\u012b par \"vair\u0101ku \u012bpa\u0161umu\". \u0160ie termini var nedaudz sajaukt, jo t\u0113ma b\u016bt\u012bb\u0101 nav saist\u012bta ne ar nomu, ne \u012bpa\u0161umu. Tas ir jaut\u0101jums par programmat\u016bras arhitekt\u016bru un t\u0101s ekspluat\u0101cijas organiz\u0113\u0161anu, kas nav maz\u0101k svar\u012bgi. <\/p>\n

M\u0113s s\u0101k\u0101m veidot savu izpratni par multientit\u0101ti taj\u0101 pa\u0161\u0101 laik\u0101, kad uzs\u0101k\u0101m projektu pieeju klientu iesp\u0113ju modelim \"1C: Uz\u0146\u0113mums\". Tas bija pirms vair\u0101kiem gadiem. Kop\u0161 t\u0101 laika m\u016bsu izpratne past\u0101v\u012bgi papla\u0161in\u0101s. M\u0113s past\u0101v\u012bgi atkl\u0101jam \u0161aj\u0101 t\u0113m\u0101 arvien jaunas un jaunas nianses (priek\u0161roc\u012bbas, tr\u016bkumi, sare\u017e\u0123\u012bjumi, iez\u012bmes utt.). <\/p>\n

\"Par
\n<\/a><\/noindex>
\nDa\u017ereiz izstr\u0101d\u0101t\u0101ji saprot multientit\u0101ti k\u0101 pavisam vienk\u0101r\u0161u jaut\u0101jumu: \"lai vair\u0101ku organiz\u0101ciju dati tiktu glab\u0101ti vien\u0101 datub\u0101z\u0113, ir j\u0101izveido vis\u0101s tabul\u0101s kolonna ar organiz\u0101cijas identifikatoru un j\u0101izveido filtrs p\u0113c t\u0101s\". M\u0113s ar\u012b, protams, s\u0101k\u0101m m\u016bsu izp\u0113ti par \u0161o jaut\u0101jumu no \u0161\u012b br\u012b\u017ea. Bet pietiekami \u0101tri saprat\u0101m, ka tas ir tikai viena da\u013ca (t\u0101pat, starp citu, nav vienk\u0101r\u0161a). Paties\u012bb\u0101 t\u0101 ir \"vesela valsts\". <\/p>\n

Galveno multientit\u0101tes ideju var aprakst\u012bt apm\u0113ram \u0161\u0101di. Parasts lietojums ir koted\u017ea, kas paredz\u0113ta vienai \u0123imenei, kas izmanto t\u0101s infrastrukt\u016bru (sienas, jumts, \u016bdensapg\u0101de, apkure utt.). Bet multientit\u0101tes lietojums ir daudzst\u0101vu m\u0101ja. Taj\u0101 katra \u0123imene izmanto vien\u0101du infrastrukt\u016bras komplektu, bet pati infrastrukt\u016bra ir izstr\u0101d\u0101ta visai m\u0101jai kopum\u0101. <\/p>\n

Vai pieeja multientit\u0101tei ir laba vai slikta? Tam var atrast \u013coti at\u0161\u0137ir\u012bgus viedok\u013cus. \u0160\u0137iet, ka nav visp\u0101r \"labi vai slikti\". J\u0101sal\u012bdzina ieguvumi un tr\u016bkumi konkr\u0113tu uzdevumu kontekst\u0101. Bet t\u0101 ir atsevi\u0161\u0137a t\u0113ma\u2026 <\/p>\n

Vienk\u0101r\u0161\u0101kaj\u0101 izpratn\u0113 multientit\u0101tes m\u0113r\u0137is ir samazin\u0101t izdevumus par lietojuma uztur\u0113\u0161anu, soci\u0101li daloties ar infrastrukt\u016bras uztur\u0113\u0161anas izdevumiem. Tas ir t\u0101ds pats solis k\u0101 lietojuma izmaksu samazin\u0101\u0161ana, izmantojot standarta risin\u0101jumu (iesp\u0113jams, ar iestat\u012bjumiem un piel\u0101gojumiem), nevis rakstot \"p\u0113c pas\u016bt\u012bjuma\". Tikai vien\u0101 gad\u012bjum\u0101 tiek kop\u012bgi izstr\u0101d\u0101ts, bet otr\u0101 - ekspluat\u0101cija. <\/p>\n

At the same time, we reiterate that there is no direct connection to the sales method here. The multitenancy architecture can also be applied in corporate or departmental IT infrastructures to automate a large number of similar branches and holding companies. <\/p>\n

It can be said that multitenancy is not just a matter of data storage organization. It is a model for the operation of the application as a whole (including a significant part of its architecture aspects, deployment model, and service organization). <\/p>\n

The most complex and interesting aspect of the multitenancy model, as we see it, is that the essence of the application is 'split'. Part of the functionality works with specific data domains (apartments) and 'does not care' about the tenants in other apartments. Meanwhile, another part perceives the house as a whole and operates for all tenants. However, the latter cannot abstract from the fact that these are indeed separate apartments, and necessary levels of granularity and security must be ensured. <\/p>\n

In '1C:Enterprise', the multitenancy model is implemented at several technology levels. These are mechanisms of the '1C:Enterprise' platform, the mechanisms of '1C:Solution Publishing Technology 1cFresh<\/a><\/noindex>\" un \"1C:Solution Development Technology 1cFresh<\/a><\/noindex>', mechanisms BSP<\/a><\/noindex> (standard subsystem libraries). <\/p>\n

Each of these elements contributes to the construction of the common infrastructure of the apartment building. Why is this implemented in several technologies instead of just one, for example, the platform? Primarily because we believe that some mechanisms are reasonable to modify based on specific deployment options. But in general, this is a complex question, and we constantly face the choice of at what level it is better to implement a particular aspect of multitenancy. <\/p>\n

It is clear that the basic part of the mechanisms needed to be implemented in the platform. For example, the very separation of data. This is usually where the conversation about multitenancy begins. However, in the end, the multitenancy model 'traveled through' a significant part of the platform's mechanisms and required their refinement, and in some cases, even rethinking. <\/p>\n

Platformas l\u012bmen\u012b m\u0113s esam ieviesu\u0161i tie\u0161i pamata meh\u0101nismus. Tie \u013cauj izveidot lietotnes, kas darbojas multitenancy model\u012b. Tom\u0113r, lai lietotnes \u201edz\u012bvotu un darbotos\u201d \u0161\u0101d\u0101 model\u012b, ir nepiecie\u0161ama sist\u0113ma, kas p\u0101rvalda to \u201edz\u012bves ciklu\u201d. Par to r\u016bp\u0113jas tehnolo\u0123ijas 1cFresh un standartiz\u0113ta biznesa lo\u0123ikas sl\u0101\u0146a BSP l\u012bmen\u012b. T\u0101pat k\u0101 dz\u012bvok\u013cu m\u0101j\u0101 infrastrukt\u016bra nodro\u0161ina iedz\u012bvot\u0101jus visam nepiecie\u0161amajam, tehnolo\u0123ijas 1cFresh nodro\u0161ina visam nepiecie\u0161amajam lietotnes, kas darbojas multitenancy model\u012b. Un, lai lietotnes var\u0113tu mijiedarboties ar \u0161o infrastrukt\u016bru (bez b\u016btisk\u0101m izmai\u0146\u0101m), taj\u0101s tiek ieb\u016bv\u0113ti atbilsto\u0161i \u201esavienojumi\u201d BSP apak\u0161sist\u0113mu veid\u0101. <\/p>\n

No platformas meh\u0101nismu skata viedok\u013ca ir viegli paman\u012bt, ka, att\u012bstoties un g\u016bstot pieredzi m\u0101ko\u0146varianta izmanto\u0161an\u0101 \u201e1C: Uz\u0146\u0113mums\u201d, m\u0113s papla\u0161in\u0101m meh\u0101nismu kopumu, kas iesaist\u012bts \u0161aj\u0101 arhitekt\u016br\u0101. Apskat\u012bsim vienu piem\u0113ru. Multitenancy model\u012b b\u016btiski main\u0101s lomu sadal\u012bjums lietot\u0146u apkalpes dal\u012bbniekiem. Iev\u0113rojami palielin\u0101s to lomu (atbild\u012bbas l\u012bmenis), kas atbild par lietot\u0146u ekspluat\u0101ciju. Vi\u0146iem ir nepiecie\u0161ams r\u012bkoties ar jaud\u012bg\u0101kiem instrumentiem lietot\u0146u uzraudz\u012bbai. Jo lietot\u0146u lietot\u0101ji (iedz\u012bvot\u0101ji) vispirms uzticas pakalpojumu sniedz\u0113jam, ar kuru vi\u0146i str\u0101d\u0101. T\u0101d\u0113\u013c m\u0113s versij\u0101 8.3 ievie\u0161am jauno dro\u0161\u012bbas profilu meh\u0101nismu<\/a><\/noindex>. \u0160is meh\u0101nisms \u013cauj pakalpojumu sniedz\u0113ju administratoriem ierobe\u017eot lietot\u0146u izstr\u0101d\u0101t\u0101ju br\u012bv\u012bbu nepiecie\u0161amaj\u0101 dro\u0161\u012bbas l\u012bmen\u012b \u2013 b\u016bt\u012bb\u0101 izol\u0113t lietotnes darbu katram iedz\u012bvot\u0101jam noteikt\u0101s \u201esmil\u0161u kastes\u201d (sandbox) robe\u017e\u0101s. <\/p>\n

Arhitekt\u016bra, kas nodro\u0161ina lietojumprogrammu p\u0101rvald\u012bbu multitenancy re\u017e\u012bm\u0101 (k\u0101 to \u012bsteno 1cFresh un BSP tehnolo\u0123ij\u0101s), ir ne maz\u0101k interesanta. \u0160aj\u0101 gad\u012bjum\u0101, sal\u012bdzinot ar parasto izvieto\u0161anas modeli, par\u0101d\u0101s daudz augst\u0101kas automatiz\u0101cijas pras\u012bbas p\u0101rvald\u012bbas procesos. \u0160\u0101du procesu ir desmitiem: jaunu datu jomu (\u00abdz\u012bvok\u013cu\u00bb) izveide, lietojumprogrammu atjaunin\u0101\u0161ana, normat\u012bv\u0101s inform\u0101cijas atjaunin\u0101\u0161ana, dubl\u0113\u0161ana utt. Un, protams, pieaug pras\u012bbas p\u0113c uzticam\u012bbas un pieejam\u012bbas. Piem\u0113ram, lai nodro\u0161in\u0101tu uzticamu lietojumprogrammu savienojam\u012bbu ar vad\u012bbas sist\u0113mas komponentiem, m\u0113s ievie\u0161am tehnolo\u0123iju asinkron\u0101s zvanu sist\u0113mas ar garant\u0113tu pieg\u0101di. <\/p>\n

\u013boti smalks mirklis ir datu un procesu publisko\u0161anas veids. Tas no pirm\u0101 acu uzmetiena var \u0161\u0137ist vienk\u0101r\u0161i (ja k\u0101dam t\u0101 \u0161\u0137iet). Visliel\u0101ko sare\u017e\u0123\u012bt\u012bbu rada l\u012bdzsvara uztur\u0113\u0161ana starp datu un procesu centraliz\u0101ciju un decentraliz\u0101ciju. No vienas puses, centraliz\u0101cija \u013cauj samazin\u0101t izmaksas (disku vietu, procesora resursus, administratoru piep\u016bli\u2026). No otras puses, t\u0101 ierobe\u017eo \u00abiedz\u012bvot\u0101ju\u00bb br\u012bv\u012bbu. Tas ir tie\u0161i viens no \u00abdivi\u0161\u0137a\u00bb programmat\u016bras aspektiem, kad izstr\u0101d\u0101t\u0101jam j\u0101dom\u0101 vienlaikus par lietojumprogrammu \u0161aur\u0101 noz\u012bm\u0113 (apkalpojot vienu \u00abdz\u012bvokli\u00bb) un pla\u0161\u0101 noz\u012bm\u0113 (apkalpojot visus \u00abiedz\u012bvot\u0101jus\u00bb). <\/p>\n

K\u0101 \u0161\u0101das \u00abdilemmes\u00bb piem\u0113ru var min\u0113t normat\u012bvo inform\u0101ciju. Protams, past\u0101v liela v\u0113lme padar\u012bt to kop\u012bgu visiem \u00abiedz\u012bvot\u0101jiem\u00bb m\u0101j\u0101. Tas \u013cauj glab\u0101t to vien\u0101 eksempl\u0101r\u0101 un atjaunin\u0101t uzreiz visiem. Bet da\u017ereiz k\u0101dam iedz\u012bvot\u0101jam ir nepiecie\u0161amas specifiskas izmai\u0146as. K\u0101 smiekl\u012bgi, tas patie\u0161\u0101m notiek praks\u0113, pat attiec\u012bb\u0101 uz inform\u0101ciju, kas ir noteikta regul\u0113t\u0101jiem (valsts iest\u0101d\u0113m). T\u0101d\u0113j\u0101di rodas gr\u016bti atbildams jaut\u0101jums: publiskot vai nepublikot? Protams, k\u0101rdin\u0101jums ir izveidot kop\u012bgu inform\u0101ciju visiem un individu\u0101lu tiem, kas to v\u0113las. Bet tas jau noved pie pavisam sare\u017e\u0123\u012btas \u012bsteno\u0161anas. Bet m\u0113s pie t\u0101 str\u0101d\u0101jam... <\/p>\n

V\u0113l viens piem\u0113rs ir regul\u0101ru procesu projekt\u0113\u0161ana un \u012bsteno\u0161ana (kas tiek veikti saska\u0146\u0101 ar grafiku, ierosin\u0101ti vad\u012bbas sist\u0113mas utt.). No vienas puses, tos var ieviest katrai datu jomai atsevi\u0161\u0137i. Tas ir vienk\u0101r\u0161\u0101k un \u0113rt\u0101k. Bet, no otras puses, \u0161\u0101da s\u012bka sadal\u012b\u0161ana rada lielu slodzi uz sist\u0113mu. Lai samazin\u0101tu slodzi, ir j\u0101\u012bsteno centraliz\u0113ti procesi. Bet tie prasa r\u016bp\u012bg\u0101ku izstr\u0101di. <\/p>\n

Protams, rodas \u013coti b\u016btisks jaut\u0101jums. K\u0101 izstr\u0101d\u0101t\u0101jiem nodro\u0161in\u0101t darbu multitenancy re\u017e\u012bm\u0101? Ko vi\u0146iem vajadz\u0113tu dar\u012bt? Protams, m\u0113s cen\u0161amies, lai tehnolo\u0123isko un infrastrukt\u016bras jaut\u0101jumu smagums maksim\u0101li gulstas uz pieg\u0101d\u0101t\u0101s tehnolo\u0123ijas pleciem, bet lietojumprogrammas izstr\u0101d\u0101t\u0101jam vajadz\u0113tu dom\u0101t tikai par biznesa lo\u0123ikas uzdevumiem. Tom\u0113r, t\u0101pat k\u0101 ar citiem svar\u012bgiem arhitekt\u016bras jaut\u0101jumiem, izstr\u0101d\u0101t\u0101jiem j\u0101b\u016bt kaut k\u0101dai izpratnei par darbu multitenancy model\u012b un noteikti b\u016bs nepiecie\u0161amas zin\u0101mas p\u016bles lietojumprogrammu izstr\u0101d\u0113. K\u0101ds iemesls? T\u0101p\u0113c, ka ir momenti, kurus tehnolo\u0123ija nevar autom\u0101tiski nodro\u0161in\u0101t, \u0146emot v\u0113r\u0101 datu semantiku. Piem\u0113ram, t\u0101 pati inform\u0101cijas centraliz\u0101cijas robe\u017eu noteik\u0161ana. Bet m\u0113s cen\u0161amies, lai \u0161\u012bs gr\u016bt\u012bbas b\u016btu minim\u0101las. \u0160\u0101du lietojumprogrammu \u012bsteno\u0161anas piem\u0113ri jau ir. <\/p>\n

Svar\u012bgs moments attiec\u012bb\u0101 uz multitenancy \u012bsteno\u0161anu \u00ab1C:Uz\u0146\u0113mum\u0101\u00bb ir tas, ka m\u0113s izveidojam hibr\u012bda modeli, kur\u0101 viena lietojumprogramma var darboties gan multitenancy re\u017e\u012bm\u0101, gan parastaj\u0101 re\u017e\u012bm\u0101. Tas ir diezgan sare\u017e\u0123\u012bts uzdevums un ir atsevi\u0161\u0137as diskusijas priek\u0161mets.
\n
Avots: 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\udd47Par multitenancy | ProHoster","description":"Diem\u017e\u0113l \u0161im terminam nav labas latvie\u0161u valodas analo\u0123ijas.","canonical_url":"https:\/\/prohoster.info\/lv\/blog\/administrirovanie\/pro-multitenancy","robots":"max-image-preview:large","keywords":"","webmasterTools":{"miscellaneous":""},"schema":null,"og:locale":"lv_LV","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\/lv\/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\/lv\/wp-json\/wp\/v2\/posts\/55231","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/prohoster.info\/lv\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/prohoster.info\/lv\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/prohoster.info\/lv\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/prohoster.info\/lv\/wp-json\/wp\/v2\/comments?post=55231"}],"version-history":[{"count":0,"href":"https:\/\/prohoster.info\/lv\/wp-json\/wp\/v2\/posts\/55231\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/prohoster.info\/lv\/wp-json\/wp\/v2\/media\/55232"}],"wp:attachment":[{"href":"https:\/\/prohoster.info\/lv\/wp-json\/wp\/v2\/media?parent=55231"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/prohoster.info\/lv\/wp-json\/wp\/v2\/categories?post=55231"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/prohoster.info\/lv\/wp-json\/wp\/v2\/tags?post=55231"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}