{"id":89872,"date":"2020-07-27T01:42:19","date_gmt":"2020-07-26T23:42:19","guid":{"rendered":"https:\/\/prohoster.info\/blog\/administrirovanie\/raspredelyonnye-subd-dlya-enterprajza"},"modified":"2020-07-27T01:42:19","modified_gmt":"2020-07-26T23:42:19","slug":"raspredelyonnye-subd-dlya-enterprajza","status":"publish","type":"post","link":"https:\/\/prohoster.info\/ro\/blog\/administrirovanie\/raspredelyonnye-subd-dlya-enterprajza","title":{"rendered":"Baze de date distribuite pentru \u00eentreprinderi","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"<p>Teorema CAP este piatra de temelie a teoriei sistemelor distribuite. Evident, controversele \u00een jurul ei nu se sting: defini\u021biile nu sunt canonice, iar o dovad\u0103 riguroas\u0103 lipse\u0219te... Cu toate acestea, st\u00e2nd ferm pe pozi\u021biile bunului sim\u021b&trade;, \u00een\u021belegem din instinct c\u0103 teorema este corect\u0103.<\/p>\n<p><img decoding=\"async\" alt=\"Baze de date distribuite pentru \u00eentreprinderi\" src=\"\/wp-content\/uploads\/2020\/07\/35c8b29bb024cbf383d78caa1af2c525.png\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<br \/>\nSingurul lucru care nu este evident este semnifica\u021bia literei \u201eP\u201d. C\u00e2nd un cluster se separ\u0103, decide dac\u0103 s\u0103 nu r\u0103spund\u0103 p\u00e2n\u0103 c\u00e2nd nu se atinge un quor, sau s\u0103 ofere datele pe care le are. \u00cen func\u021bie de rezultatele acestei alegeri, sistemul este clasificat fie ca CP, fie ca AP. Cassandra, de exemplu, poate func\u021biona at\u00e2t \u00een mod CP, c\u00e2t \u0219i \u00een mod AP, \u00een func\u021bie nu doar de set\u0103rile cluster-ului, ci \u0219i de parametrii fiec\u0103rei cereri \u00een parte. Dar dac\u0103 sistemul nu este \u201eP\u201d \u0219i s-a separat, atunci \u2013 ce se \u00eent\u00e2mpl\u0103?<\/p>\n<p>R\u0103spunsul la aceast\u0103 \u00eentrebare este oarecum surprinz\u0103tor: un cluster CA nu se poate separa.<br \/>\nCe fel de cluster este acesta, care nu se poate separa?<br \/>\n<noindex><a rel=\"nofollow\" name=\"habracut\"><\/a><\/noindex><br \/>\nUn atribut esen\u021bial al unui astfel de cluster este un sistem comun de stocare a datelor. \u00cen cea mai mare parte a cazurilor, aceasta \u00eenseamn\u0103 conectarea prin SAN, ceea ce limiteaz\u0103 aplica\u021biile solu\u021biilor CA la mari \u00eentreprinderi capabile s\u0103 men\u021bin\u0103 o infrastructur\u0103 SAN. Pentru ca mai multe <a class=\"wpil_keyword_link\" href=\"https:\/\/prohoster.info\/ro\/server\/\"   title=\"servere\" data-wpil-keyword-link=\"linked\"  data-wpil-monitor-id=\"1512\">servere<\/a> s\u0103 poat\u0103 lucra cu acelea\u0219i date, este necesar\u0103 o sistem de fi\u0219iere clusterizat. Astfel de sisteme de fi\u0219iere sunt disponibile \u00een portofoliile HPE (CFS), Veritas (VxCFS) \u0219i IBM (GPFS). <\/p>\n<h4>Oracle RAC<\/h4>\n<p>\nOp\u021biunea Real Application Cluster a fost introdus\u0103 pentru prima dat\u0103 \u00een 2001 \u00een versiunea Oracle 9i. \u00centr-un astfel de cluster, mai multe instan\u021be <a class=\"wpil_keyword_link\" href=\"https:\/\/prohoster.info\/ro\/server\/dts-los-angeles\/\"   title=\"server\" data-wpil-keyword-link=\"linked\"  data-wpil-monitor-id=\"3642\">server<\/a> lucreaz\u0103 cu aceea\u0219i baz\u0103 de date.<br \/>\nOracle poate func\u021biona at\u00e2t cu un sistem de fi\u0219iere clusterizat, c\u00e2t \u0219i cu propria solu\u021bie \u2013 ASM, Automatic Storage Management.<\/p>\n<p>Fiecare instan\u021b\u0103 \u00ee\u0219i \u021bine jurnalul. O tranzac\u021bie este executat\u0103 \u0219i \u00eenregistrat\u0103 de o singur\u0103 instan\u021b\u0103. \u00cen caz de e\u0219ec al unei instan\u021be, unul dintre nodurile supravie\u021buitoare ale cluster-ului (instan\u021belor) cite\u0219te jurnalul s\u0103u \u0219i recupereaz\u0103 datele pierdute \u2013 astfel se asigur\u0103 disponibilitatea.<\/p>\n<p>Toate instan\u021bele \u00ee\u0219i men\u021bin propriul cache, iar acelea\u0219i pagini (blocuri) pot fi prezente simultan \u00een cache-urile mai multor instan\u021be. Mai mult, dac\u0103 o pagin\u0103 este necesar\u0103 unei instan\u021be \u0219i aceasta exist\u0103 \u00een cache-ul altei instan\u021be, ea o poate ob\u021bine de la \u201evecin\u201d prin intermediul mecanismului de fusionare a cache-ului \u00een loc s\u0103 o citeasc\u0103 de pe disc.<\/p>\n<p><img decoding=\"async\" alt=\"Baze de date distribuite pentru \u00eentreprinderi\" src=\"\/wp-content\/uploads\/2020\/07\/917cb1bfcc2c47ccf0dbb2f1e34ac921.png\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<br \/>\nDar ce se \u00eent\u00e2mpl\u0103 dac\u0103 unul dintre instan\u021be are nevoie s\u0103 modifice datele?<\/p>\n<p>Particularitatea Oracle este c\u0103 nu are un serviciu dedicat de blocare: dac\u0103 serverul dore\u0219te s\u0103 blocheze un r\u00e2nd, \u00eenregistrarea bloc\u0103rii este pus\u0103 direct pe pagina de memorie unde se afl\u0103 r\u00e2ndul blocat. Datorit\u0103 acestei abord\u0103ri, Oracle este campion \u00een performan\u021b\u0103 printre bazele de date monolitice: serviciul de blocare nu devine niciodat\u0103 un punct de \u00eengustare. \u00cens\u0103, \u00een configura\u021biile de cluster, o astfel de arhitectur\u0103 poate duce la schimburi intensificate de re\u021bea \u0219i bloc\u0103ri reciproc.<\/p>\n<p>Odat\u0103 ce \u00eenregistrarea este blocat\u0103, instan\u021ba notific\u0103 toate celelalte instan\u021be c\u0103 pagina \u00een care este stocat\u0103 aceast\u0103 \u00eenregistrare este ocupat\u0103 \u00een mod monopol. Dac\u0103 unei alte instan\u021be \u00eei va trebuie s\u0103 modifice \u00eenregistrarea de pe aceea\u0219i pagin\u0103, aceasta trebuie s\u0103 a\u0219tepte p\u00e2n\u0103 c\u00e2nd modific\u0103rile de pe pagin\u0103 sunt confirmate, adic\u0103 informa\u021bia despre modificare nu a fost \u00eenc\u0103 scris\u0103 \u00een jurnal pe disc (\u00een acest timp, tranzac\u021bia poate continua). Poate ap\u0103rea \u0219i situa\u021bia \u00een care pagina este modificat\u0103 consecutiv de mai multe instan\u021be, iar atunci, c\u00e2nd pagina este scris\u0103 pe disc, va trebui s\u0103 se determine cine de\u021bine versiunea actual\u0103 a acelei pagini.<\/p>\n<p>Actualiz\u0103rile accidentale ale acelora\u0219i pagini prin diferite noduri RAC conduc la o sc\u0103dere drastic\u0103 a performan\u021bei bazei de date - p\u00e2n\u0103 la punctul \u00een care performan\u021ba clusterului poate fi mai mic\u0103 dec\u00e2t cea a unei singure instan\u021be.<\/p>\n<p>Utilizarea corect\u0103 a Oracle RAC presupune divizarea fizic\u0103 a datelor (de exemplu, prin mecanismul tabelelor sec\u021bionate) \u0219i accesarea fiec\u0103rui set de sec\u021biuni printr-un nod dedicat. Principala destina\u021bie a RAC nu a devenit scalarea orizontal\u0103, ci asigurarea rezilien\u021bei la erori.<\/p>\n<p>Dac\u0103 un nod nu mai r\u0103spunde la heartbeat, atunci nodul care a descoperit acest lucru prima dat\u0103 initiaz\u0103 o procedur\u0103 de votare pe disc. Dac\u0103 \u0219i aici nodul pierdut nu se \u00eenregistreaz\u0103, unul dintre noduri \u00ee\u0219i asum\u0103 responsabilit\u0103\u021bile de recuperare a datelor:<\/p>\n<ul>\n<li>\u00ab\u00eenghea\u021b\u0103\u00bb toate paginile care erau \u00een cache-ul nodului pierdut;<\/li>\n<li>cite\u0219te jurnalele (redo) ale nodului pierdut \u0219i aplic\u0103 din nou modific\u0103rile \u00eenregistrate \u00een aceste jurnale, verific\u00e2nd \u00een acela\u0219i timp dac\u0103 alte noduri au versiuni mai recente ale paginilor modificate;<\/li>\n<li>revine tranzac\u021biile nefinalizate.<\/li>\n<\/ul>\n<p>\nPentru a simplifica comutarea \u00eentre noduri, Oracle are conceptul de serviciu \u2013 un exemplu virtual. Un exemplu poate deservi mai multe servicii, iar un serviciu poate migra \u00eentre noduri. Exemplul aplica\u021biei, care deserve\u0219te o anumit\u0103 parte a bazei de date (de exemplu, un grup de clien\u021bi), lucreaz\u0103 cu un singur serviciu, iar serviciul responsabil pentru aceast\u0103 parte a bazei de date migreaz\u0103 pe un alt nod \u00een cazul \u00een care un nod e\u0219ueaz\u0103.<\/p>\n<h4>IBM Pure Data Systems for Transactions<\/h4>\n<p>\nSolutia de cluster pentru SGBD a ap\u0103rut \u00een portofoliul Gigantului Albastru \u00een 2009. Ideologic, este urma\u0219ul clusterului Parallel Sysplex, construit pe echipamente \u201eobi\u0219nuite\u201d. \u00cen 2009 a fost lansat produsul DB2 pureScale, care reprezint\u0103 un pachet software, iar \u00een 2012 IBM ofer\u0103 un pachet software \u0219i hardware (appliance) denumit Pure Data Systems for Transactions. Nu trebuie confundat cu Pure Data Systems for Analytics, care nu este altceva dec\u00e2t un Netezza redenumit.<\/p>\n<p>Arhitectura pureScale pare la prima vedere similar\u0103 cu Oracle RAC: astfel, mai multe noduri sunt conectate la un sistem comun de stocare a datelor, \u0219i pe fiecare nod lucreaz\u0103 propria instan\u021b\u0103 SGBD cu propriile sale zone de memorie \u0219i jurnale de tranzac\u021bii. Dar, spre deosebire de Oracle, \u00een DB2 exist\u0103 un serviciu dedicat de blocare, reprezentat de un set de procese db2LLM*. \u00cen configura\u021bia clusterului, acest serviciu este transferat pe un nod separat, care \u00een Parallel Sysplex se nume\u0219te coupling facility (CF), iar \u00een Pure Data \u2013 PowerHA.<\/p>\n<p>PowerHA ofer\u0103 urm\u0103toarele servicii:<\/p>\n<ul>\n<li>manager de bloc\u0103ri;<\/li>\n<li>cache global de buffer;<\/li>\n<li>domeniu de comunica\u021bii interproces.<\/li>\n<\/ul>\n<p>\nPentru a transfera date de la PowerHA la nodurile Bazei de Date \u0219i \u00eenapoi, se utilizeaz\u0103 accesul la memorie de la distan\u021b\u0103, astfel \u00eenc\u00e2t interconectarea clusterului trebuie s\u0103 suporte protocolul RDMA. PureScale poate utiliza at\u00e2t Infiniband, c\u00e2t \u0219i RDMA peste Ethernet.<\/p>\n<p><img decoding=\"async\" alt=\"Baze de date distribuite pentru \u00eentreprinderi\" src=\"\/wp-content\/uploads\/2020\/07\/7757acd68445dac4a9f378d5813e663f.png\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<br \/>\nDac\u0103 nodul are nevoie de o pagin\u0103, iar acea pagin\u0103 nu se afl\u0103 \u00een cache, nodul solicit\u0103 pagina din cache-ul global, \u0219i doar \u00een acel caz, dac\u0103 nici acolo nu este, o cite\u0219te de pe disc. Spre deosebire de Oracle, cererea se face doar \u00een PowerHA, nu \u0219i la nodurile adiacente.<\/p>\n<p>Dac\u0103 un nod inten\u021bioneaz\u0103 s\u0103 modifice o linie, acesta o blocheaz\u0103 \u00een modul exclusiv, iar pagina unde se afl\u0103 linia \u2013 \u00een mod partajat. Toate bloc\u0103rile sunt \u00eenregistrate \u00een managerul global de bloc\u0103ri. C\u00e2nd tranzac\u021bia se finalizeaz\u0103, nodul trimite un mesaj managerului de bloc\u0103ri, care copiaz\u0103 pagina modificat\u0103 \u00een cache-ul global, elimin\u0103 bloc\u0103rile \u0219i invalideaz\u0103 pagina modificat\u0103 \u00een cache-urile altor noduri.<\/p>\n<p>Dac\u0103 pagina pe care se afl\u0103 linia modificabil\u0103 este deja blocat\u0103, managerul de bloc\u0103ri va citi pagina modificat\u0103 din memoria nodului care a efectuat modific\u0103rile, va elimina blocarea, va invalida pagina modificat\u0103 \u00een cache-urile altor noduri \u0219i va restitui blocarea paginii nodului care a solicitat-o.<\/p>\n<p>\"Pagini murdare\", adic\u0103 modificate, pot fi scrise pe disc at\u00e2t de la un nod obi\u0219nuit, c\u00e2t \u0219i de la PowerHA (castout).<\/p>\n<p>\u00cen cazul unui defect al unui nod pureScale, recuperarea este limitat\u0103 doar la tranzac\u021biile care \u00een momentul \u00eentreruperii nu au fost \u00eenc\u0103 finalizate: paginile modificate de acest nod \u00een tranzac\u021biile finalizate se afl\u0103 \u00een cache-ul global de pe PowerHA. Nodul se reporne\u0219te \u00eentr-o configura\u021bie restr\u00e2ns\u0103 pe unul dintre serverele clusterului, anuleaz\u0103 tranzac\u021biile nefinalizate \u0219i elibereaz\u0103 bloc\u0103rile.<\/p>\n<p>PowerHA func\u021bioneaz\u0103 pe dou\u0103 servere, iar nodul principal replic\u0103 starea sa sincron. \u00cen cazul unui defect al nodului principal, clusterul PowerHA continu\u0103 s\u0103 func\u021bioneze cu nodul de rezerv\u0103.<br \/>\nDesigur, dac\u0103 se acceseaz\u0103 un set de date printr-un singur nod, performan\u021ba general\u0103 a clusterului va fi mai bun\u0103. PureScale poate chiar observa c\u0103 o anumit\u0103 zon\u0103 de date este procesat\u0103 de un singur nod, iar atunci toate bloc\u0103rile asociate acestei zone vor fi gestionate local de nod f\u0103r\u0103 comunic\u0103ri cu PowerHA. Dar de \u00eendat\u0103 ce aplica\u021bia \u00eencearc\u0103 s\u0103 acceseze aceste date printr-un alt nod, procesarea centralizat\u0103 a bloc\u0103rilor va fi reluat\u0103.<\/p>\n<p>Testele interne IBM pe o sarcin\u0103 compus\u0103 din 90% citiri \u0219i 10% scrieri, ceea ce seam\u0103n\u0103 foarte mult cu o sarcin\u0103 industrial\u0103 real\u0103, arat\u0103 o scalare aproape liniar\u0103 p\u00e2n\u0103 la 128 de noduri. Din p\u0103cate, condi\u021biile de testare nu sunt dezv\u0103luite.<\/p>\n<h4>HPE NonStop SQL<\/h4>\n<p>\nPlatforma sa de \u00eenalt\u0103 disponibilitate este disponibil\u0103 \u0219i \u00een portofoliul Hewlett-Packard Enterprise. Aceasta este platforma NonStop, lansat\u0103 pe pia\u021b\u0103 \u00een 1976 de compania Tandem Computers. \u00cen 1997, compania a fost achizi\u021bionat\u0103 de Compaq, care, la r\u00e2ndul s\u0103u, s-a integrat \u00een Hewlett-Packard \u00een 2002.<\/p>\n<p>NonStop este utilizat\u0103 pentru construirea aplica\u021biilor critice \u2013 de exemplu, HLR sau procesarea cardurilor bancare. Platforma este disponibil\u0103 ca un complex software-hardware (appliance), care include noduri de calcul, un sistem de stocare a datelor \u0219i echipamente de comunica\u021bie. Re\u021beaua ServerNet (\u00een sistemele moderne \u2013 Infiniband) serve\u0219te at\u00e2t pentru schimbul de date \u00eentre noduri, c\u00e2t \u0219i pentru accesul la sistemul de stocare a datelor.<\/p>\n<p>\u00cen versiunile anterioare ale sistemului, erau utilizate procesoare proprietare, care erau sincronizate \u00eentre ele: toate opera\u021biile erau executate sincron de c\u0103tre mai multe procesoare, \u0219i de \u00eendat\u0103 ce unul dintre procesoare \u00eent\u00e2mpina o eroare, se deconecta, \u00een timp ce cel\u0103lalt continua s\u0103 func\u021bioneze. Ulterior, sistemul a trecut la procesoare standard (ini\u021bial MIPS, apoi Itanium \u0219i, \u00een cele din urm\u0103, x86), iar pentru sincronizare au fost folosite alte mecanisme:<\/p>\n<ul>\n<li>mesaje: fiecare proces de sistem are un duplicat-\u201eumbr\u0103\u201d, c\u0103ruia procesul activ \u00eei trimite periodic mesaje despre starea sa; \u00een cazul unei erori a procesului principal, procesul umbr\u0103 \u00eencepe s\u0103 func\u021bioneze din punctul stabilit de ultimul mesaj;<\/li>\n<li>votare: sistemul de stocare a datelor are un component hardware special, care prime\u0219te mai multe solicit\u0103ri identice \u0219i le execut\u0103 doar dac\u0103 acestea coincid; \u00een loc de sincronizare fizic\u0103, procesoarele func\u021bioneaz\u0103 asincron, iar rezultatele muncii lor sunt comparate doar \u00een momentele de intrare\/ie\u0219ire.<\/li>\n<\/ul>\n<p>\n\u00cencep\u00e2nd din 1987, platforma NonStop g\u0103zduie\u0219te un sistem de gestionare a bazelor de date rela\u021bionale \u2013 mai \u00eent\u00e2i SQL\/MP, iar mai t\u00e2rziu \u2013 SQL\/MX.<\/p>\n<p>\u00centreaga baz\u0103 de date este \u00eemp\u0103r\u021bit\u0103 \u00een p\u0103r\u021bi, fiecare parte fiind gestionat\u0103 de propriul proces Data Access Manager (DAM). Acesta asigur\u0103 scrierea datelor, caching-ul \u0219i mecanismul de blocare. Procesarea datelor este efectuat\u0103 de procesele executante (Executor Server Process), care ruleaz\u0103 pe acelea\u0219i noduri ca \u0219i managerii de date aferen\u021bi. Scheduler-ul SQL\/MX \u00eemparte sarcinile \u00eentre executan\u021bi \u0219i combin\u0103 rezultatele. \u00cen cazul \u00een care este necesar\u0103 efectuarea modific\u0103rilor coordonate, se folose\u0219te protocolul de confirmare \u00een dou\u0103 faze, asigurat de biblioteca TMF (Transaction Management Facility).<\/p>\n<p><img decoding=\"async\" alt=\"Baze de date distribuite pentru \u00eentreprinderi\" src=\"\/wp-content\/uploads\/2020\/07\/00e9473dd95a78c409dd5283d299fe96.png\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<br \/>\nNonStop SQL prioritizeaz\u0103 procesele astfel \u00eenc\u00e2t interog\u0103rile analitice de lung\u0103 durat\u0103 s\u0103 nu interfereze cu executarea transac\u021biilor. Totu\u0219i, scopul s\u0103u este de a gestiona transac\u021bii scurte, nu analiza. Dezvoltatorul garanteaz\u0103 disponibilitatea clusterului NonStop la nivel de cinci \u201enou\u0103\u201d, adic\u0103 downtime-ul este de doar 5 minute pe an.<\/p>\n<h4>SAP HANA<\/h4>\n<p>\nPrima versiune stabil\u0103 a SGBD-ului HANA (1.0) a fost lansat\u0103 \u00een noiembrie 2010, iar pachetul SAP ERP a trecut la HANA \u00eencep\u00e2nd cu mai 2013. Platforma se bazeaz\u0103 pe tehnologii achizi\u021bionate: motorul de c\u0103utare TREX (pentru c\u0103utarea \u00een stocarea pe coloane), SGBD P*TIME \u0219i MAX DB.<\/p>\n<p>Cuv\u00e2ntul \u201eHANA\u201d este un acronim pentru High Performance ANalytical Appliance. Acest SGBD este disponibil sub form\u0103 de cod care poate func\u021biona pe orice servere x86, \u00eens\u0103 instala\u021biile industriale sunt permise doar pe echipamente certificate. Exist\u0103 solu\u021bii de la HP, Lenovo, Cisco, Dell, Fujitsu, Hitachi, NEC. Unele configura\u021bii Lenovo permit chiar exploatarea f\u0103r\u0103 SAN \u2013 clusterul GPFS pe discurile locale joac\u0103 rolul unui stocare comun\u0103.<\/p>\n<p>Spre deosebire de platformele men\u021bionate mai sus, HANA este un SGBD \u00een memorie, adic\u0103 imaginea primar\u0103 a datelor este stocat\u0103 \u00een memoria RAM, iar pe disc sunt scrise doar jurnalele \u0219i instantaneele periodice \u2013 pentru recuperare \u00een caz de avarie.<\/p>\n<p><img decoding=\"async\" alt=\"Baze de date distribuite pentru \u00eentreprinderi\" src=\"\/wp-content\/uploads\/2020\/07\/f64194ca6de13e1a93f7190dc38ad2d7.png\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<br \/>\nFiecare nod al clusterului HANA este responsabil pentru partea sa de date, iar harta datelor este stocat\u0103 \u00eentr-un component special \u2013 Name Server, situat pe nodul coordonator. Datele \u00eentre noduri nu sunt duplicate. Informa\u021biile despre blocaje sunt de asemenea stocate pe fiecare nod, dar \u00een sistem exist\u0103 un detector global de blocaje.<\/p>\n<p>Client HANA, when connecting to the cluster, loads its topology and can subsequently address any node directly depending on the data it needs. If the transaction involves data from a single node, it can be executed locally by that node, but if data from multiple nodes is being modified, the initiating node communicates with the coordinating node, which opens and coordinates the distributed transaction, committing it using an optimized two-phase commit protocol.<\/p>\n<p>The coordinating node is duplicated, so in case the coordinator fails, a backup node immediately takes over. However, if a data node fails, the only way to access its data is to restart the node. Typically, HANA clusters maintain a spare server to quickly restart the lost node.<br \/>\n<br \/>Sursa: <a content=\"nofollow\" rel=\"nofollow\" href=\"https:\/\/habr.com\/ru\/post\/512298\/\">habr.com<\/a> <\/p>","protected":false,"gt_translate_keys":[{"key":"rendered","format":"html"}]},"excerpt":{"rendered":"<p>CAP-\u0442\u0435\u043e\u0440\u0435\u043c\u0430 \u044f\u0432\u043b\u044f\u0435\u0442\u0441\u044f \u043a\u0440\u0430\u0435\u0443\u0433\u043e\u043b\u044c\u043d\u044b\u043c \u043a\u0430\u043c\u043d\u0435\u043c \u0442\u0435\u043e\u0440\u0438\u0438 \u0440\u0430\u0441\u043f\u0440\u0435\u0434\u0435\u043b\u0451\u043d\u043d\u044b\u0445 \u0441\u0438\u0441\u0442\u0435\u043c. \u041a\u043e\u043d\u0435\u0447\u043d\u043e, \u0441\u043f\u043e\u0440\u044b \u0432\u043e\u043a\u0440\u0443\u0433 \u043d\u0435\u0451 \u043d\u0435 \u0443\u0442\u0438\u0445\u0430\u044e\u0442: \u0438 \u043e\u043f\u0440\u0435\u0434\u0435\u043b\u0435\u043d\u0438\u044f \u0432 \u043d\u0435\u0439 \u043d\u0435 \u043a\u0430\u043d\u043e\u043d\u0438\u0447\u0435\u0441\u043a\u0438\u0435, \u0438 \u0441\u0442\u0440\u043e\u0433\u043e\u0433\u043e \u0434\u043e\u043a\u0430\u0437\u0430\u0442\u0435\u043b\u044c\u0441\u0442\u0432\u0430 \u043d\u0435\u0442\u2026 \u0422\u0435\u043c \u043d\u0435 \u043c\u0435\u043d\u0435\u0435, \u0442\u0432\u0451\u0440\u0434\u043e \u0441\u0442\u043e\u044f \u043d\u0430 \u043f\u043e\u0437\u0438\u0446\u0438\u044f\u0445 \u0431\u044b\u0442\u043e\u0432\u043e\u0433\u043e \u0437\u0434\u0440\u0430\u0432\u043e\u0433\u043e \u0441\u043c\u044b\u0441\u043b\u0430&trade;, \u043c\u044b \u0438\u043d\u0442\u0443\u0438\u0442\u0438\u0432\u043d\u043e \u043f\u043e\u043d\u0438\u043c\u0430\u0435\u043c, \u0447\u0442\u043e \u0442\u0435\u043e\u0440\u0435\u043c\u0430 \u0432\u0435\u0440\u043d\u0430. \u0415\u0434\u0438\u043d\u0441\u0442\u0432\u0435\u043d\u043d\u043e\u0435, \u0447\u0442\u043e \u043d\u0435 \u043e\u0447\u0435\u0432\u0438\u0434\u043d\u043e, \u0442\u0430\u043a \u044d\u0442\u043e \u0437\u043d\u0430\u0447\u0435\u043d\u0438\u0435 \u0431\u0443\u043a\u0432\u044b \u00abP\u00bb. \u041a\u043e\u0433\u0434\u0430 \u043a\u043b\u0430\u0441\u0442\u0435\u0440 \u0440\u0430\u0437\u0434\u0435\u043b\u0438\u043b\u0441\u044f, \u043e\u043d \u0440\u0435\u0448\u0430\u0435\u0442 \u2013 \u0442\u043e [&hellip;]<\/p>\n","protected":false,"gt_translate_keys":[{"key":"rendered","format":"html"}]},"author":1,"featured_media":89873,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[688],"tags":[],"class_list":["post-89872","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.2.1 - aioseo.com -->\n\t<meta name=\"description\" content=\"CAP-\u0442\u0435\u043e\u0440\u0435\u043c\u0430 \u044f\u0432\u043b\u044f\u0435\u0442\u0441\u044f \u043a\u0440\u0430\u0435\u0443\u0433\u043e\u043b\u044c\u043d\u044b\u043c \u043a\u0430\u043c\u043d\u0435\u043c \u0442\u0435\u043e\u0440\u0438\u0438 \u0440\u0430\u0441\u043f\u0440\u0435\u0434\u0435\u043b\u0451\u043d\u043d\u044b\u0445 \u0441\u0438\u0441\u0442\u0435\u043c.\" \/>\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\/ro\/blog\/administrirovanie\/raspredelyonnye-subd-dlya-enterprajza\" \/>\n\t<meta name=\"generator\" content=\"All in One SEO (AIOSEO) 5.0.2.1\" \/>\n\t\t<meta property=\"og:locale\" content=\"ro_RO\" \/>\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\u0420\u0430\u0441\u043f\u0440\u0435\u0434\u0435\u043b\u0451\u043d\u043d\u044b\u0435 \u0421\u0423\u0411\u0414 \u0434\u043b\u044f \u044d\u043d\u0442\u0435\u0440\u043f\u0440\u0430\u0439\u0437\u0430 | ProHoster\" \/>\n\t\t<meta property=\"og:description\" content=\"CAP-\u0442\u0435\u043e\u0440\u0435\u043c\u0430 \u044f\u0432\u043b\u044f\u0435\u0442\u0441\u044f \u043a\u0440\u0430\u0435\u0443\u0433\u043e\u043b\u044c\u043d\u044b\u043c \u043a\u0430\u043c\u043d\u0435\u043c \u0442\u0435\u043e\u0440\u0438\u0438 \u0440\u0430\u0441\u043f\u0440\u0435\u0434\u0435\u043b\u0451\u043d\u043d\u044b\u0445 \u0441\u0438\u0441\u0442\u0435\u043c.\" \/>\n\t\t<meta property=\"og:url\" content=\"https:\/\/prohoster.info\/ro\/blog\/administrirovanie\/raspredelyonnye-subd-dlya-enterprajza\" \/>\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-07-26T23:42:19+00:00\" \/>\n\t\t<meta property=\"article:modified_time\" content=\"2020-07-26T23:42: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\udd47Sisteme de gestionare a bazelor de date distribuite pentru \u00eentreprinderi | ProHoster","description":"The CAP theorem is the cornerstone of distributed systems theory.","canonical_url":"https:\/\/prohoster.info\/ro\/blog\/administrirovanie\/raspredelyonnye-subd-dlya-enterprajza","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\u0420\u0430\u0441\u043f\u0440\u0435\u0434\u0435\u043b\u0451\u043d\u043d\u044b\u0435 \u0421\u0423\u0411\u0414 \u0434\u043b\u044f \u044d\u043d\u0442\u0435\u0440\u043f\u0440\u0430\u0439\u0437\u0430 | ProHoster","og:description":"CAP-\u0442\u0435\u043e\u0440\u0435\u043c\u0430 \u044f\u0432\u043b\u044f\u0435\u0442\u0441\u044f \u043a\u0440\u0430\u0435\u0443\u0433\u043e\u043b\u044c\u043d\u044b\u043c \u043a\u0430\u043c\u043d\u0435\u043c \u0442\u0435\u043e\u0440\u0438\u0438 \u0440\u0430\u0441\u043f\u0440\u0435\u0434\u0435\u043b\u0451\u043d\u043d\u044b\u0445 \u0441\u0438\u0441\u0442\u0435\u043c.","og:url":"https:\/\/prohoster.info\/ro\/blog\/administrirovanie\/raspredelyonnye-subd-dlya-enterprajza","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-07-26T23:42:19+00:00","article:modified_time":"2020-07-26T23:42:19+00:00","article:publisher":"https:\/\/www.facebook.com\/prohoster","article:author":"https:\/\/www.facebook.com\/prohoster"},"aioseo_meta_data":{"post_id":"89872","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 13:03:25","updated":"2026-02-22 15:29:33","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\/89872","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=89872"}],"version-history":[{"count":2,"href":"https:\/\/prohoster.info\/ro\/wp-json\/wp\/v2\/posts\/89872\/revisions"}],"predecessor-version":[{"id":162170,"href":"https:\/\/prohoster.info\/ro\/wp-json\/wp\/v2\/posts\/89872\/revisions\/162170"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/prohoster.info\/ro\/wp-json\/wp\/v2\/media\/89873"}],"wp:attachment":[{"href":"https:\/\/prohoster.info\/ro\/wp-json\/wp\/v2\/media?parent=89872"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/prohoster.info\/ro\/wp-json\/wp\/v2\/categories?post=89872"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/prohoster.info\/ro\/wp-json\/wp\/v2\/tags?post=89872"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}