{"id":100516,"date":"2021-06-14T16:22:58","date_gmt":"2021-06-14T14:22:58","guid":{"rendered":"https:\/\/prohoster.info\/blog\/novosti-interneta\/vypusk-rqlite-6-0-raspredelyonnoj-otkazoustojchivoj-subd-na-osnove-sqlite"},"modified":"2021-06-14T16:22:58","modified_gmt":"2021-06-14T14:22:58","slug":"vypusk-rqlite-6-0-raspredelyonnoj-otkazoustojchivoj-subd-na-osnove-sqlite","status":"publish","type":"post","link":"https:\/\/prohoster.info\/sq\/blog\/novosti-interneta\/vypusk-rqlite-6-0-raspredelyonnoj-otkazoustojchivoj-subd-na-osnove-sqlite","title":{"rendered":"L\u00ebshimi rqlite 6.0, nj\u00eb DBMS i shp\u00ebrndar\u00eb me q\u00ebndrueshm\u00ebri t\u00eb lart\u00eb t\u00eb bazuar n\u00eb SQLite.","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"
\u00cbsht\u00eb prezentuar versioni i ri i DB t\u00eb shp\u00ebrndar\u00eb rqlite 6.0, i cili p\u00ebrdor SQLite si motor ruajtjeje dhe lejon organizimin e pun\u00ebs s\u00eb nj\u00eb klasteri me ruajtje t\u00eb sinkronizuara. Nj\u00eb nga karakteristikat e rqlite \u00ebsht\u00eb thjesht\u00ebsia e instalimit, ngjyr\u00ebs dhe mbajtjes s\u00eb nj\u00eb ruajtjeje t\u00eb shp\u00ebrndar\u00eb t\u00eb q\u00ebndrueshme, e ngjashme me etcd dhe Consul, por q\u00eb p\u00ebrdor modelin relacional p\u00ebr pun\u00ebn me t\u00eb dh\u00ebnat n\u00eb vend t\u00eb formateve \u00e7el\u00ebs\/vler\u00eb. Kodi i projektit \u00ebsht\u00eb shkruar n\u00eb gjuh\u00ebn Go dhe shp\u00ebrndahet n\u00ebn licenc\u00ebn MIT. <\/p>\n
P\u00ebr t\u00eb mbajtur t\u00eb gjitha nyjat n\u00eb nj\u00eb gjendje t\u00eb sinkronizuar p\u00ebrdoret algoritmi i arritjes s\u00eb konsensusit Raft. Rqlite p\u00ebrdor bibliotek\u00ebn origjinale SQLite dhe drejtuesin standard go-sqlite3, mbi t\u00eb cil\u00ebt ngrihet nj\u00eb nd\u00ebrfaqe q\u00eb trajton k\u00ebrkesat e klient\u00ebve, kryen replikim n\u00eb nyja t\u00eb tjera dhe ndjek arritjen e konsensusit p\u00ebr zgjedhjen e nyj\u00ebs lidere. <\/p>\n
Ndryshimet n\u00eb DB mund t\u00eb b\u00ebhen vet\u00ebm nga nyja q\u00eb \u00ebsht\u00eb zgjedhur si lidere, por lidhjet me operacionet e shkruar mund t\u00eb drejtohen edhe te nyjat e tjera t\u00eb klasterit, t\u00eb cilat do t\u00eb kthejn\u00eb adres\u00ebn e liderit p\u00ebr p\u00ebrs\u00ebritjen e k\u00ebrkes\u00ebs (n\u00eb versionin e ardhsh\u00ebm premtohet t\u00eb shtohet kalimi automatik i k\u00ebrkesave te lideri). Fokus i madh \u00ebsht\u00eb n\u00eb q\u00ebndrueshm\u00ebri, prandaj DB p\u00ebrshkall\u00ebzohet vet\u00ebm p\u00ebr operacionet e leximit, nd\u00ebrsa operacionet e shkruar jan\u00eb pika e ngusht\u00eb. \u00cbsht\u00eb e mundur t\u00eb startohet nj\u00eb klaster rqlite nga nj\u00eb nyje dhe nj\u00eb zgjidhje e till\u00eb mund t\u00eb p\u00ebrdoret p\u00ebr t\u00eb organizuar aksesin n\u00eb SQLite mbi HTTP pa ofruar q\u00ebndrueshm\u00ebri. <\/p>\n
T\u00eb dh\u00ebnat SQLite n\u00eb \u00e7do nyje ruhet jo n\u00eb skedar, por n\u00eb memorie. N\u00eb nivelin e shtres\u00ebs me realizimin e protokollit Raft mbahet nj\u00eb log i t\u00eb gjitha komandave SQLite, q\u00eb shkaktojn\u00eb ndryshimin e DB. Ky log p\u00ebrdoret gjat\u00eb replikimit (replikimi n\u00eb nivelin e riprodhimit t\u00eb k\u00ebrkesave n\u00eb nyja t\u00eb tjera), startimi i nj\u00eb nyjeje t\u00eb re apo rikuperimi pas humbjes s\u00eb lidhjes. P\u00ebr t\u00eb reduktuar madh\u00ebsin\u00eb e logut, aplikohet paketimi automatik, i cili aktivizohet pas nj\u00eb numri t\u00eb caktuar ndryshimesh dhe \u00e7on n\u00eb regjistrimin n\u00eb disk t\u00eb nj\u00eb snapshot-i, n\u00eb raport me t\u00eb cilin fillon t\u00eb mbahet nj\u00eb log i ri (gjendja e DB n\u00eb memorie \u00ebsht\u00eb identike me snapshot-in + logun e akumuluar t\u00eb ndryshimeve). <\/p>\n
Karakteristikat e rqlite: <\/p>\n
\n
Thjesht\u00ebsia e shp\u00ebrndarjes s\u00eb klasterit, pa nevoj\u00ebn e instalimit t\u00eb ve\u00e7ant\u00eb t\u00eb SQLite.\n
Mund\u00ebsia p\u00ebr t\u00eb marr\u00eb shpejt nj\u00eb depo SQL t\u00eb replikuar.\n
Gati p\u00ebr p\u00ebrdorim n\u00eb projekte t\u00eb pun\u00ebs (Production-grade).\n
Disponueshm\u00ebria e nj\u00eb API HTTP(S), q\u00eb lejon p\u00ebrdit\u00ebsimin e t\u00eb dh\u00ebnave n\u00eb m\u00ebnyr\u00eb grumbuj dhe p\u00ebrcaktimin e nyj\u00ebs lidere t\u00eb klasterit. Po ashtu, ofrohet nj\u00eb nd\u00ebrfaqe e komandave n\u00eb linj\u00eb dhe mund\u00ebsia e p\u00ebrdorimit t\u00eb librarive t\u00eb ndryshme t\u00eb klientit, t\u00eb krijuara p\u00ebr SQLite.\n
Disponibiliteti i sh\u00ebrbimit p\u00ebr t\u00eb identifikuar node t\u00eb tjera, duke lejuar krijimin dinamik t\u00eb klaster\u00ebve.\n
Mb\u00ebshtetje p\u00ebr enkriptimin e komunikimit t\u00eb t\u00eb dh\u00ebnave midis node-ve.\n
Mund\u00ebsia p\u00ebr t\u00eb konfigurur nivelin e verifikimit t\u00eb \u0430\u043a\u0442\u0443\u0430\u043bitetit dhe koherenc\u00ebs s\u00eb t\u00eb dh\u00ebnave gjat\u00eb leximit.\n
Mund\u00ebsi opsionale p\u00ebr t\u00eb lidhur node n\u00eb m\u00ebnyr\u00eb vet\u00ebm p\u00ebr lexim, t\u00eb cilat nuk marrin pjes\u00eb n\u00eb p\u00ebrcaktimin e konsensusit dhe p\u00ebrdoren p\u00ebr t\u00eb rritur shkall\u00ebzueshm\u00ebrin\u00eb e klasterit p\u00ebr operacionet e leximit.\n
Mb\u00ebshtetje p\u00ebr forma t\u00eb veta t\u00eb transaksioneve t\u00eb bazuara n\u00eb bashkimin e komandave n\u00eb nj\u00eb k\u00ebrkes\u00eb (transaksionet e bazuara n\u00eb BEGIN, COMMIT, ROLLBACK, SAVEPOINT dhe RELEASE nuk mb\u00ebshteten).\n
Mb\u00ebshtetje p\u00ebr krijimin e kopjeve rezerv\u00eb t\u00eb nxehta. <\/ul>\n
N\u00eb edicionin e ri jan\u00eb b\u00ebr\u00eb ndryshime t\u00eb r\u00ebnd\u00ebsishme arkitekturore, t\u00eb drejtuara n\u00eb p\u00ebrmir\u00ebsimin e besueshm\u00ebris\u00eb s\u00eb klasterit p\u00ebrmes p\u00ebrmir\u00ebsimit t\u00eb procesit t\u00eb drejtimit t\u00eb k\u00ebrkesave p\u00ebr lexim dhe shkruar n\u00eb nyja t\u00eb sakta t\u00eb klasterit. Nyjat rqlite tani mund t\u00eb shum\u00ebfishojn\u00eb mes tyre disa lidhje logjike, duke p\u00ebrdorur lidhje TCP t\u00eb vendosura midis nyjave p\u00ebrmes protokollit Raft. N\u00ebse nj\u00eb k\u00ebrkes\u00eb k\u00ebrkon autorizime nga nyja lidere, por d\u00ebrgohet te nj\u00eb nyj\u00eb sekondare, nyja sekondare mund t\u00eb p\u00ebrcaktoj\u00eb adres\u00ebn e liderit dhe t'ia d\u00ebrgoj\u00eb klientit, pa kryer llogaritin e konsensusit p\u00ebrmes protokollit Raft. <\/p>\n
Ky\u00e7i i ri gjithashtu mund\u00ebsoi heqjen e nj\u00eb komponenti t\u00eb ve\u00e7ant\u00eb p\u00ebr sinkronizimin e metadata dhe p\u00ebrjashtimin e trajtimit t\u00eb ve\u00e7ant\u00eb t\u00eb gjendjes Raft dhe metadata. Nyjet sekondare tani drejtojn\u00eb k\u00ebrkesat vet\u00ebm ndaj nyj\u00ebs kryesuese kur \u00ebsht\u00eb e nevojshme, n\u00eb momentet kur duhet t\u00eb m\u00ebsojn\u00eb adres\u00ebn e nyj\u00ebs kryesuese. N\u00eb API \u00ebsht\u00eb ofruar mund\u00ebsia p\u00ebr t\u00eb marr\u00eb informacion mbi gjendjen e nyjeve t\u00eb tjera n\u00eb klaster. N\u00eb nd\u00ebrfaqen e komand\u00ebs \u00ebsht\u00eb shtuar komanda \u00ab.sysdump\u00bb. \n Burimi: opennet.ru<\/a> <\/p>","protected":false,"gt_translate_keys":[{"key":"rendered","format":"html"}]},"excerpt":{"rendered":"