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

Din p\u0103cate, acest termen nu are un echivalent bun \u00een limba rom\u00e2n\u0103. Wikipedia ofer\u0103 traducere<\/a><\/noindex> \u201emultiarend\u0103, \u00eenchiriere multipl\u0103\u201d. Uneori, acest lucru este numit \u201eproprietate multipl\u0103\u201d. Aceste termeni pot fi pu\u021bin confuzi, deoarece subiectul nu este \u00een esen\u021b\u0103 legat de \u00eenchiriere sau de proprietate. Este o chestiune de arhitectur\u0103 software \u0219i de organizarea exploat\u0103rii acestuia, ceea ce este la fel de important. <\/p>\n

Am \u00eenceput s\u0103 ne form\u0103m \u00een\u021belegerea multitenancy \u00een momentul \u00een care am \u00eenceput s\u0103 proiect\u0103m o abordare pentru modelul de lucru bazat pe cloud (serviciu) \u201e1C:Enterprise\u201d. Acum c\u00e2\u021biva ani. \u0218i de atunci, \u00een\u021belegerea noastr\u0103 s-a extins constant. Descoperim continuu noi \u0219i noi aspecte ale acestui subiect (avantaje, dezavantaje, dificult\u0103\u021bi, particularit\u0103\u021bi etc.). <\/p>\n

\"Despre
\n<\/a><\/noindex>
\nUneori, dezvoltatorii \u00een\u021beleg prin multitenancy un concept destul de simplu: \u201epentru ca datele mai multor organiza\u021bii s\u0103 fie stocate \u00eentr-o singur\u0103 baz\u0103 de date, trebuie s\u0103 ad\u0103ug\u0103m \u00een toate tabelele o coloan\u0103 cu identificatorul organiza\u021biei \u0219i s\u0103 aplic\u0103m un filtru pe baza acesteia\u201d. Desigur, \u0219i noi am \u00eenceput studiul acestei probleme de la acest punct. \u00eens\u0103 ne-am dat seama destul de repede c\u0103 acesta este doar un aspect (de asemenea, nu chiar u\u0219or). \u00cen realitate, este un \u201e \u00eentreg teritoriu\u201d. <\/p>\n

Ideea principal\u0103 a multitenancy poate fi descris\u0103 astfel. O aplica\u021bie obi\u0219nuit\u0103 este o cas\u0103 de vacan\u021b\u0103, destinat\u0103 locuirii unei singure familii, care utilizeaz\u0103 infrastructura sa (pere\u021bi, acoperi\u0219, alimentare cu ap\u0103, \u00eenc\u0103lzire etc.). Pe c\u00e2nd o aplica\u021bie multitenancy este un bloc de apartamente. \u00cen el, fiecare familie folose\u0219te aceea\u0219i infrastructur\u0103, dar infrastructura este realizat\u0103 pentru \u00eentregul bloc \u00een ansamblul s\u0103u. <\/p>\n

Este abordarea multitenancy bun\u0103 sau proast\u0103? Se pot g\u0103si p\u0103reri foarte diferite \u00een privin\u021ba asta. Se pare c\u0103 nu exist\u0103 un \u201ebun sau r\u0103u\u201d \u00een general. Trebuie comparate avantajele \u0219i dezavantajele \u00een contextul problemelor specifice rezolvate. Dar aceasta este o tem\u0103 separat\u0103... <\/p>\n

\u00cen cea mai simpl\u0103 \u00een\u021belegere, scopul multitenancy este de a reduce costurile de \u00eentre\u021binere a aplica\u021biei prin \u201esocializarea\u201d cheltuielilor pe infrastructur\u0103. Este o mi\u0219care similar\u0103 cu reducerea costului aplica\u021biei prin utilizarea unei solu\u021bii \u00een serie (poate cu personalizare \u0219i ajust\u0103ri) \u00een loc de dezvoltare \u201ela comand\u0103\u201d. Doar c\u0103, \u00een cazul de fa\u021b\u0103, se socializa dezvoltarea, iar \u00een cel\u0103lalt, exploatarea. <\/p>\n

A\u0219adar, repet\u0103m, nu este o leg\u0103tur\u0103 direct\u0103 cu modul de v\u00e2nzare. Arhitectura multitenancy poate fi aplicat\u0103 \u0219i \u00een infrastructura IT corporativ\u0103 sau institu\u021bional\u0103 pentru automatizarea unui num\u0103r mare de filiale sau \u00eentreprinderi din cadrul unui holding. <\/p>\n

