{"id":30666,"date":"2019-10-31T21:36:48","date_gmt":"2019-10-31T18:36:48","guid":{"rendered":"https:\/\/prohoster.info\/blog\/byla-la-mongodb-voobshhe-pravilnym-vyborom\/"},"modified":"2019-10-31T21:36:48","modified_gmt":"2019-10-31T18:36:48","slug":"byla-la-mongodb-voobshhe-pravilnym-vyborom","status":"publish","type":"post","link":"https:\/\/prohoster.info\/ro\/blog\/administrirovanie\/byla-la-mongodb-voobshhe-pravilnym-vyborom","title":{"rendered":"A fost cu adev\u0103rat MongoDB o alegere corect\u0103?","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"<p>Recent am aflat c\u0103 <noindex><a rel=\"nofollow\" href=\"https:\/\/www.redhat.com\/en\/blog\/red-hat-satellite-standardize-postgresql-backend\">Red Hat elimin\u0103 suportul pentru MongoDB din Satellite<\/a><\/noindex> (se spune c\u0103 din cauza schimb\u0103rilor de licen\u021b\u0103). Acest lucru m-a f\u0103cut s\u0103 reflectez la faptul c\u0103 \u00een ultimii ani am v\u0103zut o mul\u021bime de articole despre c\u00e2t de teribil\u0103 este MongoDB \u0219i c\u0103 nimeni nu ar trebui s\u0103 o foloseasc\u0103 vreodat\u0103. Dar \u00een acest timp, MongoDB a devenit un produs mult mai matur. Ce s-a \u00eent\u00e2mplat? Oare toat\u0103 antipatia provine din gre\u0219elile din prima etap\u0103 de marketing a acestei noi baze de date?<\/p>\n<p>Dac\u0103 cumva crede\u021bi c\u0103 ap\u0103r MongoDB, v\u0103 rog s\u0103 citi\u021bi <noindex><a rel=\"nofollow\" href=\"#1\">disclaimerul<\/a><\/noindex> de la sf\u00e2r\u0219itul articolului.<br \/>\n<noindex><a rel=\"nofollow\" name=\"habracut\"><\/a><\/noindex><\/p>\n<h1>O nou\u0103 tendin\u021b\u0103<\/h1>\n<p>\nLucrez \u00een industria software de mai mul\u021bi ani dec\u00e2t e frumos s\u0103 spun, dar totu\u0219i mi-a revenit doar o mic\u0103 parte din tendin\u021bele care au lovit industria noastr\u0103. Am fost martor la cre\u0219terea 4GL, AOP, Agile, SOA, Web 2.0, AJAX, blockchain\u2026 lista este nesf\u00e2r\u0219it\u0103. Fiecare an aduce noi tendin\u021be. Unele se sting rapid, \u00een timp ce altele schimb\u0103 \u00een mod fundamental metodele de dezvoltare software.<\/p>\n<p>\u00cen jurul fiec\u0103rei noi tendin\u021be se creeaz\u0103 o anumit\u0103 agita\u021bie: oamenii sau sar singuri \u00een barc\u0103, sau observ\u0103 zgomotul generat de al\u021bii \u2013 \u0219i se al\u0103tur\u0103 mul\u021bimii. Acest proces a fost codificat de compania Gartner \u00een <noindex><a rel=\"nofollow\" href=\"https:\/\/en.wikipedia.org\/wiki\/Hype_cycle\">ciclul hype<\/a><\/noindex>. De\u0219i controversat, acest grafic descrie \u00een mare parte ce se \u00eent\u00e2mpl\u0103 cu tehnologiile \u00eenainte de a deveni \u00een cele din urm\u0103 utile.<\/p>\n<p>Dar din c\u00e2nd \u00een c\u00e2nd apare (sau are loc a doua venire, ca \u00een acest caz) o nou\u0103 inova\u021bie, determinat\u0103 doar de o singur\u0103 implementare specific\u0103. \u00cen cazul NoSQL, hype-ul a fost profund influen\u021bat de apari\u021bia \u0219i ascensiunea rapid\u0103 a MongoDB. Nu MongoDB a creat aceast\u0103 tendin\u021b\u0103: de fapt, problemele de procesare a unor cantit\u0103\u021bi mari de date au ap\u0103rut ini\u021bial \u00een companii mari de internet, ceea ce a dus la revenirea bazelor de date nerela\u021bionale. Mi\u0219carea a \u00eenceput cu proiecte precum Bigtable de la Google \u0219i Cassandra de la Facebook, dar MongoDB a devenit cea mai cunoscut\u0103 \u0219i accesibil\u0103 implementare a unei baze de date NoSQL, la care au avut acces majoritatea dezvoltatorilor.<\/p>\n<p><i>Not\u0103: a\u021bi putea crede c\u0103 amestec documentele Baze de Date cu Baze de Date coloane, stoc\u0103ri cheie\/valoare sau oricare dintre numeroasele alte tipuri de stoc\u0103ri de date care se \u00eencadreaz\u0103 \u00een defini\u021bia general\u0103 NoSQL. \u0218i ave\u021bi dreptate. Dar \u00een acel moment exista haos. Toat\u0103 lumea era obsedat\u0103 de NoSQL, toat\u0103 lumea o dorea. <b>absolut<\/b> necesar, de\u0219i mul\u021bi nu au observat diferen\u021bele dintre diferitele tehnologii. Pentru mul\u021bi, MongoDB a devenit <b>sindromul<\/b> NoSQL.<\/i><\/p>\n<p>\u0218i dezvoltatorii s-au av\u00e2ntat spre ea. Ideea unei baze de date f\u0103r\u0103 schem\u0103, care se scaleaz\u0103 magic pentru a rezolva orice problem\u0103, era destul de atr\u0103g\u0103toare. Aproape \u00een 2014, p\u0103rea c\u0103 peste tot unde cu un an \u00eenainte era utilizat\u0103 o baz\u0103 de date rela\u021bional\u0103, precum MySQL, Postgres sau SQL Server, s-au \u00eenceput desf\u0103\u0219ur\u0103ri de baze MongoDB. La \u00eentrebarea de ce, puteai ob\u021bine un r\u0103spuns de la banalul \u201eeste scalarea web-ului\u201d p\u00e2n\u0103 la cel mai bine g\u00e2ndit \u201edatele mele sunt foarte slab structurate \u0219i se potrivesc bine \u00eentr-o baz\u0103 de date f\u0103r\u0103 schem\u0103\u201d.<\/p>\n<p>Este important s\u0103 ne amintim c\u0103 MongoDB \u0219i bazele de date documente, \u00een general, rezolv\u0103 o serie de probleme asociate cu bazele de date rela\u021bionale tradi\u021bionale:<\/p>\n<ul>\n<li><b>Schema strict\u0103<\/b>: cu o baz\u0103 de date rela\u021bional\u0103, dac\u0103 ai date generate dinamic, e\u0219ti nevoit fie s\u0103 creezi o mul\u021bime de coloane de date \u201ediferite\u201d \u00eent\u00e2mpl\u0103toare, s\u0103 stochezi date blob acolo sau s\u0103 folose\u0219ti o configura\u021bie <noindex><a rel=\"nofollow\" href=\"https:\/\/en.wikipedia.org\/wiki\/Entity%E2%80%93attribute%E2%80%93value_model\">EAV<\/a><\/noindex>\u2026 toate acestea au dezavantaje semnificative.\n<\/li>\n<li><b>Dificultatea scal\u0103rii<\/b>: dac\u0103 datele sunt at\u00e2t de multe \u00eenc\u00e2t nu \u00eencap pe un singur server, MongoDB oferea mecanisme care permiteau scalarea lor pe mai multe ma\u0219ini.\n<\/li>\n<li><b>Modific\u0103ri complicate ale schemei<\/b>: f\u0103r\u0103 migra\u021bii! \u00centr-o baz\u0103 de date rela\u021bional\u0103, schimbarea structurii bazei de date poate deveni o problem\u0103 uria\u0219\u0103 (mai ales c\u00e2nd datele devin foarte multe). MongoDB a reu\u0219it s\u0103 simplifice semnificativ procesul. A f\u0103cut-o at\u00e2t de u\u0219or, \u00eenc\u00e2t po\u021bi actualiza schema \u00een mi\u0219care \u0219i s\u0103 avansezi foarte repede.\n<\/li>\n<li><b>Performan\u021ba \u00een scriere<\/b>: performan\u021ba MongoDB a fost bun\u0103, \u00een special cu o configurare adecvat\u0103. Chiar \u0219i configura\u021bia MongoDB din fabric\u0103, pentru care a fost adesea criticat\u0103, a ar\u0103tat unele rezultate impresionante de performan\u021b\u0103.<\/li>\n<\/ul>\n<p><\/p>\n<h1>Toate riscurile pe tine<\/h1>\n<p>\nBeneficiile poten\u021biale ale MongoDB au fost uria\u0219e, \u00een special pentru anumite categorii de probleme. Dac\u0103 cite\u0219ti lista de mai sus f\u0103r\u0103 a \u00een\u021belege contextul \u0219i f\u0103r\u0103 experien\u021b\u0103, s-ar putea s\u0103 ai impresia c\u0103 MongoDB este cu adev\u0103rat o SGBD revolu\u021bionar\u0103. Singura problem\u0103 era c\u0103 avantajele enumerate mai sus erau \u00eenso\u021bite de o serie de avertismente, dintre care unele sunt men\u021bionate mai jos.<\/p>\n<p>Pentru a fi corect, nimeni de la 10gen\/MongoDB Inc. nu va spune c\u0103 cele ce urmeaz\u0103 sunt neadev\u0103rate, acestea sunt doar compromisuri.<\/p>\n<ul>\n<li><b>Pierderea tranzac\u021biilor<\/b>: tranzac\u021biile sunt o caracteristic\u0103 principal\u0103 a multor baze de date rela\u021bionale (nu a tuturor, dar a majorit\u0103\u021bii). Tranzac\u021bionalitatea \u00eenseamn\u0103 c\u0103 po\u021bi efectua mai multe opera\u021biuni atomic \u0219i po\u021bi garanta c\u0103 datele vor r\u0103m\u00e2ne consistente. Desigur, \u00een cazul unei baze de date NoSQL, tranzac\u021bionalitatea poate fi pe un singur document sau po\u021bi utiliza commituri \u00een dou\u0103 faze pentru a ob\u021bine semantic\u0103 tranzac\u021bional\u0103. Dar va trebui s\u0103 implementezi tu aceast\u0103 func\u021bionalitate... ceea ce poate fi o sarcin\u0103 complex\u0103 \u0219i consumatoare de timp. Adesea nu realizezi problemele p\u00e2n\u0103 nu vezi c\u0103 datele din baza de date ajung \u00een st\u0103ri invalide, deoarece nu po\u021bi garanta atomicitatea opera\u021biunilor. <b>Not\u0103: mul\u021bi mi-au spus c\u0103 anul trecut, \u00een MongoDB 4.0, au ap\u0103rut tranzac\u021bii, dar cu o serie de restric\u021bii. Concluzia articolului r\u0103m\u00e2ne aceea\u0219i: evalueaz\u0103 c\u00e2t de bine se potrive\u0219te tehnologia nevoilor tale.<\/b>\n<\/li>\n<li><b>Pierderea integrit\u0103\u021bii rela\u021bionale (chei externe)<\/b>: dac\u0103 datele tale au rela\u021bii, va trebui s\u0103 le aplici \u00een aplica\u021bie. O baz\u0103 de date care respect\u0103 aceste rela\u021bii va reduce semnificativ din munca \u00een aplica\u021bie \u0219i, prin urmare, din sarcinile programatorilor t\u0103i.\n<\/li>\n<li><b>Lipsa posibilit\u0103\u021bii de a aplica structura de date<\/b>: schemele stricte pot deveni uneori o problem\u0103 mare, dar sunt, de asemenea, un mecanism puternic pentru structurarea corect\u0103 a datelor, dac\u0103 sunt folosite bine. Bazele de date documentare, precum MongoDB, ofer\u0103 o flexibilitate incredibil\u0103 a schemei, dar aceast\u0103 flexibilitate elimin\u0103 responsabilitatea de a men\u021bine datele curate. Dac\u0103 nu ai grij\u0103 de acestea, \u00een cele din urm\u0103 va trebui s\u0103 scrii mult cod \u00een aplica\u021bie pentru a \u021bine cont de datele care sunt stocate \u00eentr-o form\u0103 diferit\u0103 de cea pe care o a\u0219tep\u021bi. A\u0219a cum spunem adesea \u00een compania noastr\u0103 Simple Thread\u2026 aplica\u021bia va fi rescris\u0103 c\u00e2ndva, dar datele vor tr\u0103i ve\u0219nic. <b>Not\u0103: MongoDB suport\u0103 verificarea schemei: este util\u0103, dar nu ofer\u0103 acelea\u0219i garan\u021bii ca o baz\u0103 de date rela\u021bional\u0103. \u00cen primul r\u00e2nd, ad\u0103ugarea sau modificarea verific\u0103rii schemei nu afecteaz\u0103 datele existente \u00een colec\u021bie. Trebuie s\u0103 te asiguri c\u0103 actualizezi datele conform noii scheme. Decide singur dac\u0103 este suficient pentru nevoile tale.<\/b>\n<\/li>\n<li><b>Limbaj de interogare propriu \/ pierdere a ecosistemului de instrumente<\/b>: apari\u021bia SQL a fost o revolu\u021bie absolut\u0103, \u0219i de atunci nimic nu s-a schimbat. Este un limbaj incredibil de puternic, dar destul de complex. Necesitatea de a construi interog\u0103ri la baze de date \u00eentr-un nou limbaj, format din fragmente JSON, este considerat\u0103 un mare pas \u00eenapoi de persoanele cu experien\u021b\u0103 \u00een SQL. Exist\u0103 o \u00eentreag\u0103 univers de instrumente care interac\u021bioneaz\u0103 cu bazele de date SQL: de la IDE-uri la instrumente de raportare. Trecerea la o baz\u0103 de date care nu suport\u0103 SQL \u00eenseamn\u0103 c\u0103 nu po\u021bi folosi majoritatea acestor instrumente sau trebuie s\u0103 converte\u0219ti datele \u00een SQL pentru a le folosi, ceea ce poate fi mai complicat dec\u00e2t crezi.<\/li>\n<\/ul>\n<p>\nMul\u021bi dezvoltatori care s-au \u00eendreptat spre MongoDB nu \u00een\u021belegeau foarte bine compromisurile \u0219i, adesea, s-au aruncat cu capul \u00eenainte, stabilind-o ca principal\u0103 solu\u021bie de stocare a datelor. Dup\u0103 aceea, a fost de obicei incredibil de greu s\u0103 te \u00eentorci \u00eenapoi.<\/p>\n<h1>Ce s-ar fi putut face diferit?<\/h1>\n<p>\nNu toat\u0103 lumea a s\u0103rit cu capul \u00eenainte \u0219i a lovit fundul. Dar multe proiecte au instalat baza MongoDB acolo unde pur \u0219i simplu nu era potrivit\u0103 - \u0219i vor trebui s\u0103 tr\u0103iasc\u0103 cu ea mul\u021bi ani de acum \u00eenainte. Dac\u0103 aceste organiza\u021bii ar fi petrecut pu\u021bin timp \u0219i ar fi g\u00e2ndit metodic alegerea tehnologiilor, multe ar fi f\u0103cut o alegere diferit\u0103.<\/p>\n<p>Cum s\u0103 alegi tehnologia potrivit\u0103? Au fost c\u00e2teva \u00eencerc\u0103ri de a crea un cadru sistematic pentru evaluarea tehnologiilor, cum ar fi <noindex><a rel=\"nofollow\" href=\"http:\/\/www.wohlin.eu\/spi96.pdf\">\u201eCadru pentru implementarea tehnologiilor \u00een organiza\u021bii software\u201d<\/a><\/noindex> \u0219i <noindex><a rel=\"nofollow\" href=\"https:\/\/pdfs.semanticscholar.org\/4268\/30dd5dd944d3b75ec56b2a3b151c18afbaf9.pdf\">\u201eCadru pentru evaluarea tehnologiilor software\u201d<\/a><\/noindex>, dar mi se pare c\u0103 este o complexitate excesiv\u0103.<\/p>\n<p>Multe tehnologii pot fi evalutate \u00een mod ra\u021bional, pun\u00e2nd doar dou\u0103 \u00eentreb\u0103ri de baz\u0103. <b>Problema const\u0103 \u00een g\u0103sirea oamenilor care pot r\u0103spunde responsabil la ele, dedic\u00e2nd timp pentru a c\u0103uta r\u0103spunsuri f\u0103r\u0103 prejudec\u0103\u021bi.<\/b><\/p>\n<blockquote><p>Dac\u0103 nu te confrun\u021bi cu o problem\u0103, nu ai nevoie de un nou instrument. Punct.<\/p><\/blockquote>\n<p><\/p>\n<h1>\u00centrebare 1: Ce probleme \u00eencerc s\u0103 rezolv?<\/h1>\n<p>\nDac\u0103 nu te confrun\u021bi cu o problem\u0103, nu ai nevoie de un nou instrument. At\u00e2t. Nu trebuie s\u0103 cau\u021bi o solu\u021bie \u0219i apoi s\u0103 inventezi o problem\u0103. Dac\u0103 nu te-ai lovit de o problem\u0103 pe care noua tehnologie nu o rezolv\u0103 semnificativ mai bine dec\u00e2t tehnologia ta existent\u0103, atunci nu este cazul s\u0103 discut\u0103m aici. Dac\u0103 te g\u00e2nde\u0219ti s\u0103 folose\u0219ti aceast\u0103 tehnologie pentru c\u0103 ai v\u0103zut c\u0103 altora le folose\u0219te, g\u00e2nde\u0219te-te la ce probleme se confrunt\u0103 \u0219i \u00eentreab\u0103-te dac\u0103 ai acelea\u0219i probleme. E u\u0219or s\u0103 adop\u021bi tehnologia pentru c\u0103 o folosesc al\u021bii, dificultatea const\u0103 \u00een a \u00een\u021belege dac\u0103 te confrun\u021bi cu acelea\u0219i provoc\u0103ri.<\/p>\n<h1>\u00centrebare 2: Ce pierd?<\/h1>\n<p>\nAceasta este, f\u0103r\u0103 \u00eendoial\u0103, o \u00eentrebare mai dificil\u0103, deoarece va trebui s\u0103 te aventurezi \u00een detalii \u0219i s\u0103 \u00een\u021belegi bine at\u00e2t tehnologia veche, c\u00e2t \u0219i pe cea nou\u0103. Uneori nu po\u021bi \u00een\u021belege cu adev\u0103rat noua tehnologie p\u00e2n\u0103 nu construie\u0219ti ceva cu ajutorul ei sau p\u00e2n\u0103 nu ai un coleg care are astfel de experien\u021b\u0103.<\/p>\n<p>Dac\u0103 nu ai nici asta, nici cealalt\u0103, are sens s\u0103 te g\u00e2nde\u0219ti la investi\u021biile minime posibile pentru a determina valoarea acestui instrument. \u0218i dac\u0103 vei face investi\u021bii, c\u00e2t de greu va fi s\u0103 anulezi decizia?<\/p>\n<h1>Oamenii stric\u0103 \u00eentotdeauna totul<\/h1>\n<p>\n\u00cencerc\u00e2nd s\u0103 r\u0103spunzi la aceste \u00eentreb\u0103ri c\u00e2t mai obiectiv, aminte\u0219te-\u021bi un lucru: va trebui s\u0103 te lup\u021bi cu natura uman\u0103. Exist\u0103 o serie de prejudec\u0103\u021bi cognitive care trebuie dep\u0103\u0219ite pentru a evalua eficient tehnologia. Iat\u0103 doar c\u00e2teva:<\/p>\n<ul>\n<li><b><noindex><a rel=\"nofollow\" href=\"https:\/\/en.wikipedia.org\/wiki\/Bandwagon_effect\">Efectul de conformare la majoritate<\/a><\/noindex><\/b> \u2014 toat\u0103 lumea \u0219tie despre el, dar este totu\u0219i greu de comb\u0103tut. Asigur\u0103-te doar c\u0103 tehnologia se potrive\u0219te cu nevoile tale reale.\n<\/li>\n<li><b><noindex><a rel=\"nofollow\" href=\"https:\/\/mindmodeling.org\/cogsci2015\/papers\/0177\/index.html\">Efectul de noutate<\/a><\/noindex><\/b> \u2014 mul\u021bi dezvoltatori au tendin\u021ba de a subestima tehnologiile cu care au lucrat mult timp \u0219i de a supraestima avantajele noii tehnologii. Nu doar programatorii, toat\u0103 lumea este predispus\u0103 la aceast\u0103 prejudecat\u0103 cognitiv\u0103.\n<\/li>\n<li><b><noindex><a rel=\"nofollow\" href=\"https:\/\/pigeon.psy.tufts.edu\/avc\/dittrich\/fepef.htm\">Efectul caracteristicilor pozitive<\/a><\/noindex> \u2014 avem tendin\u021ba de a vedea ceea ce exist\u0103 \u0219i de a ignora ceea ce lipse\u0219te. Acest lucru poate duce la haos \u00een combina\u021bie cu efectul de noutate, deoarece nu doar c\u0103 supraestimezi noua tehnologie, dar ignori \u0219i dezavantajele acesteia.<\/b>.<\/li>\n<\/ul>\n<p>\nEvaluarea obiectiv\u0103 nu este u\u0219or de realizat, dar \u00een\u021belegerea principalelor distorsiuni cognitive poate ajuta la luarea unor decizii mai ra\u021bionale.<\/p>\n<h1>Rezumat<\/h1>\n<p>\nC\u00e2nd apare o inova\u021bie, trebuie s\u0103 r\u0103spundem cu mare aten\u021bie la dou\u0103 \u00eentreb\u0103ri:<\/p>\n<ul>\n<li>Aceast\u0103 unealt\u0103 rezolv\u0103 o problem\u0103 real\u0103?\n<\/li>\n<li>\u00cen\u021belegem bine compromisurile?<\/li>\n<\/ul>\n<p>\nDac\u0103 nu pute\u021bi r\u0103spunde cu \u00eencredere la aceste dou\u0103 \u00eentreb\u0103ri, face\u021bi c\u00e2\u021biva pa\u0219i \u00eenapoi \u0219i g\u00e2ndi\u021bi-v\u0103.<\/p>\n<p>A fost MongoDB cu adev\u0103rat o alegere corect\u0103? Cu siguran\u021b\u0103 da; la fel ca \u00een majoritatea tehnologiilor inginere\u0219ti, depinde de o mul\u021bime de factori. Dintre cei care au r\u0103spuns la aceste dou\u0103 \u00eentreb\u0103ri, mul\u021bi au beneficiat de MongoDB \u0219i continu\u0103 s\u0103 o fac\u0103. Cei care nu au f\u0103cut-o, sper s\u0103 fi ob\u021binut o lec\u021bie valoroas\u0103 \u0219i nu prea dureroas\u0103 despre modul de func\u021bionare \u00een cadrul buclei de hype.<\/p>\n<p><noindex><a rel=\"nofollow\" name=\"1\"><\/a><\/noindex><\/p>\n<h1>Declinarea responsabilit\u0103\u021bii<\/h1>\n<p>\nVreau s\u0103 subliniez c\u0103 nu simt nici dragoste, nici ur\u0103 fa\u021b\u0103 de MongoDB. Pur \u0219i simplu nu am avut probleme pentru care MongoDB ar fi fost solu\u021bia optim\u0103. \u0218tiu c\u0103 10gen\/MongoDB Inc. a ac\u021bionat ini\u021bial foarte curajos, stabilind valori nesigure ca set\u0103ri implicite \u0219i promov\u00e2nd MongoDB peste tot (\u00een special la hackathoane) ca o solu\u021bie universal\u0103 pentru orice tip de date. Probabil c\u0103 a fost o decizie proast\u0103. Dar aceasta sus\u021bine abordarea descris\u0103 aici: aceste probleme puteau fi descoperite foarte rapid, chiar \u0219i printr-o evaluare superficial\u0103 a tehnologiei.<br \/>\n<br \/>Sursa: <a content=\"nofollow\" rel=\"nofollow\" href=\"https:\/\/habr.com\/ru\/post\/446180\/\">habr.com<\/a><\/p>","protected":false,"gt_translate_keys":[{"key":"rendered","format":"html"}]},"excerpt":{"rendered":"<p>\u041d\u0435\u0434\u0430\u0432\u043d\u043e \u044f \u0443\u0437\u043d\u0430\u043b, \u0447\u0442\u043e Red Hat \u0443\u0434\u0430\u043b\u044f\u0435\u0442 \u043f\u043e\u0434\u0434\u0435\u0440\u0436\u043a\u0443 MongoDB \u0438\u0437 Satellite (\u0433\u043e\u0432\u043e\u0440\u044f\u0442, \u0438\u0437-\u0437\u0430 \u0438\u0437\u043c\u0435\u043d\u0435\u043d\u0438\u0439 \u043b\u0438\u0446\u0435\u043d\u0437\u0438\u0438). \u042d\u0442\u043e \u0437\u0430\u0441\u0442\u0430\u0432\u0438\u043b\u043e \u043c\u0435\u043d\u044f \u0437\u0430\u0434\u0443\u043c\u0430\u0442\u044c\u0441\u044f, \u0447\u0442\u043e \u0432 \u043f\u043e\u0441\u043b\u0435\u0434\u043d\u0438\u0435 \u043d\u0435\u0441\u043a\u043e\u043b\u044c\u043a\u043e \u043b\u0435\u0442 \u044f \u0432\u0438\u0434\u0435\u043b \u043a\u0443\u0447\u0443 \u0441\u0442\u0430\u0442\u0435\u0439, \u043a\u0430\u043a \u0443\u0436\u0430\u0441\u043d\u0430 MongoDB \u0438 \u0447\u0442\u043e \u043d\u0438\u043a\u0442\u043e \u043d\u0438\u043a\u043e\u0433\u0434\u0430 \u043d\u0435 \u0434\u043e\u043b\u0436\u0435\u043d \u0435\u0451 \u0438\u0441\u043f\u043e\u043b\u044c\u0437\u043e\u0432\u0430\u0442\u044c. \u041d\u043e \u0437\u0430 \u044d\u0442\u043e \u0432\u0440\u0435\u043c\u044f MongoDB \u0441\u0442\u0430\u043b\u0430 \u0433\u043e\u0440\u0430\u0437\u0434\u043e \u0431\u043e\u043b\u0435\u0435 \u0437\u0440\u0435\u043b\u044b\u043c \u043f\u0440\u043e\u0434\u0443\u043a\u0442\u043e\u043c. \u0427\u0442\u043e \u0436\u0435 \u0441\u043b\u0443\u0447\u0438\u043b\u043e\u0441\u044c? \u0414\u0435\u0439\u0441\u0442\u0432\u0438\u0442\u0435\u043b\u044c\u043d\u043e \u043b\u0438 \u0432\u0441\u044f [&hellip;]<\/p>\n","protected":false,"gt_translate_keys":[{"key":"rendered","format":"html"}]},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[688],"tags":[],"class_list":["post-30666","post","type-post","status-publish","format-standard","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=\"\u041d\u0435\u0434\u0430\u0432\u043d\u043e \u044f \u0443\u0437\u043d\u0430\u043b, \u0447\u0442\u043e Red Hat \u0443\u0434\u0430\u043b\u044f\u0435\u0442 \u043f\u043e\u0434\u0434\u0435\u0440\u0436\u043a\u0443 MongoDB \u0438\u0437 Satellite (\u0433\u043e\u0432\u043e\u0440\u044f\u0442, \u0438\u0437-\u0437\u0430.\" \/>\n\t<meta name=\"robots\" content=\"max-image-preview:large\" \/>\n\t<meta name=\"author\" content=\"Yuri Gagarin\"\/>\n\t<link rel=\"canonical\" href=\"https:\/\/prohoster.info\/ro\/blog\/administrirovanie\/byla-la-mongodb-voobshhe-pravilnym-vyborom\" \/>\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\u0411\u044b\u043b\u0430 \u043b\u0430 MongoDB \u0432\u043e\u043e\u0431\u0449\u0435 \u043f\u0440\u0430\u0432\u0438\u043b\u044c\u043d\u044b\u043c \u0432\u044b\u0431\u043e\u0440\u043e\u043c? | ProHoster\" \/>\n\t\t<meta property=\"og:description\" content=\"\u041d\u0435\u0434\u0430\u0432\u043d\u043e \u044f \u0443\u0437\u043d\u0430\u043b, \u0447\u0442\u043e Red Hat \u0443\u0434\u0430\u043b\u044f\u0435\u0442 \u043f\u043e\u0434\u0434\u0435\u0440\u0436\u043a\u0443 MongoDB \u0438\u0437 Satellite (\u0433\u043e\u0432\u043e\u0440\u044f\u0442, \u0438\u0437-\u0437\u0430.\" \/>\n\t\t<meta property=\"og:url\" content=\"https:\/\/prohoster.info\/ro\/blog\/administrirovanie\/byla-la-mongodb-voobshhe-pravilnym-vyborom\" \/>\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=\"2019-10-31T18:36:48+00:00\" \/>\n\t\t<meta property=\"article:modified_time\" content=\"2019-10-31T18:36:48+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\udd47A fost MongoDB cu adev\u0103rat o alegere corect\u0103? | ProHoster","description":"Recent am aflat c\u0103 Red Hat elimin\u0103 suportul pentru MongoDB din Satellite (se spune din cauza.","canonical_url":"https:\/\/prohoster.info\/ro\/blog\/administrirovanie\/byla-la-mongodb-voobshhe-pravilnym-vyborom","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\u0411\u044b\u043b\u0430 \u043b\u0430 MongoDB \u0432\u043e\u043e\u0431\u0449\u0435 \u043f\u0440\u0430\u0432\u0438\u043b\u044c\u043d\u044b\u043c \u0432\u044b\u0431\u043e\u0440\u043e\u043c? | ProHoster","og:description":"\u041d\u0435\u0434\u0430\u0432\u043d\u043e \u044f \u0443\u0437\u043d\u0430\u043b, \u0447\u0442\u043e Red Hat \u0443\u0434\u0430\u043b\u044f\u0435\u0442 \u043f\u043e\u0434\u0434\u0435\u0440\u0436\u043a\u0443 MongoDB \u0438\u0437 Satellite (\u0433\u043e\u0432\u043e\u0440\u044f\u0442, \u0438\u0437-\u0437\u0430.","og:url":"https:\/\/prohoster.info\/ro\/blog\/administrirovanie\/byla-la-mongodb-voobshhe-pravilnym-vyborom","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":"2019-10-31T18:36:48+00:00","article:modified_time":"2019-10-31T18:36:48+00:00","article:publisher":"https:\/\/www.facebook.com\/prohoster","article:author":"https:\/\/www.facebook.com\/prohoster"},"aioseo_meta_data":{"post_id":"30666","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":"2026-01-21 02:22:20","breadcrumb_settings":null,"limit_modified_date":false,"reviewed_by":null,"ai":null,"created":"2021-03-01 03:31:23","updated":"2026-01-21 02:22:20","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\/30666","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=30666"}],"version-history":[{"count":0,"href":"https:\/\/prohoster.info\/ro\/wp-json\/wp\/v2\/posts\/30666\/revisions"}],"wp:attachment":[{"href":"https:\/\/prohoster.info\/ro\/wp-json\/wp\/v2\/media?parent=30666"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/prohoster.info\/ro\/wp-json\/wp\/v2\/categories?post=30666"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/prohoster.info\/ro\/wp-json\/wp\/v2\/tags?post=30666"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}