{"id":94520,"date":"2020-09-18T07:42:20","date_gmt":"2020-09-18T05:42:20","guid":{"rendered":"https:\/\/prohoster.info\/blog\/administrirovanie\/chto-pomoglo-nam-bystro-perestroitsya-na-onlajn-torgovlyu-v-novyh-usloviyah"},"modified":"2020-09-18T07:42:20","modified_gmt":"2020-09-18T05:42:20","slug":"chto-pomoglo-nam-bystro-perestroitsya-na-onlajn-torgovlyu-v-novyh-usloviyah","status":"publish","type":"post","link":"https:\/\/prohoster.info\/sq\/blog\/administrirovanie\/chto-pomoglo-nam-bystro-perestroitsya-na-onlajn-torgovlyu-v-novyh-usloviyah","title":{"rendered":"\u00c7far\u00eb na ndihmoi t\u00eb kalojm\u00eb shpejt n\u00eb tregtin\u00eb online n\u00eb kushte t\u00eb reja","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"

\ud83e\udd47Si t\u00eb arrish n\u00eb qiell dhe t\u00eb b\u00ebhesh pilot | ProHoster<\/p>\n

M\u00eb quajn\u00eb Mikhail, jam z\u00ebvend\u00ebsdrejtor p\u00ebr IT n\u00eb kompanin\u00eb \u00abSportmaster\u00bb. Dua t\u00eb ndaj nj\u00eb histori se si u p\u00ebrball\u00ebm me sfidat q\u00eb u shfaq\u00ebn gjat\u00eb pandemis\u00eb.<\/p>\n

N\u00eb dit\u00ebt e para t\u00eb realiteteve t\u00eb reja, formati tradicional i tregtis\u00eb offline t\u00eb \u00abSportmaster\u00bb u ndal, dhe ngarkesa n\u00eb kanalin ton\u00eb online, kryesisht n\u00eb lidhje me dor\u00ebzimin tek klient\u00ebt, u rrit dhjet\u00ebfish. Brenda disa jav\u00ebsh, ne transformuam nj\u00eb biznes t\u00eb madh offline n\u00eb online, duke e adaptuar sh\u00ebrbimin sipas nevojave t\u00eb klient\u00ebve tan\u00eb.<\/p>\n

N\u00eb thelb, ajo q\u00eb ishte nj\u00eb operacion dyt\u00ebsor p\u00ebr ne, u b\u00eb biznesi kryesor. R\u00ebnd\u00ebsia e \u00e7do porosie online u rrit ekstremisht. Duhej t\u00eb ruanim \u00e7do lek q\u00eb klient\u00ebt sjellin n\u00eb kompani. <\/p>\n

\"\u00c7far\u00eb<\/p>\n

P\u00ebr t'u p\u00ebrgjigjur shpejt k\u00ebrkesave t\u00eb klient\u00ebve, hap\u00ebm nj\u00eb qend\u00ebr kontakti shtes\u00eb n\u00eb zyr\u00ebn qendrore t\u00eb kompanis\u00eb, dhe tani mund t\u00eb pranojm\u00eb rreth 285,000 telefonata n\u00eb jav\u00eb. N\u00eb t\u00eb nj\u00ebjt\u00ebn koh\u00eb, ne kaluam 270 dyqane n\u00eb nj\u00eb format t\u00eb ri pa kontakt dhe t\u00eb sigurt, \u00e7ka lejoj klient\u00ebt t\u00eb merrnin porosit\u00eb, nd\u00ebrsa punonj\u00ebsit ruanin vendet e tyre t\u00eb pun\u00ebs.<\/p>\n

Gjat\u00eb procesit t\u00eb transformimit, kishim dy probleme kryesore. S\u00eb pari, ngarkesa n\u00eb burimet tona online u rrit ndjesh\u00ebm (se si u p\u00ebrball\u00ebm me k\u00ebt\u00eb, do ta tregoj\u00eb Sergey). S\u00eb dyti, fluksi i operacioneve t\u00eb rralla (para COVID) u rrit shum\u00ebfish, \u00e7ka k\u00ebrkonte nj\u00eb volum t\u00eb madh automatizimi t\u00eb shpejt\u00eb. P\u00ebr t\u00eb zgjidhur k\u00ebt\u00eb problem, na duhej t\u00eb rishp\u00ebrndanim burimet nga drejtimet q\u00eb ishin m\u00eb par\u00eb kryesore. Si u p\u00ebrball\u00ebm me k\u00ebt\u00eb \u2014 do ta tregoj\u00eb Elena.<\/p>\n

Shfryt\u00ebzimi i sh\u00ebrbimeve online<\/h2>\n

Kolesnikov Sergey, p\u00ebrgjigjet p\u00ebr shfryt\u00ebzimin e dyqanit online dhe mikrosh\u00ebrbimeve<\/em><\/p>\n

Q\u00eb nga momenti kur dyqanet tona me pakic\u00eb filluan t\u00eb mbyllen p\u00ebr vizitor\u00ebt, ne filluam t\u00eb regjistronim rritje t\u00eb treguesve si numri i p\u00ebrdoruesve, numri i porosive q\u00eb b\u00ebhen n\u00eb aplikacionin ton\u00eb, numri i k\u00ebrkesave p\u00ebr aplikacionet. <\/p>\n

\"\u00c7far\u00ebNumri i porosive nga 18 deri m\u00eb 31 mars\"\u00c7far\u00ebNumri i k\u00ebrkesave p\u00ebr mikrosh\u00ebrbimet e pagesave online\"\u00c7far\u00ebNumri i porosive t\u00eb realizuara n\u00eb faqen e internetit<\/p>\n

N\u00eb grafikun e par\u00eb shohim se rritja ishte p\u00ebraf\u00ebrsisht 14 her\u00eb, nd\u00ebrsa n\u00eb t\u00eb dytin \u2014 4 her\u00eb. T\u00eb dh\u00ebnat m\u00eb treguese p\u00ebr ne konsiderojm\u00eb koha e p\u00ebrgjigjes s\u00eb aplikacioneve tona. <\/p>\n

\"\u00c7far\u00eb<\/p>\n

N\u00eb k\u00ebt\u00eb grafik shohim p\u00ebrgjigjen e fronteve dhe aplikacioneve, dhe p\u00ebr ne e kemi p\u00ebrcaktuar se nuk kemi v\u00ebrejtur ndonj\u00eb rritje t\u00eb till\u00eb.<\/p>\n

S\u00eb pari, kjo lidhet me faktin se ne filluam pun\u00ebt p\u00ebrgatitore n\u00eb fund t\u00eb vitit 2019. Tani sh\u00ebrbimet tona jan\u00eb t\u00eb rezervuara, \u00ebsht\u00eb siguruar q\u00ebndrueshm\u00ebria n\u00eb nivelin e server\u00ebve fizik\u00eb, sistemeve t\u00eb virtualizimit, konteiner\u00ebve dhe sh\u00ebrbimeve n\u00eb to. Megjithat\u00eb, kapacitetet e burimeve tona serverike na lejojn\u00eb t\u00eb p\u00ebrballojm\u00eb ngarkesa t\u00eb shum\u00ebfishta.<\/p>\n

Instrumenti kryesor q\u00eb na ndihmoi n\u00eb t\u00eb gjith\u00eb k\u00ebt\u00eb histori ishte sistemi yn\u00eb i monitorimit. Megjithat\u00eb, edhe para pak koh\u00ebsh ne nuk kishim nj\u00eb sistem t\u00eb vet\u00ebm q\u00eb t\u00eb na ndihmonte t\u00eb mbledhim metrika n\u00eb t\u00eb gjitha nivelet, nga niveli i pajisjeve fizike dhe harduerit deri te metrikat e biznesit. <\/p>\n

Formalisht, monitorimi ekzistonte n\u00eb kompani, por zakonisht ishte i shp\u00ebrndar\u00eb dhe n\u00eb p\u00ebrgjegj\u00ebsin\u00eb e nj\u00ebsive t\u00eb ve\u00e7anta. Faktikisht, kur ndodhte ndonj\u00eb incident, ne pothuajse kurr\u00eb nuk kishim nj\u00eb kuptim t\u00eb p\u00ebrbashk\u00ebt se \u00e7far\u00eb kishte ndodhur, nuk kishte njoftim, dhe shpesh kjo \u00e7onte n\u00eb nj\u00eb k\u00ebrkim pa fund p\u00ebr lokalizimin dhe zgjidhjen e problemit.<\/p>\n

N\u00eb nj\u00eb moment, ne menduam dhe vendos\u00ebm se ishte e mjaftueshme \u2014 na nevojitej nj\u00eb sistem i vet\u00ebm q\u00eb t\u00eb shihnim t\u00eb gjith\u00eb pamjen plot\u00ebsisht. Teknologjit\u00eb kryesore n\u00eb stogun ton\u00eb p\u00ebrfshijn\u00eb Zabbix si qend\u00ebr p\u00ebr paralajm\u00ebrim dhe ruajtjen e metrikave, Prometheus p\u00ebr mbledhjen dhe ruajtjen e metrikave t\u00eb aplikacioneve, Stack ELK p\u00ebr regjistrimin dhe ruajtjen e t\u00eb dh\u00ebnave t\u00eb gjith\u00eb sistemit t\u00eb monitorimit, si dhe Grafana p\u00ebr vizualizimin, Swagger, Docker dhe gj\u00ebra t\u00eb tjera t\u00eb dobishme dhe t\u00eb njohura p\u00ebr ju.<\/p>\n

Gjithashtu, ne p\u00ebrdorim jo vet\u00ebm teknologjit\u00eb q\u00eb jan\u00eb t\u00eb disponueshme n\u00eb treg, por zhvillojm\u00eb edhe disa gj\u00ebra vet\u00eb. P\u00ebr shembull, ne krijojm\u00eb sh\u00ebrbime p\u00ebr integrimin e sistemeve me nj\u00ebra-tjetr\u00ebn, dometh\u00ebn\u00eb nj\u00eb API p\u00ebr mbledhjen e metrikave. Gjithashtu punojm\u00eb mbi sistemet tona t\u00eb monitorimit \u2014 n\u00eb nivelin e metrikave t\u00eb biznesit p\u00ebrdorim teste UI. Po ashtu, kemi nj\u00eb bot n\u00eb Telegram p\u00ebr njoftimin e ekipeve.<\/p>\n

Dhe ne gjithashtu p\u00ebrpiqemi ta b\u00ebjm\u00eb sistemin e monitorimit t\u00eb aksesuesh\u00ebm p\u00ebr ekipet, n\u00eb m\u00ebnyr\u00eb q\u00eb ato t\u00eb mund t\u00eb ruajn\u00eb metrikat e tyre dhe t\u00eb punojn\u00eb me to, p\u00ebrfshir\u00eb konfigurimin e paralajm\u00ebrimeve n\u00eb disa metrika t\u00eb ngushta q\u00eb nuk kan\u00eb nj\u00eb p\u00ebrdorim shum\u00eb t\u00eb gjer\u00eb. <\/p>\n

N\u00eb kuad\u00ebr t\u00eb gjith\u00eb sistemit, ne synojm\u00eb proaktivitetin dhe lokalizimin e shpejt\u00eb t\u00eb incidenteve. P\u00ebr m\u00eb tep\u00ebr, numri i mikrosistemeve dhe sistemeve tona ka p\u00ebsuar nj\u00eb rritje t\u00eb ndjeshme koh\u00ebt e fundit, duke shkaktuar edhe rritjen e numrit t\u00eb integrimeve. Si pjes\u00eb e optimizimit t\u00eb procesit t\u00eb diagnostikimit t\u00eb incidenteve n\u00eb nivelin e integrimit, ne jemi duke zhvilluar nj\u00eb sistem q\u00eb lejon kontrollin nd\u00ebr-sistemor dhe nxjerrjen e rezultateve, duke ndihmuar n\u00eb identifikimin e problemeve kryesore lidhur me importet dhe nd\u00ebrveprimin midis sistemeve. <\/p>\n

Natyrisht, kemi ende shum\u00eb p\u00ebr t\u00eb rritur dhe zhvilluar n\u00eb fush\u00ebn e operimit t\u00eb sistemeve, dhe jemi duke punuar intensivisht mbi k\u00ebt\u00eb. M\u00eb shum\u00eb rreth sistemit ton\u00eb t\u00eb monitorimit mund t\u00eb lexoni k\u00ebtu<\/u><\/a><\/noindex>. <\/p>\n

Testet teknike <\/h2>\n

Sergei Orlov, drejton qendr\u00ebn e kompetenc\u00ebs p\u00ebr zhvillimin e uebit dhe mobilit<\/em><\/p>\n

Q\u00eb nga fillimi i mbylljes s\u00eb dyqaneve fizike, na \u00ebsht\u00eb dashur t\u00eb p\u00ebrballim prova t\u00eb ndryshme nga pik\u00ebpamja e zhvillimit. N\u00eb radh\u00eb t\u00eb par\u00eb, nj\u00eb rritje e ngarkes\u00ebs si e till\u00eb. \u00cbsht\u00eb e qart\u00eb se n\u00ebse nuk merren masa p\u00ebrkat\u00ebse, me nj\u00eb ngarkes\u00eb t\u00eb madhe, sistemi mund t\u00eb shnd\u00ebrrohet n\u00eb nj\u00eb p\u00ebrvoj\u00eb t\u00eb pak\u00ebndshme, ose t\u00eb degradon n\u00eb performanc\u00eb, ose madje t\u00eb humbas kompleksi i funksionimit t\u00eb tij.<\/p>\n

Aspakti i dyt\u00eb, pak m\u00eb pak i duksh\u00ebm, \u00ebsht\u00eb se sistemi n\u00ebn ngarkes\u00eb t\u00eb lart\u00eb duhej t\u00eb ndryshohej shum\u00eb shpejt, duke u adaptuar p\u00ebr nd\u00ebrrimet e proceseve t\u00eb biznesit. Her\u00eb pas here disa her\u00eb n\u00eb dit\u00eb. N\u00eb shum\u00eb kompani ka nj\u00eb rregull q\u00eb gjat\u00eb aktiviteteve t\u00eb m\u00ebdha marketingu nuk duhet t\u00eb b\u00ebhen asnj\u00eb ndryshim n\u00eb sistem. Asnj\u00eb, le t\u00eb funksionoj\u00eb si\u00e7 \u00ebsht\u00eb.<\/p>\n

Por ne kishim, n\u00eb thelb, nj\u00eb t\u00eb premte t\u00eb pakufizuar t\u00eb zez\u00eb, gjat\u00eb s\u00eb cil\u00ebs duhej t\u00eb ndryshonim sistemin. Dhe \u00e7do gabim, problem, ose d\u00ebshtim n\u00eb sistem do t\u00eb ishte shum\u00eb i kushtuesh\u00ebm p\u00ebr biznesin.<\/p>\n

Duke kaluar p\u00ebrpara, mund t\u00eb them se arrit\u00ebm t\u00eb p\u00ebrballojm\u00eb k\u00ebto prova, t\u00eb gjitha sistemet p\u00ebrballuan ngarkes\u00ebn, u shkall\u00ebzuan leht\u00ebsisht, dhe nuk pat\u00ebm ndonj\u00eb d\u00ebshtim teknik t\u00eb r\u00ebnd\u00ebsish\u00ebm.<\/p>\n

Ekzistojn\u00eb kat\u00ebr shtylla mbi t\u00eb cilat mb\u00ebshtetet aft\u00ebsia e sistemit p\u00ebr t\u00eb duruar ngarkesa t\u00eb larta t\u00eb papritura. E para prej tyre \u00ebsht\u00eb monitorimi, p\u00ebr t\u00eb cilin keni lexuar m\u00eb lart. Pa nj\u00eb sistem monitorimi t\u00eb nd\u00ebrtuar, \u00ebsht\u00eb praktikisht e pamundur t\u00eb identifikohen ngushticat e sistemit. Nj\u00eb sistem i mir\u00eb monitorimi \u00ebsht\u00eb si nj\u00eb rrob\u00eb sht\u00ebpie, ai duhet t\u00eb jet\u00eb i rehatsh\u00ebm dhe i p\u00ebrshtatur p\u00ebr ju.<\/p>\n

Aspekti i dyt\u00eb \u00ebsht\u00eb testimi. Ne e marrim k\u00ebt\u00eb moment shum\u00eb seriozisht: shkruajm\u00eb teste klasike unitare, integruese, teste ngarkese dhe shum\u00eb t\u00eb tjera p\u00ebr \u00e7do sistem. Gjithashtu, ne shkruajm\u00eb nj\u00eb strategji testimi dhe p\u00ebrpiqemi ta \u00e7ojm\u00eb nivelin e testimit deri sa kontrolli manual t\u00eb mos na nevojitet m\u00eb.<\/p>\n

Shtylla e tret\u00eb \u00ebsht\u00eb CI\/CD Pipeline. Proceset e nd\u00ebrtimit, testimit dhe shp\u00ebrndarjes s\u00eb aplikacionit duhet t\u00eb jen\u00eb sa m\u00eb t\u00eb automatizuara, nuk duhet t\u00eb ket\u00eb nd\u00ebrhyrje manuale. Tematika CI\/CD Pipeline \u00ebsht\u00eb mjaft e thell\u00eb dhe un\u00eb do ta prek vet\u00ebm pak. Duhet p\u00ebrmendur vet\u00ebm se ne kemi nj\u00eb list\u00eb kontrolli CI\/CD Pipeline, me t\u00eb cil\u00ebn \u00e7do ekip produkti kalon p\u00ebrmes qendrave t\u00eb kompetenc\u00ebs.<\/p>\n

\"\u00c7far\u00ebJa lista e kontrollit<\/p>\n

K\u00ebshtu arrihen shum\u00eb q\u00ebllime. Kjo p\u00ebrfshin versionimin e API-s\u00eb, dhe feature toggle, p\u00ebr t\u00eb shmangur trenin e l\u00ebshimeve, si dhe arritjen e mbulimit t\u00eb testeve t\u00eb ndryshme n\u00eb nj\u00eb nivel t\u00eb till\u00eb sa t\u00eb automatizohet plot\u00ebsisht testimi, dhe shp\u00ebrndarjet t\u00eb jen\u00eb pa nd\u00ebrprerje etj.<\/p>\n

Shtylla e kat\u00ebrt jan\u00eb parimet arkitektonike dhe zgjidhjet teknike. Mund t\u00eb flasim shum\u00eb dhe gjat\u00eb p\u00ebr arkitektur\u00ebn, por d\u00ebshiroj t\u00eb theksoj disa parime mbi t\u00eb cilat d\u00ebshiroj t\u00eb p\u00ebrqendrohem.<\/p>\n

S\u00eb pari, duhet t\u00eb zgjidhni mjete t\u00eb specializuara p\u00ebr detyra t\u00eb caktuara. Po, duket e qart\u00eb, dhe \u00ebsht\u00eb e qart\u00eb se p\u00ebr t\u00eb goditur gozhd\u00eb duhen p\u00ebrdorur \u00e7eki\u00e7, nd\u00ebrsa p\u00ebr t\u00eb \u00e7montuar or\u00ebt duhen p\u00ebrdorur dh\u00ebmb\u00ebz t\u00eb ve\u00e7ant\u00eb. Por n\u00eb epok\u00ebn ton\u00eb, shum\u00eb mjete synojn\u00eb t\u00eb jen\u00eb universale, p\u00ebr t\u00eb p\u00ebrfshir\u00eb nj\u00eb segment maksimal p\u00ebrdoruesish: bazat e t\u00eb dh\u00ebnave, cach\u00ebt, framework-et dhe t\u00eb tjera. P\u00ebr shembull, n\u00ebse marrim baz\u00ebn e t\u00eb dh\u00ebnave MongoDB, ajo punon me transaksione multidokumentar, nd\u00ebrsa baza e t\u00eb dh\u00ebnave Oracle punon me json. Dhe duket se gjith\u00e7ka mund t\u00eb p\u00ebrdoret p\u00ebr \u00e7do gj\u00eb. Por n\u00ebse ne jemi p\u00ebr performanc\u00ebn, duhet t\u00eb kuptojm\u00eb qart\u00eb pik\u00ebt e forta dhe t\u00eb dob\u00ebta t\u00eb \u00e7do mjeti dhe t\u00eb p\u00ebrdorim ato q\u00eb na nevojiten p\u00ebr klas\u00ebn ton\u00eb t\u00eb detyrave. <\/p>\n

S\u00eb dyti, gjat\u00eb projektimit t\u00eb sistemeve, \u00e7do rritje e kompleksitetit duhet t\u00eb jet\u00eb e arsyetuar. Duhet t\u00eb mbajm\u00eb vazhdimisht k\u00ebt\u00eb n\u00eb mendje; parimi i low coupling \u00ebsht\u00eb i njohur p\u00ebr t\u00eb gjith\u00eb. Un\u00eb besoj se ai duhet t\u00eb zbatohet si n\u00eb nivelin e sh\u00ebrbimit konkret, ashtu edhe n\u00eb at\u00eb t\u00eb gjith\u00eb sistemit, dhe n\u00eb nivelin e peizazhit arkitektural. Gjithashtu, \u00ebsht\u00eb e r\u00ebnd\u00ebsishme t\u00eb kemi aft\u00ebsin\u00eb e shkall\u00ebzimit horizontal t\u00eb \u00e7do komponente t\u00eb sistemit n\u00eb rast ngarkese. N\u00ebse kemi k\u00ebt\u00eb aft\u00ebsi, shkall\u00ebzimi nuk do t\u00eb jet\u00eb asnj\u00ebher\u00eb nj\u00eb problem.<\/p>\n

N\u00ebse flasim p\u00ebr zgjidhje teknike, kemi k\u00ebrkuar nga ekipet produktore t\u00eb p\u00ebrgatisin nj\u00eb set t\u00eb ri rekomandimesh, idesh dhe zgjidhjesh q\u00eb ata kan\u00eb realizuar gjat\u00eb p\u00ebrgatitjes p\u00ebr val\u00ebn e ardhshme t\u00eb ngarkes\u00ebs.<\/p>\n

Cach\u00ebt<\/h2>\n

\u00cbsht\u00eb e nevojshme t\u00eb qasemi me vet\u00ebdije ndaj zgjedhjes s\u00eb cach\u00ebve lokale dhe t\u00eb shp\u00ebrndar\u00eb. Ndonj\u00ebher\u00eb ka kuptim t\u00eb p\u00ebrdoren t\u00eb dyja brenda nj\u00eb sistemi. P\u00ebr shembull, ne kemi sisteme, ku nj\u00eb pjes\u00eb e t\u00eb dh\u00ebnave n\u00eb thelb \u00ebsht\u00eb nj\u00eb cache vitrine, dometh\u00ebn\u00eb burimi i p\u00ebrdit\u00ebsimeve ndodhet jasht\u00eb vet\u00eb sistemit, dhe sistemi nuk e nd\u00ebrron at\u00eb t\u00eb dh\u00ebn\u00eb. P\u00ebr k\u00ebt\u00eb qasje ne p\u00ebrdorim Caffeine Cache lokale. <\/p>\n

Dhe ka t\u00eb dh\u00ebna q\u00eb sistemi i ndryshon aktivisht gjat\u00eb pun\u00ebs, dhe k\u00ebtu aplikojm\u00eb cache-n e shp\u00ebrndar\u00eb me Hazelcast. Kjo qasje na mund\u00ebson t\u00eb shfryt\u00ebzojm\u00eb avantazhet e cache-s\u00eb s\u00eb shp\u00ebrndar\u00eb atje ku ato v\u00ebrtet jan\u00eb t\u00eb nevojshme dhe t\u00eb minimizojm\u00eb shpenzimet sh\u00ebrbyese p\u00ebr qarkullimin e t\u00eb dh\u00ebnave n\u00eb klasterin Hazelcast atje ku mund t\u00eb ja dalim pa to. Kemi shkruar shum\u00eb p\u00ebr cache-t. k\u00ebtu <\/u><\/a><\/noindex>dhe k\u00ebtu<\/u><\/a><\/noindex>.<\/p>\n

P\u00ebr m\u00eb tep\u00ebr, kalimi n\u00eb serializuesin Kryo n\u00eb Hazelcast na ka dh\u00ebn\u00eb nj\u00eb rritje t\u00eb konsiderueshme. Nd\u00ebrsa kalimi nga ReplicatedMap n\u00eb IMap + Near Cache n\u00eb Hazelcast na ka lejuar t\u00eb minimizojm\u00eb l\u00ebvizjen e t\u00eb dh\u00ebnave n\u00ebp\u00ebr grupin. <\/p>\n

Nj\u00eb k\u00ebshill\u00eb e vog\u00ebl: kur b\u00ebni invalidimin masiv t\u00eb caches, nganj\u00ebher\u00eb aplikohet taktika e ngrohjes s\u00eb caches t\u00eb dyt\u00eb me kalimin e m\u00ebpassh\u00ebm n\u00eb t\u00eb. Mund t\u00eb duket se, me k\u00ebt\u00eb qasje, duhet t\u00eb kemi nj\u00eb konsum t\u00eb dyfisht\u00eb t\u00eb memories, por n\u00eb praktik\u00eb, n\u00eb ato sisteme ku kjo \u00ebsht\u00eb praktikuar, konsumimi i memories \u00ebsht\u00eb zvog\u00ebluar.<\/p>\n

Staku reaktiv<\/h2>\n

Ne p\u00ebrdorim stakun reaktiv n\u00eb nj\u00eb num\u00ebr t\u00eb konsideruesh\u00ebm sistemesh. N\u00eb rastin ton\u00eb, kjo \u00ebsht\u00eb Webflux ose Kotlin me korutina. Staku reaktiv \u00ebsht\u00eb ve\u00e7an\u00ebrisht efektiv aty ku presim operacione t\u00eb ngadalta t\u00eb input-output. P\u00ebr shembull, thirrje t\u00eb sh\u00ebrbimeve t\u00eb ngadalta, pun\u00eb me sistemin e skedar\u00ebve ose me sistemet e ruajtjes.<\/p>\n

Principi m\u00eb i r\u00ebnd\u00ebsish\u00ebm \u00ebsht\u00eb t\u00eb shmangni thirrjet bllokuese. N\u00ebn kapakun e framework-eve reaktive, ka nj\u00eb num\u00ebr t\u00eb vog\u00ebl sh\u00ebrbimesh aktive. N\u00ebse me kujdes lejojm\u00eb veten t\u00eb b\u00ebjm\u00eb nj\u00eb thirrje t\u00eb drejtp\u00ebrdrejt\u00eb bllokuese, si thirrjen e driver-it JDBC, sistemi thjesht do t\u00eb ndaloj\u00eb. <\/p>\n

D\u00ebshironi t\u00eb ktheni gabimet n\u00eb p\u00ebrjashtime runtime t\u00eb vetat. Procesi real i ekzekutimit t\u00eb programit kalon n\u00eb framework-et reaktive, ekzekutimi i kodit b\u00ebhet jo-lineare. Si pasoj\u00eb, \u00ebsht\u00eb shum\u00eb e v\u00ebshtir\u00eb t\u00eb diagnostikosh problemet p\u00ebrmes stack-trace-ve. Zgjidhja k\u00ebtu do t\u00eb ishte krijimi i p\u00ebrjashtimeve runtime objektive dhe t\u00eb qarta p\u00ebr \u00e7do gabim.<\/p>\n

Elasticsearch<\/h2>\n

Kur p\u00ebrdorni Elasticsearch, mos zgjidhni t\u00eb dh\u00ebna q\u00eb nuk p\u00ebrdoren. Ky \u00ebsht\u00eb nj\u00eb k\u00ebshill\u00eb shum\u00eb e thjesht\u00eb, por shpesh harrohet. N\u00ebse duhet t\u00eb zgjidhni m\u00eb shum\u00eb se 10,000 regjistrime nj\u00ebher\u00ebsh, duhet t\u00eb p\u00ebrdorni Scroll. N\u00ebse b\u00ebjm\u00eb nj\u00eb analogji, \u00ebsht\u00eb paksa si nj\u00eb kursori n\u00eb nj\u00eb baz\u00eb t\u00eb dh\u00ebnash relationale. <\/p>\n

Mos p\u00ebrdorni postfilter pa nevoj\u00eb. Me t\u00eb dh\u00ebna t\u00eb m\u00ebdha n\u00eb p\u00ebrzgjedhjen kryesore, kjo operacion ngarkon shum\u00eb baz\u00ebn e t\u00eb dh\u00ebnave. <\/p>\n

P\u00ebrdorni operacione bulk aty ku \u00ebsht\u00eb e aplikueshme.<\/p>\n

API<\/h2>\n

Kur projektoni API, vendosni k\u00ebrkesa p\u00ebr minimizimin e t\u00eb dh\u00ebnave t\u00eb transferuara. Kjo \u00ebsht\u00eb ve\u00e7an\u00ebrisht e r\u00ebnd\u00ebsishme n\u00eb nd\u00ebrlidhjen me frontin: pik\u00ebrisht n\u00eb k\u00ebt\u00eb pik\u00eb ne dalim p\u00ebrtej kanaleve t\u00eb Qendrave tona t\u00eb t\u00eb Dh\u00ebnave dhe tashm\u00eb punojm\u00eb n\u00eb kanalin q\u00eb na lidh me klientin. N\u00ebse ka probleme t\u00eb vogla atje, trafik i tep\u00ebrt e sjell nj\u00eb p\u00ebrvoj\u00eb negative p\u00ebr p\u00ebrdoruesin.<\/p>\n

Dhe, m\u00eb n\u00eb fund, mos e derdhni t\u00eb gjith\u00eb mas\u00ebn e t\u00eb dh\u00ebnave, qart\u00eb qasuni kontrat\u00ebs mes konsumator\u00ebve dhe furnizuesve.<\/p>\n

Transformimi organizativ<\/h2>\n

Eroshkina Elena, z\u00ebvend\u00ebs drejtoresh\u00eb p\u00ebr IT<\/em><\/p>\n

N\u00eb momentin kur ndodhi karantina dhe u shfaq nevoja p\u00ebr t\u00eb rritur ndjesh\u00ebm ritmin e zhvillimit online dhe p\u00ebr t\u00eb zbatuar sh\u00ebrbime omnichannel, ne ishim tashm\u00eb n\u00eb procesin e transformimit organizativ. <\/p>\n

Nj\u00eb pjes\u00eb e struktur\u00ebs ton\u00eb u kalua n\u00eb pun\u00ebn sipas parimeve dhe praktikave t\u00eb qasjes produktive. U formuan ekipe, t\u00eb cilat tani jan\u00eb p\u00ebrgjegj\u00ebse p\u00ebr funksionimin dhe zhvillimin e secilit produkt. Punonj\u00ebsit n\u00eb k\u00ebto ekipe jan\u00eb angazhuar n\u00eb 100% dhe e organizojn\u00eb pun\u00ebn e tyre sipas Scrum ose Kanban, n\u00eb var\u00ebsi t\u00eb asaj q\u00eb \u00ebsht\u00eb m\u00eb e preferueshme p\u00ebr ta, rregullojn\u00eb linj\u00ebn e shtrirjes, zbatojn\u00eb praktikat teknike, praktikat e sigurimit t\u00eb cil\u00ebsis\u00eb dhe shum\u00eb t\u00eb tjera.<\/p>\n

Me fat, pjesa m\u00eb e madhe e atyre ekipeve produktive ndodhej pik\u00ebrisht n\u00eb fush\u00ebn e sh\u00ebrbimeve online dhe omnichannel. Kjo na leht\u00ebsoi t\u00eb kalonim n\u00eb m\u00ebnyr\u00eb t\u00eb shpejt\u00eb (seriozisht, p\u00ebr dy dit\u00eb) n\u00eb nj\u00eb mod nga distanca pa humbur efikasitetin. Procesi i vendosur na lejoi t\u00eb adaptoheshim shpejt n\u00eb kushtet e reja t\u00eb pun\u00ebs dhe t\u00eb mbanim nj\u00eb rit\u00ebm t\u00eb mjaftuesh\u00ebm t\u00eb dor\u00ebzimit t\u00eb funksionaliteteve t\u00eb reja.<\/p>\n

P\u00ebr m\u00eb tep\u00ebr, na u shfaq nevoja t\u00eb forcojm\u00eb ato ekipe q\u00eb ndodhen n\u00eb frontierin e biznesit online. N\u00eb at\u00eb moment, u b\u00eb e qart\u00eb se mund ta b\u00ebnim k\u00ebt\u00eb vet\u00ebm p\u00ebrmes burimeve t\u00eb brendshme. Dhe rreth 50 njer\u00ebz brenda dy jav\u00ebsh ndryshuan fush\u00ebn, ku kishin punuar m\u00eb par\u00eb dhe u integruan n\u00eb pun\u00ebn mbi nj\u00eb produkt t\u00eb ri p\u00ebr ta. <\/p>\n

P\u00ebr k\u00ebt\u00eb, nuk nevojiteshin ndonj\u00eb p\u00ebrpjekje t\u00eb ve\u00e7anta menaxheriale, sepse p\u00ebrve\u00e7 organizimit t\u00eb procesit ton\u00eb, me p\u00ebrmir\u00ebsimin teknik t\u00eb produktit, me praktikat e sigurimit t\u00eb cil\u00ebsis\u00eb, ne i m\u00ebsojm\u00eb ekipet tona p\u00ebr autodashuri \u2014 t\u00eb menaxhojn\u00eb procesin e tyre t\u00eb prodhimit pa angazhuar burime administrative.<\/p>\n

Ne menaxhuar burimin, arrit\u00ebm ta fokusohemi pik\u00ebrisht aty ku ishte e nevojshme n\u00eb at\u00eb moment, - n\u00eb koordinimin me biznesin: \u00c7far\u00eb \u00ebsht\u00eb aktualisht e r\u00ebnd\u00ebsishme p\u00ebr klientin ton\u00eb, cila funksionalitet duhet t\u00eb implementohet si prioritet, \u00e7far\u00eb duhet t\u00eb b\u00ebjm\u00eb p\u00ebr t\u00eb rritur kapacitetin ton\u00eb p\u00ebr d\u00ebrges\u00eb dhe p\u00ebrpunim t\u00eb porosive. T\u00eb gjitha k\u00ebto dhe nj\u00eb model i qart\u00eb role na lejuan q\u00eb n\u00eb k\u00ebt\u00eb periudh\u00eb t\u00eb mundohemi t\u00eb ngarkojm\u00eb proceset tona prodhuese me at\u00eb q\u00eb \u00ebsht\u00eb v\u00ebrtet e r\u00ebnd\u00ebsishme dhe e nevojshme. <\/p>\n

E qart\u00eb, n\u00eb pun\u00ebn e larg\u00ebt dhe me ritmin e lart\u00eb t\u00eb ndryshimeve, kur pjes\u00ebmarrja e secilit ndikon n\u00eb treguesit e biznesit, nuk mund t\u00eb mb\u00ebshtetemi vet\u00ebm n\u00eb ndjenjat e brendshme si \"A po na shkon mir\u00eb? Po, mendoj se po\". K\u00ebrkohen matjet objektive t\u00eb procesit prodhues. K\u00ebto i kemi, jan\u00eb t\u00eb-accessueshme p\u00ebr secilin k\u00ebtu q\u00eb interesohet p\u00ebr matjet e ekipeve produktive. Para gjith\u00e7kaje, p\u00ebr ekipin e vet, biznesin, koleg\u00ebt dhe menaxhmentin.<\/p>\n

\u00c7do dy jav\u00eb, me \u00e7do ekip mbahet nj\u00eb status, ku p\u00ebr 10 minuta analizohen metrikat, identifikohen ngushticat e procesit prodhues dhe propozohet nj\u00eb zgjidhje e p\u00ebrbashk\u00ebt: \u00e7far\u00eb mund t\u00eb b\u00ebhet p\u00ebr t\u00eb eliminuar k\u00ebto ngushtica. K\u00ebtu mund t\u00eb k\u00ebrkoni ndihm\u00eb nga drejtuesit n\u00eb rast se ndonj\u00eb problem i identifikuar \u00ebsht\u00eb jasht\u00eb ndikimit t\u00eb ekipeve, ose nga ekspert\u00ebt e koleg\u00ebve q\u00eb, ndoshta, kan\u00eb hasur n\u00eb nj\u00eb problem t\u00eb ngjash\u00ebm.<\/p>\n

Megjithat\u00eb, ne kuptojm\u00eb se p\u00ebr t\u00eb p\u00ebrshpejtuar n\u00eb m\u00ebnyr\u00eb t\u00eb konsiderueshme (kjo \u00ebsht\u00eb pik\u00ebrisht q\u00ebllimi yn\u00eb), na duhen ende shum\u00eb gj\u00ebra p\u00ebr t\u00eb m\u00ebsuar dhe implementuar n\u00eb pun\u00ebn ton\u00eb t\u00eb p\u00ebrditshme. Pik\u00ebrisht tani, ne vazhdojm\u00eb t\u00eb zgjerim qasjen produktive n\u00eb ekipe t\u00eb tjera dhe n\u00eb produkte t\u00eb reja. P\u00ebr k\u00ebt\u00eb, na duhej t\u00eb zot\u00ebronim nj\u00eb format t\u00eb ri p\u00ebr ne, shkoll\u00ebn online t\u00eb metodolog\u00ebve.<\/p>\n

Metodolog\u00ebt, njer\u00ebzit q\u00eb ndihmojn\u00eb ekipet t\u00eb nd\u00ebrtkojn\u00eb procesin, t\u00eb p\u00ebrmir\u00ebsojn\u00eb komunikimin, t\u00eb rrisin efikasitetin e pun\u00ebs, n\u00eb thelb jan\u00eb agjent\u00eb t\u00eb ndryshimit. Tani, absolvimet tona t\u00eb grupit t\u00eb par\u00eb po punojn\u00eb me ekipet dhe u ndihmojn\u00eb atyre t\u00eb b\u00ebhen t\u00eb suksessh\u00ebm. <\/p>\n

Mendoj se situata e krijuar na ofron mund\u00ebsi dhe perspektiva q\u00eb ndoshta nuk i kemi kuptuar plot\u00ebsisht ende. Por ajo p\u00ebrvoj\u00eb dhe praktik\u00eb q\u00eb po marrim tani e konfirmon se kemi zgjedhur rrug\u00ebn e duhur t\u00eb zhvillimit, nuk do t'i humbasim k\u00ebto mund\u00ebsi t\u00eb reja n\u00eb t\u00eb ardhmen dhe do t\u00eb jemi po aq efektiv n\u00eb p\u00ebrgjigjen ndaj sfidave q\u00eb do t\u00eb paraqiten p\u00ebr \"Sportmasterin\".<\/p>\n

P\u00ebrfundimet<\/h3>\n

Gjat\u00eb k\u00ebtij kohe t\u00eb v\u00ebshtir\u00eb, ne formuluam parimet kryesore mbi t\u00eb cilat mb\u00ebshtetet zhvillimi i softuerit, t\u00eb cilat mendoj se do t\u00eb vlejn\u00eb p\u00ebr \u00e7do kompani q\u00eb merret me k\u00ebt\u00eb.<\/p>\n

Njer\u00ebzit<\/strong>Kjo \u00ebsht\u00eb ajo mbi t\u00eb cil\u00ebn bazohet gjith\u00e7ka. Punonj\u00ebsit duhet t\u00eb g\u00ebzojn\u00eb nga puna, t\u00eb kuptojn\u00eb q\u00ebllimet e kompanis\u00eb dhe q\u00ebllimet e produkteve me t\u00eb cilat merret. Dhe, natyrisht, t\u00eb ken\u00eb mund\u00ebsi p\u00ebr zhvillim profesional. <\/p>\n

Shkenca<\/strong>\u00cbsht\u00eb e nevojshme q\u00eb kompania t\u00eb afroj\u00eb nj\u00eb qasje t\u00eb zhvilluar ndaj pun\u00ebs me stiv\u00ebn e saj teknologjike dhe t\u00eb rris\u00eb kompetencat atje ku \u00ebsht\u00eb realisht e nevojshme. Ting\u00ebllon shum\u00eb e thjesht\u00eb dhe e dukshme. Dhe shpesh neglizhohet.<\/p>\n

Proceset<\/strong>\u00cbsht\u00eb e r\u00ebnd\u00ebsishme t\u00eb organizohet si\u00e7 duhet puna e ekipeve t\u00eb produkteve dhe qendrave t\u00eb kompetenc\u00ebs, p\u00ebr t\u00eb nd\u00ebrtuar bashk\u00ebpunimin me biznesin, n\u00eb m\u00ebnyr\u00eb q\u00eb t\u00eb punosh me t\u00eb si nj\u00eb partner.<\/p>\n<\/p>\n

N\u00eb p\u00ebrgjith\u00ebsi, k\u00ebshtu e kaluam. Teza kryesore e koh\u00ebrave moderne u konfirmua edhe nj\u00eb her\u00eb, duke b\u00ebr\u00eb nj\u00eb goditje t\u00eb fort\u00eb n\u00eb ball\u00eb.<\/p>\n

Edhe n\u00ebse je nj\u00eb biznes i madh offline me shum\u00eb dyqane dhe shum\u00eb qytete, zhvillo online t\u00ebndin. Nuk \u00ebsht\u00eb thjesht nj\u00eb kanal shtes\u00eb shitjeje apo nj\u00eb aplikacion i bukur, p\u00ebrmes t\u00eb cilit gjithashtu mund t\u00eb blihen gj\u00ebra (edhe sepse konkurent\u00ebt kan\u00eb gjithashtu nj\u00eb aplikacion t\u00eb bukur). Nuk \u00ebsht\u00eb nj\u00eb rezerv\u00eb p\u00ebr \u00e7do rast, q\u00eb do t\u00eb ndihmoj\u00eb p\u00ebr t\u00eb kaluar stuhin\u00eb.<\/p>\n

\u00cbsht\u00eb nj\u00eb nevoj\u00eb e v\u00ebrtet\u00eb. P\u00ebr t\u00eb cil\u00ebn duhet t\u00eb jen\u00eb t\u00eb gatsh\u00ebm jo vet\u00ebm kapacitetet teknike dhe infrastruktura, por edhe njer\u00ebzit dhe proceset. Sepse, blerja e shpejt\u00eb e memories, hap\u00ebsir\u00ebs, shp\u00ebrndarja e instancave t\u00eb reja dhe t\u00eb tjera mund t\u00eb b\u00ebhet p\u00ebr disa or\u00eb. Por njer\u00ebzit dhe proceset duhet t\u00eb p\u00ebrgatiten paraprakisht p\u00ebr nj\u00eb gj\u00eb t\u00eb till\u00eb.<\/p>\n<\/p>\n

Burimi: habr.com<\/a> <\/p>","protected":false,"gt_translate_keys":[{"key":"rendered","format":"html"}]},"excerpt":{"rendered":"

\u041f\u0440\u0438\u0432\u0435\u0442! \u041c\u0435\u043d\u044f \u0437\u043e\u0432\u0443\u0442 \u041c\u0438\u0445\u0430\u0438\u043b, \u044f \u0437\u0430\u043c\u0435\u0441\u0442\u0438\u0442\u0435\u043b\u044c \u0434\u0438\u0440\u0435\u043a\u0442\u043e\u0440\u0430 \u043f\u043e \u0418\u0422 \u0432 \u043a\u043e\u043c\u043f\u0430\u043d\u0438\u0438 \u00ab\u0421\u043f\u043e\u0440\u0442\u043c\u0430\u0441\u0442\u0435\u0440\u00bb. \u042f \u0445\u043e\u0447\u0443 \u043f\u043e\u0434\u0435\u043b\u0438\u0442\u044c\u0441\u044f \u0438\u0441\u0442\u043e\u0440\u0438\u0435\u0439 \u043e \u0442\u043e\u043c, \u043a\u0430\u043a \u043c\u044b \u0441\u043f\u0440\u0430\u0432\u0438\u043b\u0438\u0441\u044c \u0441 \u0442\u0440\u0443\u0434\u043d\u043e\u0441\u0442\u044f\u043c\u0438, \u0432\u043e\u0437\u043d\u0438\u043a\u0448\u0438\u043c\u0438 \u0432\u043e \u0432\u0440\u0435\u043c\u044f \u043f\u0430\u043d\u0434\u0435\u043c\u0438\u0438. \u0412 \u043f\u0435\u0440\u0432\u044b\u0435 \u0434\u043d\u0438 \u043d\u043e\u0432\u044b\u0445 \u0440\u0435\u0430\u043b\u0438\u0439 \u043f\u0440\u0438\u0432\u044b\u0447\u043d\u044b\u0439 \u0444\u043e\u0440\u043c\u0430\u0442 \u043e\u0444\u043b\u0430\u0439\u043d-\u0442\u043e\u0440\u0433\u043e\u0432\u043b\u0438 \u00ab\u0421\u043f\u043e\u0440\u0442\u043c\u0430\u0441\u0442\u0435\u0440\u0430\u00bb \u0437\u0430\u043c\u0435\u0440, \u0438 \u043d\u0430\u0433\u0440\u0443\u0437\u043a\u0430 \u043d\u0430 \u043d\u0430\u0448 \u043e\u043d\u043b\u0430\u0439\u043d-\u043a\u0430\u043d\u0430\u043b, \u0432 \u043f\u0435\u0440\u0432\u0443\u044e \u043e\u0447\u0435\u0440\u0435\u0434\u044c \u0432 \u0447\u0430\u0441\u0442\u0438 \u0434\u043e\u0441\u0442\u0430\u0432\u043a\u0438 \u043d\u0430 \u0430\u0434\u0440\u0435\u0441 \u043a\u043b\u0438\u0435\u043d\u0442\u0443, \u0432\u043e\u0437\u0440\u043e\u0441\u043b\u0430 \u0432 10 \u0440\u0430\u0437. […]<\/p>\n","protected":false,"gt_translate_keys":[{"key":"rendered","format":"html"}]},"author":1,"featured_media":94521,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[688],"tags":[],"class_list":["post-94520","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\udd47 \u00c7far\u00eb na ndihmoi t\u00eb ridizajnojm\u00eb shpejt n\u00eb tregtin\u00eb online n\u00eb kushte t\u00eb reja | ProHoster","description":"P\u00ebrsh\u00ebndetje! M\u00eb quajn\u00eb Mihail, un\u00eb jam z\u00ebvend\u00ebsdrejtor i IT-s\u00eb n\u00eb kompanin\u00eb \"Sportmaster\".","canonical_url":"https:\/\/prohoster.info\/sq\/blog\/administrirovanie\/chto-pomoglo-nam-bystro-perestroitsya-na-onlajn-torgovlyu-v-novyh-usloviyah","robots":"max-image-preview:large","keywords":"","webmasterTools":{"miscellaneous":""},"schema":null,"og:locale":"sq_AL","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\u0427\u0442\u043e \u043f\u043e\u043c\u043e\u0433\u043b\u043e \u043d\u0430\u043c \u0431\u044b\u0441\u0442\u0440\u043e \u043f\u0435\u0440\u0435\u0441\u0442\u0440\u043e\u0438\u0442\u044c\u0441\u044f \u043d\u0430 \u043e\u043d\u043b\u0430\u0439\u043d-\u0442\u043e\u0440\u0433\u043e\u0432\u043b\u044e \u0432 \u043d\u043e\u0432\u044b\u0445 \u0443\u0441\u043b\u043e\u0432\u0438\u044f\u0445 | ProHoster","og:description":"\u041f\u0440\u0438\u0432\u0435\u0442!\u041c\u0435\u043d\u044f \u0437\u043e\u0432\u0443\u0442 \u041c\u0438\u0445\u0430\u0438\u043b, \u044f \u0437\u0430\u043c\u0435\u0441\u0442\u0438\u0442\u0435\u043b\u044c \u0434\u0438\u0440\u0435\u043a\u0442\u043e\u0440\u0430 \u043f\u043e \u0418\u0422 \u0432 \u043a\u043e\u043c\u043f\u0430\u043d\u0438\u0438 \u00ab\u0421\u043f\u043e\u0440\u0442\u043c\u0430\u0441\u0442\u0435\u0440\u00bb.","og:url":"https:\/\/prohoster.info\/sq\/blog\/administrirovanie\/chto-pomoglo-nam-bystro-perestroitsya-na-onlajn-torgovlyu-v-novyh-usloviyah","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-09-18T05:42:20+00:00","article:modified_time":"2020-09-18T05:42:20+00:00","article:publisher":"https:\/\/www.facebook.com\/prohoster","article:author":"https:\/\/www.facebook.com\/prohoster"},"aioseo_meta_data":{"post_id":"94520","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 11:25:23","updated":"2022-09-29 04:36:15","focus_keyword":null,"additional_keywords":null,"truseo_locale":null},"gt_translate_keys":[{"key":"link","format":"url"}],"_links":{"self":[{"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/posts\/94520","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/comments?post=94520"}],"version-history":[{"count":0,"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/posts\/94520\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/media\/94521"}],"wp:attachment":[{"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/media?parent=94520"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/categories?post=94520"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/tags?post=94520"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}