Se poate spune c\u0103 multitenancy nu este doar o problem\u0103 de organizare a stoc\u0103rii datelor. Este un model de lucru al aplica\u021biei \u00een \u00eentregul s\u0103u (inclusiv o parte semnificativ\u0103 a aspectelor arhitecturii sale, modelul de desf\u0103\u0219urare \u0219i organizarea \u00eentre\u021binerii). <\/p>\n

Ceea ce este cel mai complex \u0219i interesant \u00een modelul multitenancy, dup\u0103 cum ni se pare, este c\u0103 esen\u021ba aplica\u021biei se \u201edivizeaz\u0103\u201d. O parte din func\u021bionalitate lucreaz\u0103 cu anumite domenii de date (apartamente) \u0219i \u201enu este interesat\u0103\u201d de faptul c\u0103 exist\u0103 locatari \u00een alte apartamente. O alt\u0103 parte percepe \u00eentregul imobil \u0219i lucreaz\u0103 simultan pentru to\u021bi locatarii. Totu\u0219i, aceasta din urm\u0103 nu poate s\u0103 ignore faptul c\u0103, totu\u0219i, sunt apartamente separate \u0219i trebuie s\u0103 asigure un nivel necesar de granularitate \u0219i siguran\u021b\u0103. <\/p>\n

\u00cen \u201e1C:Enterprise\u201d, modelul multitenancy este implementat la nivelul mai multor tehnologii. Acestea sunt mecanismele platformei \u201e1C:Enterprise\u201d, mecanismele \u201e1C:Tehnologia de publicare a solu\u021biilor 1cFresh<\/a><\/noindex>\u201d \u0219i \u201e1C:Tehnologia de dezvoltare a solu\u021biilor 1cFresh<\/a><\/noindex>\u201d, mecanismele BSP<\/a><\/noindex> (bibliotecile sistemelor standard). <\/p>\n

Fiecare dintre aceste elemente contribuie la construirea infrastructurii generale a unei cl\u0103diri cu apartamente. De ce este realizat\u0103 \u00een mai multe tehnologii \u0219i nu \u00eentr-una singur\u0103, de exemplu, \u00een platform\u0103? \u00cen primul r\u00e2nd, pentru c\u0103 o parte din mecanisme, dup\u0103 p\u0103rerea noastr\u0103, poate fi modificat\u0103 cu u\u0219urin\u021b\u0103 \u00een func\u021bie de varianta specific\u0103 de desf\u0103\u0219urare. Dar, \u00een linii mari, acesta este o \u00eentrebare complex\u0103, iar noi ne confrunt\u0103m constant cu alegerea \u2013 la ce nivel este mai bine s\u0103 implement\u0103m un anumit aspect al multitenancy. <\/p>\n

Este evident c\u0103 partea de baz\u0103 a mecanismelor trebuia implementat\u0103 \u00een platform\u0103. De exemplu, efectiv \u00eemp\u0103r\u021birea datelor. Acesta este subiectul de \u00eenceput al discu\u021biei despre multitenancy. Dar, \u00een cele din urm\u0103, modelul multitenancy a \u201eacoperit\u201d o parte semnificativ\u0103 din mecanismele platformei \u0219i a necesitat revizuirea lor, iar \u00een unele cazuri, chiar \u0219i o redefinire. <\/p>\n

La nivel de platform\u0103, am implementat exact mecanismele de baz\u0103. Acestea permit crearea de aplica\u021bii care func\u021bioneaz\u0103 \u00een modelul multitenancy. Dar pentru ca aplica\u021biile s\u0103 \u201etr\u0103iasc\u0103 \u0219i s\u0103 func\u021bioneze\u201d \u00een acest model, este nevoie de un sistem de gestionare a \u201evie\u021bii\u201d lor. Pentru aceasta, sunt responsabile tehnologiile 1cFresh \u0219i stratul unificat de logic\u0103 de afaceri la nivelul BSC. A\u0219a cum infrastructura asigur\u0103 necesit\u0103\u021bile locatarilor dintr-un bloc cu apartamente, tehnologiile 1cFresh ofer\u0103 toate cele necesare aplica\u021biilor care func\u021bioneaz\u0103 \u00een modelul multitenancy. Iar pentru ca aplica\u021biile s\u0103 poat\u0103 interac\u021biona cu aceast\u0103 infrastructur\u0103 (f\u0103r\u0103 modific\u0103ri semnificative), sunt inserate \u201eprize\u201d corespunz\u0103toare sub form\u0103 de subsisteme BSC. <\/p>\n

Din perspectiva mecanismelor platformei, se observ\u0103 cu u\u0219urin\u021b\u0103 c\u0103, pe m\u0103sur\u0103 ce acumul\u0103m experien\u021b\u0103 \u0219i dezvolt\u0103m varianta bazat\u0103 pe cloud a \u201e1C:Enterprise\u201d, extindem compunerea mecanismelor implicate \u00een aceast\u0103 arhitectur\u0103. Iat\u0103 un exemplu. \u00cen modelul multitenancy, rolurile participan\u021bilor la \u00eentre\u021binerea aplica\u021biilor se schimb\u0103 semnificativ. Cre\u0219te considerabil rolul (nivelul de responsabilitate) celor care r\u0103spund de exploatarea aplica\u021biilor. Ace\u0219tia au nevoie de instrumente de control mai puternice. Pentru c\u0103 utilizatorii aplica\u021biilor (locatarii) au \u00eencredere mai \u00eent\u00e2i \u00een furnizorul cu care colaboreaz\u0103. De aceea, \u00een versiunea 8.3 am implementat o nou\u0103 mecanism de profiluri de securitate<\/a><\/noindex>. Acest mecanism permite administratorilor furnizorului s\u0103 limiteze libertatea dezvoltatorilor de aplica\u021bii la un nivel de securitate necesar \u2013 \u00een esen\u021b\u0103, s\u0103 izoleze func\u021bionarea aplica\u021biei pentru fiecare locatar \u00een anumite limite ale \u201esandbox-ului\u201d. <\/p>\n

Arhitectura pentru gestionarea aplica\u021biilor care func\u021bioneaz\u0103 \u00een mod multitenant (a\u0219a cum este implementat \u00een tehnologiile 1cFresh \u0219i BSP) este deosebit de interesant\u0103. Comparativ cu modelul obi\u0219nuit de desf\u0103\u0219urare, cerin\u021bele pentru automatizarea proceselor de gestionare cresc semnificativ. Aceste procese sunt zeci: crearea de noi domenii de date (\u201eapartamente\u201d), actualizarea aplica\u021biilor, actualizarea informa\u021biilor normative, backup de date etc. \u0218i, desigur, cerin\u021bele pentru nivelul de fiabilitate \u0219i disponibilitate cresc. De exemplu, pentru a asigura interac\u021biunea fiabil\u0103 a aplica\u021biilor cu componentele sistemului de gestionare, am implementat o tehnologie de sistem de apeluri asincrone cu livrare garantat\u0103. <\/p>\n

Un aspect foarte delicat este modul de partajare a datelor \u0219i proceselor. La prima vedere, pare simplu (dac\u0103 asta crede cineva). Cea mai mare dificultate const\u0103 \u00een echilibrul \u00eentre centralizarea datelor \u0219i proceselor \u0219i descentralizare. Pe de o parte, centralizarea permite reducerea cheltuielilor (spa\u021biu pe disc, resurse ale procesorului, eforturile administratorilor\u2026). Pe de alt\u0103 parte, limiteaz\u0103 libertatea \u201elocatarilor\u201d. Aceasta este exact una dintre problemele \u201ediviz\u0103rii\u201d aplica\u021biei, c\u00e2nd dezvoltatorul trebuie s\u0103 se g\u00e2ndeasc\u0103 simultan la aplica\u021bia \u00een sens restr\u00e2ns (care deserveste o \u201eapartament\u201d) \u0219i \u00een sens larg (care deserveste to\u021bi \u201elocatarii\u201d deodat\u0103). <\/p>\n

Un exemplu al unei astfel de \u201edileme\u201d este informa\u021bia normativ\u0103. Este evident c\u0103 tenta\u021bia de a o face comun\u0103 pentru to\u021bi \u201elocatarii\u201d cl\u0103dirii este mare. Aceasta permite p\u0103strarea ei \u00eentr-un singur exemplar \u0219i actualizarea imediat\u0103 pentru to\u021bi. Dar se \u00eent\u00e2mpl\u0103 adesea ca unora dintre locatari s\u0103 le fie necesare modific\u0103ri specifice. Ciudat, dar \u00een practic\u0103, acest lucru apare chiar \u0219i pentru informa\u021biile specificate de reglementatori (organe guvernamentale). Rezult\u0103 o \u00eentrebare complicat\u0103: s\u0103 partaj\u0103m sau nu? E tentant, desigur, s\u0103 facem informa\u021bii comune pentru to\u021bi \u0219i private pentru doritori. Dar asta deja duce la o realizare mult mai complex\u0103. Dar lucr\u0103m la asta\u2026 <\/p>\n

Un alt exemplu este proiectarea implement\u0103rii proceselor regulate (executate conform unui program, ini\u021biate de sistemul de gestionare etc.). Pe de o parte, acestea pot fi implementate pentru fiecare domeniu de date separat. Este mai simplu \u0219i mai convenabil. Dar, pe de alt\u0103 parte, o granularitate at\u00e2t de mic\u0103 creeaz\u0103 o sarcin\u0103 mai mare asupra sistemului. Pentru a reduce aceast\u0103 sarcin\u0103, trebuie implementate procese consolidate. \u00cens\u0103 acestea necesit\u0103 o dezvoltare mai atent\u0103. <\/p>\n

Desigur, se ridic\u0103 o \u00eentrebare foarte relevant\u0103. Cum pot dezvoltatorii de aplica\u021bii s\u0103 asigure func\u021bionarea \u00een modul multitenancy? Ce trebuie s\u0103 fac\u0103 pentru aceasta? Desigur, ne str\u0103duim ca povara \u00eentreb\u0103rilor tehnologice \u0219i infrastructurale s\u0103 cad\u0103 c\u00e2t mai mult pe umerii tehnologiei furnizate, iar dezvoltatorul aplica\u021biei s\u0103 se g\u00e2ndeasc\u0103 doar la logica de afaceri. Dar, precum \u00een alte \u00eentreb\u0103ri arhitecturale importante, dezvoltatorii de aplica\u021bii trebuie s\u0103 aib\u0103 o oarecare \u00een\u021belegere a func\u021bion\u0103rii \u00een modelul multitenancy, iar unele eforturi vor fi necesare \u00een dezvoltarea aplica\u021biilor. De ce? Pentru c\u0103 exist\u0103 aspecte pe care tehnologia nu le poate asigura automat, f\u0103r\u0103 a lua \u00een considerare semantica datelor. De exemplu, aceea\u0219i defini\u021bie a limitelor consolid\u0103rii informa\u021biei. Dar ne str\u0103duim ca aceste dificult\u0103\u021bi s\u0103 fie minime. Exemple de implementare a unor astfel de aplica\u021bii exist\u0103 deja. <\/p>\n

Un aspect important \u00een contextul implement\u0103rii multitenancy \u00een \u00ab1C:Enterprise\u00bb este faptul c\u0103 cre\u0103m un model hibrid, \u00een care o aplica\u021bie poate func\u021biona at\u00e2t \u00een modul multitenancy, c\u00e2t \u0219i \u00een modul obi\u0219nuit. Aceasta este o sarcin\u0103 destul de complicat\u0103 \u0219i un subiect de discu\u021bie separat\u0103.
\n
Sursa: 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\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\udd47Despre multitenancy | ProHoster","description":"Din p\u0103cate, acest termen nu are un echivalent bun \u00een limba rom\u00e2n\u0103.","canonical_url":"https:\/\/prohoster.info\/ro\/blog\/administrirovanie\/pro-multitenancy","robots":"max-image-preview:large","keywords":"","webmasterTools":{"miscellaneous":""},"schema":null,"og:locale":"ro_RO","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\/ro\/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\/ro\/wp-json\/wp\/v2\/posts\/55231","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/prohoster.info\/ro\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/prohoster.info\/ro\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/prohoster.info\/ro\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/prohoster.info\/ro\/wp-json\/wp\/v2\/comments?post=55231"}],"version-history":[{"count":0,"href":"https:\/\/prohoster.info\/ro\/wp-json\/wp\/v2\/posts\/55231\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/prohoster.info\/ro\/wp-json\/wp\/v2\/media\/55232"}],"wp:attachment":[{"href":"https:\/\/prohoster.info\/ro\/wp-json\/wp\/v2\/media?parent=55231"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/prohoster.info\/ro\/wp-json\/wp\/v2\/categories?post=55231"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/prohoster.info\/ro\/wp-json\/wp\/v2\/tags?post=55231"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}