{"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 kushtet e reja","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"

P\u00ebrsh\u00ebndetje!<\/p>\n

M\u00eb quajn\u00eb Mikhail, jam z\u00ebvend\u00ebsdrejtor i IT n\u00eb kompanin\u00eb \u00abSportmaster\u00bb. Dua t\u00eb ndaj nj\u00eb histori mbi m\u00ebnyr\u00ebn se si p\u00ebrballuam 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 i zakonsh\u00ebm offline i tregtis\u00eb \u00abSportmaster\u00bb u ngrit, dhe ngarkesa n\u00eb kanalin ton\u00eb online, kryesisht n\u00eb aspektin e dor\u00ebzimeve n\u00eb adres\u00ebn e klient\u00ebve, u rrit 10 her\u00eb. Brenda disa jav\u00ebsh, ne transformuam nj\u00eb biznes offline t\u00eb madh n\u00eb online, duke e adaptuar sh\u00ebrbimin sipas nevojave t\u00eb klient\u00ebve tan\u00eb.<\/p>\n

N\u00eb t\u00ebr\u00ebsi, ajo q\u00eb n\u00eb thelb ishte operacioni yn\u00eb dyt\u00ebsor, u b\u00eb biznesi yn\u00eb kryesor. R\u00ebnd\u00ebsia e \u00e7do porosie online u rrit ekstremisht. Duhej t\u00eb ruanim \u00e7do lek q\u00eb klienti sillte n\u00eb kompani. <\/p>\n

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

P\u00ebr t\u00eb reaguar shpejt ndaj k\u00ebrkesave t\u00eb klient\u00ebve, hap\u00ebm nj\u00eb qend\u00ebr t\u00eb re kontakti n\u00eb selin\u00eb e 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 u mund\u00ebsoi klient\u00ebve t\u00eb merrnin porosit\u00eb, nd\u00ebrsa punonj\u00ebsit ruajt\u00ebn vendet e tyre t\u00eb pun\u00ebs.<\/p>\n

Gjat\u00eb procesit t\u00eb transformimit, has\u00ebm dy probleme kryesore. S\u00eb pari, ngarkesa n\u00eb burimet tona online u rrit ndjesh\u00ebm (se si e kemi trajtuar k\u00ebt\u00eb, do t\u00eb tregoj\u00eb Sergey). S\u00eb dyti, fluksi i operacioneve t\u00eb rralla (para COVID) u rrit shum\u00eb, gj\u00eb q\u00eb k\u00ebrkoi nj\u00eb volum t\u00eb madh automatizimi t\u00eb shpejt\u00eb. P\u00ebr t\u00eb zgjidhur k\u00ebt\u00eb problem, na duhej t\u00eb transferonim shpejt burimet nga sektor\u00ebt q\u00eb ishin m\u00eb par\u00eb kryesor\u00eb. Si ia dol\u00ebm, do t\u00eb tregoj\u00eb Elena.<\/p>\n

Funksionimi i sh\u00ebrbimeve online<\/h2>\n

Kolesnikov Sergey, p\u00ebrgjigjet p\u00ebr funksionimin 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, filluam t\u00eb regjistronim rritje t\u00eb metrikeve t\u00eb tilla si numri i p\u00ebrdoruesve, numri i porosive t\u00eb b\u00ebra 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 b\u00ebra n\u00eb faqe<\/p>\n

N\u00eb grafikun e par\u00eb shohim se rritja ishte af\u00ebrsisht 14 her\u00eb, nd\u00ebrsa n\u00eb t\u00eb dytin \u2013 4 her\u00eb. Metrika m\u00eb treguese n\u00eb k\u00ebt\u00eb rast \u00ebsht\u00eb koha e p\u00ebrgjigjes s\u00eb aplikacioneve tona. <\/p>\n

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

N\u00eb k\u00ebt\u00eb grafik shohim p\u00ebrgjigjet e fronteve dhe aplikacioneve, dhe p\u00ebr vete e kemi p\u00ebrcaktuar se nuk kemi v\u00ebn\u00eb re ndonj\u00eb rritje t\u00eb dukshme.<\/p>\n

Kjo \u00ebsht\u00eb kryesisht e lidhur me faktin se filluam punimet 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, docker\u00ebve dhe sh\u00ebrbimeve brenda tyre. Megjithat\u00eb, kapacitetet e burimeve tona serverike na lejojn\u00eb t\u00eb p\u00ebrballojm\u00eb ngarkesa shum\u00ebfish.<\/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, sapo nuk kishim nj\u00eb sistem t\u00eb unifikuar i cili do t\u00eb lejonte mbledhjen e metrikave n\u00eb t\u00eb gjitha nivelet, nga niveli i pajisjeve fizike dhe hardware-it deri te metrikat e biznesit. <\/p>\n

Formalisht, monitorimi n\u00eb kompanin\u00eb ton\u00eb ka ekzistuar, por zakonisht ai ka qen\u00eb i shp\u00ebrndar\u00eb dhe n\u00ebn p\u00ebrgjegj\u00ebsin\u00eb e departamenteve t\u00eb ve\u00e7anta. N\u00eb fakt, kur ndodhte ndonj\u00eb incident, ne kurr\u00eb nuk kishim nj\u00eb kuptim t\u00eb p\u00ebrbashk\u00ebt p\u00ebr at\u00eb q\u00eb kishte ndodhur, nuk kishte informacion dhe shpeshher\u00eb kjo \u00e7onte n\u00eb nj\u00eb cik\u00ebl t\u00eb pafund k\u00ebrkimesh dhe lokalizimi t\u00eb problemit p\u00ebr zgjidhje t\u00eb m\u00ebvonshme.<\/p>\n

N\u00eb ndonj\u00eb moment ne menduam dhe vendos\u00ebm q\u00eb mjaft \u00ebsht\u00eb mjaft \u2014 na nevojitet nj\u00eb sistem i vet\u00ebm p\u00ebr t\u00eb par\u00eb t\u00eb gjith\u00eb pamjen n\u00eb t\u00ebr\u00ebsi. Teknologjit\u00eb kryesore q\u00eb p\u00ebrfshihen n\u00eb stack-un ton\u00eb jan\u00eb Zabbix si qendra e alarmimit dhe ruajtjes s\u00eb metrikeve, Prometheus p\u00ebr mbledhjen dhe ruajtjen e metrikeve t\u00eb aplikacioneve, Stack ELK p\u00ebr regjistrimin dhe ruajtjen e t\u00eb dh\u00ebnave t\u00eb sistemit t\u00eb monitorimit, si dhe Grafana p\u00ebr vizualizim, Swagger, Docker dhe gj\u00ebra t\u00eb tjera t\u00eb dobishme e t\u00eb njohura p\u00ebr ju.<\/p>\n

Ne vet\u00ebm q\u00eb p\u00ebrdorim teknologjit\u00eb e disponueshme n\u00eb treg, por gjithashtu zhvillojm\u00eb disa gj\u00ebra vet\u00eb. P\u00ebr shembull, ne krijojm\u00eb sh\u00ebrbime p\u00ebr integrimin e sistemeve me nj\u00ebri-tjetrin, pra nj\u00eb API p\u00ebr mbledhjen e statistikave. Po ashtu punojm\u00eb p\u00ebr sistemet tona t\u00eb monitorimit \u2014 n\u00eb nivelin e metrikeve t\u00eb biznesit p\u00ebrdorim teste UI. Gjithashtu, kemi nj\u00eb bot n\u00eb Telegram p\u00ebr njoftimin e ekipeve.<\/p>\n

N\u00eb t\u00eb nj\u00ebjt\u00ebn koh\u00eb, ne p\u00ebrpiqemi ta b\u00ebjm\u00eb sistemin e monitorimit t\u00eb arritsh\u00ebm p\u00ebr ekipet, n\u00eb m\u00ebnyr\u00eb q\u00eb ato t\u00eb mund t\u00eb ruajn\u00eb vet\u00eb statistikat e tyre dhe t\u00eb punojn\u00eb me to, p\u00ebrfshir\u00eb konfigurimin e alarmeve n\u00eb disa metrika t\u00eb ngushta, q\u00eb kan\u00eb nj\u00eb p\u00ebrdorim jo shum\u00eb t\u00eb gjer\u00eb. <\/p>\n

N\u00eb t\u00eb gjith\u00eb sistemin, ne synojm\u00eb proaktivitetin dhe lokalizimin sa m\u00eb t\u00eb shpejt\u00eb t\u00eb incidenteve. P\u00ebr m\u00eb tep\u00ebr, numri i mikrosh\u00ebrbimeve dhe sistemeve tona \u00ebsht\u00eb rritur ndjesh\u00ebm koh\u00ebt e fundit, dhe po ashtu po rritet numri i integrimeve. N\u00eb kuad\u00ebr t\u00eb optimizimit t\u00eb procesit t\u00eb diagnostikimit t\u00eb incidenteve n\u00eb nivelin e integrimit, ne po zhvillojm\u00eb nj\u00eb sistem q\u00eb lejon kryerjen e kontrollimeve nd\u00ebr-sistem dhe nxjerrjen e rezultateve, duke mund\u00ebsuar gjetjen e problemeve kryesore q\u00eb lidhen me importet dhe nd\u00ebrveprimin e sistemeve me nj\u00ebra-tjetr\u00ebn. <\/p>\n

Natyrisht, ne kemi ende p\u00ebr t\u00eb ecur p\u00ebrpara dhe zhvilluar n\u00eb aspektin e operimit t\u00eb sistemeve, dhe ne po punojm\u00eb aktivisht mbi k\u00ebt\u00eb. M\u00eb shum\u00eb n\u00eb lidhje me sistemin ton\u00eb t\u00eb monitorimit mund t\u00eb lexoni k\u00ebtu<\/u><\/a><\/noindex>. <\/p>\n

Operacionet teknike <\/h2>\n

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

Q\u00eb nga fillimi i mbylljes s\u00eb dyqaneve fizike, na \u00ebsht\u00eb dashur t\u00eb p\u00ebrballemi me nj\u00eb s\u00ebr\u00eb sfidash nga k\u00ebndv\u00ebshtrimi i zhvillimit. E para dhe kryesore \u00ebsht\u00eb rritja e ngarkes\u00ebs. E qart\u00eb \u00ebsht\u00eb se, n\u00ebse nuk merren masat p\u00ebrkat\u00ebse, sistemi mund t\u00eb shnd\u00ebrrohet me nj\u00eb goditje t\u00eb trishtuar n\u00eb nj\u00eb kungull, ose t\u00eb degradoj\u00eb ndjesh\u00ebm n\u00eb performanc\u00eb, ose t\u00eb humbas\u00eb plot\u00ebsisht funksionalitetin e tij.<\/p>\n

Aspekti 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 p\u00ebrshtatur me ndryshimet e proceseve t\u00eb biznesit. Ndonj\u00ebher\u00eb 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 duhen b\u00ebr\u00eb ndryshime n\u00eb sistem. Asnj\u00eb ndryshim, le t\u00eb funksionoj\u00eb, pasi funksionon.<\/p>\n

Dhe ne, n\u00eb thelb, kishim nj\u00eb e premte t\u00eb zez\u00eb t\u00eb pafund, n\u00eb t\u00eb cil\u00ebn duhej t\u00eb ndryshonim sistemin. \u00c7do gabim, problem, apo d\u00ebshtim n\u00eb sistem do t\u00eb kishte kosto shum\u00eb t\u00eb larta p\u00ebr biznesin.<\/p>\n

Duke p\u00ebrpara, dua t\u00eb them se arrit\u00ebm t\u00eb p\u00ebrballojm\u00eb k\u00ebto sfida, t\u00eb gjitha sistemet p\u00ebrballuan ngarkes\u00ebn, u shkall\u00ebzuan leht\u00ebsisht dhe nuk pat\u00ebm ndonj\u00eb prishje teknike globale.<\/p>\n

Ekzistojn\u00eb kat\u00ebr shtylla q\u00eb mbajn\u00eb aft\u00ebsin\u00eb e sistemit p\u00ebr t\u00eb p\u00ebrballuar ngarkesa t\u00eb larta. E para \u00ebsht\u00eb monitorimi, p\u00ebr t\u00eb cilin keni lexuar m\u00eb sip\u00ebr. Pa nj\u00eb sistem monitorimi t\u00eb nd\u00ebrtuar, \u00ebsht\u00eb praktikisht e pamundur t\u00eb identifikosh lidhjet e dob\u00ebta t\u00eb sistemit. Nj\u00eb sistem i mir\u00eb monitorimi \u00ebsht\u00eb si veshjet sht\u00ebpiake, 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 \u00e7\u00ebshtje shum\u00eb seriozisht: shkruajm\u00eb teste klasike nj\u00ebsish, integruese, teste ngarkese dhe shum\u00eb t\u00eb tjera p\u00ebr \u00e7do sistem. Gjithashtu, ne shkruajm\u00eb nj\u00eb strategji testimi dhe mundohemi ta \u00e7ojm\u00eb nivelin e testimit n\u00eb nj\u00eb pik\u00eb q\u00eb verifikimet manuale t\u00eb mos na nevojiten m\u00eb.<\/p>\n

Kiti i tret\u00eb \u00ebsht\u00eb CI\/CD Pipeline. Proceset e nd\u00ebrtimit, testimit dhe distribuimit t\u00eb aplikacionit duhet t\u00eb jen\u00eb sa m\u00eb automatizuar, pa nd\u00ebrhyrje manuale. Tema e CI\/CD Pipeline \u00ebsht\u00eb mjaft e thell\u00eb, dhe un\u00eb do ta p\u00ebrmend vet\u00ebm n\u00eb p\u00ebrgjith\u00ebsi. \u00cbsht\u00eb e r\u00ebnd\u00ebsishme t\u00eb p\u00ebrmendet se ne kemi nj\u00eb list\u00eb kontrolli p\u00ebr CI\/CD Pipeline, sipas s\u00eb cil\u00ebs kalon \u00e7do ekip produkti me ndihm\u00ebn e qendrave t\u00eb kompetenc\u00ebs.<\/p>\n

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

K\u00ebshtu arrihen shum\u00eb q\u00ebllime. Kjo \u00ebsht\u00eb versionimi i API-ve, dhe nd\u00ebrrimi i ve\u00e7orive p\u00ebr t\u00eb shmangur daljen e grumbulluar t\u00eb l\u00ebshimeve, si dhe arritja e mbulimit t\u00eb testeve n\u00eb nj\u00eb nivel t\u00eb till\u00eb q\u00eb testimi t\u00eb jet\u00eb t\u00ebr\u00ebsisht automatizuar, deployt t\u00eb jen\u00eb pa probleme dhe shum\u00eb t\u00eb tjera.<\/p>\n

Kiti i kat\u00ebrt jan\u00eb parimet arkitekturore dhe zgjidhjet teknike. Mund t\u00eb flas\u00ebsh shum\u00eb dhe gjat\u00eb p\u00ebr arkitektur\u00ebn, por dua t\u00eb theksoj disa principe mbi t\u00eb cilat do doja t\u00eb fokusohem.<\/p>\n

S\u00eb pari, duhet t\u00eb zgjedhim mjete t\u00eb specializuara p\u00ebr detyra t\u00eb ve\u00e7anta. Po, duket e qart\u00eb, dhe \u00ebsht\u00eb e kuptueshme q\u00eb duhet t\u00eb godisni thikat me nj\u00eb hammer, nd\u00ebrsa p\u00ebr t\u00eb shkuar or\u00ebt dore, duhet t\u00eb p\u00ebrdorni screwdriver t\u00eb ve\u00e7ant\u00eb. Por n\u00eb epok\u00ebn ton\u00eb, shum\u00eb mjete k\u00ebrkojn\u00eb t\u00eb b\u00ebhen universale, p\u00ebr t\u00eb kapur sa m\u00eb shum\u00eb p\u00ebrdorues: databaza, cache-t, framework-et dhe t\u00eb tjera. P\u00ebr shembull, n\u00ebse e marrim databaz\u00ebn MongoDB, ajo punon me transaksione multi-dokumentar, nd\u00ebrsa databaza Oracle punon me json. Dhe duke e par\u00eb k\u00ebshtu, duket se gjith\u00e7ka mund t\u00eb p\u00ebrdoret p\u00ebr gjith\u00e7ka. Por n\u00ebse ne mbrojm\u00eb performanc\u00ebn, duhet t\u00eb kuptojm\u00eb qart\u00eb pikat e forta dhe t\u00eb dob\u00ebta t\u00eb secilit mjet dhe t\u00eb p\u00ebrdorim ato q\u00eb na nevojiten p\u00ebr klas\u00ebn ton\u00eb t\u00eb detyrave. <\/p>\n

N\u00eb t\u00eb dyt\u00ebn, kur projektimi i sistemeve, \u00e7do rritje e kompleksitetit duhet t\u00eb justifikohet. Duhet ta kemi vazhdimisht n\u00eb mendje k\u00ebt\u00eb, parimi i low coupling \u00ebsht\u00eb i njohur p\u00ebr t\u00eb gjith\u00eb. Un\u00eb mendoj se duhet ta aplikojm\u00eb si n\u00eb nivelin e sh\u00ebrbimit t\u00eb ve\u00e7ant\u00eb, ashtu edhe n\u00eb nivelin e gjith\u00eb sistemit, dhe n\u00eb nivelin e peizazhit arkitektonik. Po ashtu, aft\u00ebsia p\u00ebr t\u00eb shkall\u00ebzuar horizontalisht \u00e7do komponent t\u00eb sistemit n\u00eb rast ngarkese \u00ebsht\u00eb e r\u00ebnd\u00ebsishme. N\u00ebse e kemi k\u00ebt\u00eb aft\u00ebsi, shkall\u00ebzimi nuk do t\u00eb jet\u00eb aspak i v\u00ebshtir\u00eb.<\/p>\n

N\u00eb lidhje me zgjidhjet teknike, i k\u00ebrkuam ekipeve produktore t\u00eb p\u00ebrgatitin nj\u00eb grup t\u00eb ri rekomandimesh, ideve dhe zgjidhjeve q\u00eb ata kan\u00eb realizuar gjat\u00eb p\u00ebrgatitjes p\u00ebr val\u00ebn e re t\u00eb ngarkes\u00ebs.<\/p>\n

Keshat<\/h2>\n

\u00cbsht\u00eb e nevojshme t\u00eb qasemi me kujdes n\u00eb zgjedhjen e keshave lokale dhe t\u00eb shp\u00ebrndara. Ndonj\u00ebher\u00eb ka kuptim t\u00eb p\u00ebrdorim t\u00eb dyja brenda nj\u00eb sistemi. P\u00ebr shembull, ne kemi sisteme n\u00eb t\u00eb cilat nj\u00eb pjes\u00eb e t\u00eb dh\u00ebnave n\u00eb thelb \u00ebsht\u00eb kesh i vitrin\u00ebs, dometh\u00ebn\u00eb burimi i p\u00ebrdit\u00ebsimeve ndodhet pas vet\u00eb sistemit, dhe k\u00ebto sisteme nuk i ndryshojn\u00eb k\u00ebto t\u00eb dh\u00ebna. P\u00ebr k\u00ebt\u00eb qasje ne p\u00ebrdorim Caffeine Cache lokal. <\/p>\n

Ka jan\u00eb t\u00eb dh\u00ebna q\u00eb sistemi i ndryshon aktivisht n\u00eb procesin e pun\u00ebs, dhe k\u00ebtu ne zbatojm\u00eb nj\u00eb cache t\u00eb shp\u00ebrndar\u00eb me Hazelcast. Ky qasje na lejon t\u00eb p\u00ebrdorim p\u00ebrfitimet e cache-it t\u00eb shp\u00ebrndar\u00eb aty ku ato v\u00ebrtet nevojiten dhe t\u00eb minimizojm\u00eb shpenzimet e sh\u00ebrbimeve p\u00ebr qarkullimin e t\u00eb dh\u00ebnave n\u00eb klasterin Hazelcast aty ku mund t\u00eb shmangim k\u00ebt\u00eb. Ne kemi shkruar shum\u00eb p\u00ebr cache-t. k\u00ebtu <\/u><\/a><\/noindex>dhe k\u00ebtu<\/u><\/a><\/noindex>.<\/p>\n

P\u00ebrve\u00e7 k\u00ebsaj, nd\u00ebrrimi i serializatorit n\u00eb Kryo n\u00eb Hazelcast na dha nj\u00eb rritje t\u00eb konsiderueshme. Kalimi nga ReplicatedMap n\u00eb IMap + Near Cache n\u00eb Hazelcast na ndihmoi t\u00eb minimizojm\u00eb l\u00ebvizjen e t\u00eb dh\u00ebnave n\u00ebp\u00ebr klaster. <\/p>\n

Nj\u00eb k\u00ebshill\u00eb e vog\u00ebl: kur b\u00ebhet nj\u00eb invalizim masiv i cache-it, ndonj\u00ebher\u00eb taktika e ngrohjes s\u00eb cache-it t\u00eb dyt\u00eb me kalimin e m\u00ebpassh\u00ebm n\u00eb t\u00eb \u00ebsht\u00eb e aplikueshme. Mund t\u00eb duket se me k\u00ebt\u00eb qasje do t\u00eb kemi dyfishim t\u00eb konsumit t\u00eb memories, por n\u00eb praktik\u00eb, n\u00eb sistemet ku di\u00e7ka e till\u00eb \u00ebsht\u00eb praktikuar, konsumimi i memories \u00ebsht\u00eb ulur.<\/p>\n

Stoku reaktiv<\/h2>\n

Ne p\u00ebrdorim nj\u00eb grusht reaktiv n\u00eb nj\u00eb num\u00ebr t\u00eb konsideruesh\u00ebm sistemesh. N\u00eb rastin ton\u00eb, kjo \u00ebsht\u00eb Webflux ose Kotlin me coroutine. Grushti reaktiv funksionon ve\u00e7an\u00ebrisht mir\u00eb aty ku presim operacione t\u00eb ngadalta input-output. P\u00ebr shembuj, thirrjet ndaj sh\u00ebrbimeve t\u00eb ngadalta, punimi me sistemin e skedar\u00ebve ose sistemet e ruajtjes.<\/p>\n

Principi m\u00eb i r\u00ebnd\u00ebsish\u00ebm \u00ebsht\u00eb t\u00eb shmangni thirrjet bllokuese. N\u00ebn kapak, kuptimi i kornizave reaktive funksionon me nj\u00eb num\u00ebr t\u00eb vog\u00ebl t\u00eb rasteve sh\u00ebrbimi aktive. N\u00ebse me kujdes lejojm\u00eb nj\u00eb thirrje t\u00eb drejtp\u00ebrdrejt\u00eb bllokuese, si p.sh. thirrja e drejtuesit JDBC, sistemi do t\u00eb ndaloj\u00eb thjesht. <\/p>\n

P\u00ebrpiquni t\u00eb ktheni gabimet n\u00eb p\u00ebrjashtime runtime t\u00eb duhura. Rrjedha reale e ekzekutimit t\u00eb programit kalon n\u00eb kornizat reaktive, ekzekutimi i kodit b\u00ebhet jo-linear. Si pasoj\u00eb, \u00ebsht\u00eb shum\u00eb e v\u00ebshtir\u00eb t\u00eb diagnostikoni problemet p\u00ebrmes stack trace. Nj\u00eb zgjidhje k\u00ebtu do t\u00eb ishte krijimi i p\u00ebrjashtimeve runtime objektive t\u00eb qarta p\u00ebr \u00e7do gabim.<\/p>\n

Elasticsearch<\/h2>\n

Kur p\u00ebrdorni Elasticsearch, mos zgjidhni t\u00eb dh\u00ebna t\u00eb pap\u00ebrdorura. Kjo \u00ebsht\u00eb nj\u00eb k\u00ebshill\u00eb shum\u00eb e thjesht\u00eb, por shpesh harrohet. N\u00ebse nevojitet t\u00eb zgjidhen m\u00eb shum\u00eb se 10 mij\u00eb t\u00eb dh\u00ebna nj\u00ebher\u00ebsh, duhet t\u00eb p\u00ebrdorni Scroll. N\u00ebse b\u00ebni nj\u00eb analogji, kjo \u00ebsht\u00eb paksi si nj\u00eb kursor n\u00eb nj\u00eb baz\u00eb t\u00eb dh\u00ebnash relationale. <\/p>\n

Mos p\u00ebrdorni postfilter pa nevoj\u00eb. Kur keni t\u00eb dh\u00ebna t\u00eb m\u00ebdha n\u00eb p\u00ebrzgjedhjen kryesore, kjo operacion ngarkon shum\u00eb databaz\u00ebn. <\/p>\n

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

API<\/h2>\n

Kur projektoni API, parashikoni k\u00ebrkesat p\u00ebr minimizimin e t\u00eb dh\u00ebnave t\u00eb transmetuara. Kjo \u00ebsht\u00eb ve\u00e7an\u00ebrisht e r\u00ebnd\u00ebsishme n\u00eb lidhje me frontin: pik\u00ebrisht n\u00eb k\u00ebt\u00eb pik\u00eb, ne dalim jasht\u00eb kanaleve t\u00eb Qendrave tona t\u00eb T\u00eb Dh\u00ebnave dhe punojm\u00eb n\u00eb kanalin q\u00eb na lidh me klientin. N\u00ebse ka probleme m\u00eb t\u00eb vogla n\u00eb t\u00eb, nj\u00eb trafik shum\u00eb i lart\u00eb shkakton nj\u00eb p\u00ebrvoj\u00eb negative p\u00ebr p\u00ebrdoruesin.<\/p>\n

Dhe, p\u00ebrfundimisht, mos e nxirrni gjith\u00eb grumbullin e t\u00eb dh\u00ebnave, qasuni me kujdes kontrat\u00ebs midis konsumator\u00ebve dhe ofruesve.<\/p>\n

Transformimi organizativ<\/h2>\n

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

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

Nj\u00eb pjes\u00eb e struktur\u00ebs son\u00eb u kalua n\u00eb pun\u00ebn sipas parimeve dhe praktikave t\u00eb qasjes produktive. U formuan skuadra q\u00eb tani jan\u00eb p\u00ebrgjegj\u00ebse p\u00ebr funksionimin dhe zhvillimin e \u00e7do produkti. Punonj\u00ebsit n\u00eb k\u00ebto skuadra jan\u00eb angazhuar 100% dhe ndjekin metodologjit\u00eb Scrum ose Kanban, n\u00eb var\u00ebsi t\u00eb asaj q\u00eb preferojn\u00eb, duke krijuar linjat e shp\u00ebrndarjes, duke implementuar praktikat teknike, praktikat e sigurimit t\u00eb cil\u00ebsis\u00eb dhe shum\u00eb t\u00eb tjera.<\/p>\n

K\u00ebshtu ndodhi q\u00eb shumica e k\u00ebtyre skuadrave produktive ishin pik\u00ebrisht n\u00eb fush\u00ebn e sh\u00ebrbimeve online dhe omnikanale. Kjo na leht\u00ebsoi t\u00eb kalonim n\u00eb nj\u00eb mod t\u00eb pun\u00ebs nga distanca n\u00eb nj\u00eb koh\u00eb shum\u00eb t\u00eb shkurt\u00ebr (seriozisht, p\u00ebr dy dit\u00eb) pa humbur efikasitetin. Procesi i vendosur na leht\u00ebsoi t\u00eb adaptoheshim shpejt n\u00eb kushtet e reja t\u00eb pun\u00ebs dhe t\u00eb mbajm\u00eb nj\u00eb rit\u00ebm t\u00eb lart\u00eb t\u00eb d\u00ebrgimit t\u00eb funksionaliteteve t\u00eb reja.<\/p>\n

P\u00ebrve\u00e7 k\u00ebsaj, na u krijua nevoja p\u00ebr t\u00eb forcuar ekipet q\u00eb jan\u00eb n\u00eb vij\u00ebn e par\u00eb t\u00eb biznesit online. N\u00eb at\u00eb moment u kuptua se mund ta b\u00ebnim k\u00ebt\u00eb vet\u00ebm duke p\u00ebrdorur burimet tona t\u00eb brendshme. Rreth 50 persona brenda dy jav\u00ebsh ndryshuan fush\u00ebn ku kishin punuar m\u00eb par\u00eb dhe u inkuadruan n\u00eb pun\u00ebn mbi nj\u00eb produkt t\u00eb ri p\u00ebr ta. <\/p>\n

P\u00ebr k\u00ebt\u00eb nuk kishte nevoj\u00eb p\u00ebr ndonj\u00eb p\u00ebrpjekje t\u00eb ve\u00e7ant\u00eb menaxheriale, sepse p\u00ebrve\u00e7 organizimit t\u00eb procesit ton\u00eb, p\u00ebr p\u00ebrmir\u00ebsimin teknik t\u00eb produktit, dhe p\u00ebr praktik\u00ebn e sigurimit t\u00eb cil\u00ebsis\u00eb, ne i m\u00ebsojm\u00eb ekipet tona t\u00eb vet\u00eborganizohen \u2014 t\u00eb menaxhojn\u00eb procesin e tyre prodhues pa angazhimin e burimeve administrative.<\/p>\n

Ne e thjesht nj\u00eb burim menaxhimi q\u00eb arrit\u00ebm ta fokusojm\u00eb aty ku ishte e nevojshme n\u00eb at\u00eb moment, \u2013 n\u00eb koordinimin me biznesin: \u00c7far\u00eb \u00ebsht\u00eb e r\u00ebnd\u00ebsishme tani p\u00ebr klientin ton\u00eb, cila funksionalitet duhet t\u00eb realizohet si prioritet, \u00e7far\u00eb duhet t\u00eb b\u00ebjm\u00eb p\u00ebr t\u00eb rritur kapacitetin ton\u00eb t\u00eb shp\u00ebrndarjes dhe p\u00ebrpunimit t\u00eb porosive. T\u00eb gjitha k\u00ebto, s\u00eb bashku me nj\u00eb model t\u00eb qart\u00eb rolesh, na ndihmuan t\u00eb ngarkonim proceset tona prodhuese me at\u00eb q\u00eb v\u00ebrtet \u00ebsht\u00eb e r\u00ebnd\u00ebsishme dhe e nevojshme gjat\u00eb k\u00ebsaj periudhe. <\/p>\n

Sigurisht, n\u00eb pun\u00ebn e larg\u00ebt dhe me nj\u00eb rit\u00ebm t\u00eb lart\u00eb ndryshimesh, kur rezultate e biznesit varen nga pjes\u00ebmarrja e secilit, nuk mund t\u00eb mb\u00ebshtetesh vet\u00ebm te ndjenjat e brendshme si \"A po shkon mir\u00eb? Po, duket mir\u00eb.\" Nevojiten metrika objektive t\u00eb procesit prodhues. K\u00ebto i kemi, dhe jan\u00eb t\u00eb disponueshme p\u00ebr \u00e7do person q\u00eb intereson p\u00ebr metrikat e ekipeve t\u00eb produkteve. Para s\u00eb gjithash, p\u00ebr ekipin vet\u00eb, biznesin, koleg\u00ebt dhe menaxhimin.<\/p>\n

\u00c7do dy jav\u00eb, realizohet nj\u00eb status me \u00e7do ekip, ku p\u00ebr 10 minuta analizohen metrikat, identifikohen lidhjet e dob\u00ebta t\u00eb procesit prodhues dhe krijohet nj\u00eb zgjidhje e p\u00ebrbashk\u00ebt: \u00e7far\u00eb mund t\u00eb b\u00ebjm\u00eb p\u00ebr t\u00eb eliminuar k\u00ebto lidhje t\u00eb dob\u00ebta. K\u00ebtu, gjithashtu, mund t\u00eb k\u00ebrkoni ndihm\u00eb nga drejtuesit n\u00ebse ndonj\u00eb problem i identifikuar \u00ebsht\u00eb jasht\u00eb zon\u00ebs s\u00eb ndikimit t\u00eb ekipeve, ose nga ekspertiz\u00ebn e koleg\u00ebve q\u00eb ndoshta kan\u00eb hasur n\u00eb probleme t\u00eb ngjashme.<\/p>\n

Megjithat\u00eb, ne kuptojm\u00eb se p\u00ebr nj\u00eb rritje t\u00eb konsiderueshme (ky \u00ebsht\u00eb q\u00ebllimi yn\u00eb) na nevojitet ende t\u00eb m\u00ebsojm\u00eb shum\u00eb dhe t\u00eb implementojm\u00eb n\u00eb pun\u00ebn e p\u00ebrditshme. Aktualisht, ne po 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 m\u00ebsonim nj\u00eb format t\u00eb ri p\u00ebr ne t\u00eb shkoll\u00ebs online t\u00eb metodolog\u00ebve.<\/p>\n

Metodolog\u00ebt, njer\u00ebzit q\u00eb ndihmojn\u00eb ekipet t\u00eb nd\u00ebrtojn\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, absolvent\u00ebt e grupit ton\u00eb t\u00eb par\u00eb po punojn\u00eb me ekipet dhe i ndihmojn\u00eb ato t\u00eb b\u00ebhen t\u00eb suksesshme. <\/p>\n

Mendoj se situata aktuale na hap mund\u00ebsi dhe perspektiva q\u00eb ndoshta ne vet\u00eb akoma nuk i kemi kuptuar plot\u00ebsisht. Por, p\u00ebrvoja dhe praktika q\u00eb po marrim tani e konfirmon se kemi zgjedhur rrug\u00ebn e duhur p\u00ebr zhvillim, nuk do t'i humbim k\u00ebto mund\u00ebsi t\u00eb reja n\u00eb t\u00eb ardhmen dhe do t\u00eb jemi po aq efektiv\u00eb n\u00eb p\u00ebrgjigjen ndaj sfidave q\u00eb do t'i kund\u00ebrvihen \u2018Sportmasterit\u2019.<\/p>\n

P\u00ebrfundimet<\/h3>\n

Gjat\u00eb k\u00ebsaj periudhe t\u00eb v\u00ebshtir\u00eb, ne formulua parimet kryesore mbi t\u00eb cilat mb\u00ebshtetet zhvillimi i software-it, t\u00eb cilat mendoj se do t\u00eb jen\u00eb relevante 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 mb\u00ebshtetet gjith\u00e7ka. Punonj\u00ebsit duhet t\u00eb g\u00ebzojn\u00eb pun\u00ebn, t\u00eb kuptojn\u00eb q\u00ebllimet e kompanis\u00eb dhe q\u00ebllimet e produkteve me t\u00eb cilat punojn\u00eb. Dhe, sigurisht, duhet t\u00eb ken\u00eb mund\u00ebsi p\u00ebr zhvillim profesional. <\/p>\n

Teknologjia<\/strong>. \u00cbsht\u00eb e nevojshme q\u00eb kompania t\u00eb qaset me maturi ndaj pun\u00ebs me teknologjin\u00eb e saj dhe t\u00eb rris\u00eb kompetencat aty ku \u00ebsht\u00eb e nevojshme. Duket shum\u00eb e thjesht\u00eb dhe e dukshme. Dhe shpesh her\u00eb injorohet.<\/p>\n

Proceset<\/strong>. \u00cbsht\u00eb e r\u00ebnd\u00ebsishme t\u00eb nd\u00ebrtohet sakt\u00eb puna e ekipeve produktive dhe qendrat e kompetenc\u00ebs, t\u00eb krijohet bashk\u00ebpunimi me biznesin, q\u00eb t\u00eb punosh me t\u00eb si me nj\u00eb partner.<\/p>\n<\/p>\n

N\u00eb p\u00ebrgjith\u00ebsi, k\u00ebshtu e kaluam. Tez\u00eb kryesore e modernitetit u konfirmua edhe nj\u00eb her\u00eb, duke klikuar fort 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-n t\u00ebnd. Kjo nuk \u00ebsht\u00eb thjesht nj\u00eb kanal i hapur p\u00ebr shitje ose nj\u00eb aplikacion i bukur p\u00ebrmes t\u00eb cilit mund t\u00eb blini di\u00e7ka (dhe as sepse konkurent\u00ebt kan\u00eb gjithashtu ndonj\u00eb gj\u00eb t\u00eb bukur). Kjo nuk \u00ebsht\u00eb nj\u00eb rezerv\u00eb p\u00ebr rastet e k\u00ebqija, q\u00eb do t\u00eb ndihmoj\u00eb p\u00ebr t\u00eb kaluar stuhin\u00eb.<\/p>\n

Kjo \u00ebsht\u00eb nj\u00eb domosdoshm\u00ebri e v\u00ebrtet\u00eb. N\u00eb t\u00eb cil\u00ebn duhet t\u00eb jen\u00eb t\u00eb gatsh\u00ebm jo vet\u00ebm kapacitetet teknike dhe infrastruktura juaj, por edhe njer\u00ebzit dhe proceset. Sepse mund t\u00eb blihen shpejt kujtes\u00eb, hap\u00ebsir\u00eb, t\u00eb zhvillohen instance t\u00eb reja dhe gj\u00ebra t\u00eb tjera brenda disa or\u00ebve. Por njer\u00ebzit dhe proceset duhet t\u00eb p\u00ebrgatiten p\u00ebr k\u00ebt\u00eb m\u00eb par\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 kalojm\u00eb shpejt n\u00eb tregtin\u00eb online n\u00eb kushte t\u00eb reja | ProHoster","description":"P\u00ebrsh\u00ebndetje! Un\u00eb quhem Mikhail, jam z\u00ebvend\u00ebsdrejtor i IT n\u00eb kompanin\u00eb \"Sportmaster\". Dua t\u00eb ndaj nj\u00eb histori se si e kaluam v\u00ebshtir\u00ebsit\u00eb q\u00eb u shfaq\u00ebn gjat\u00eb pandemis\u00eb. N\u00eb dit\u00ebt e para t\u00eb realiteteve t\u00eb reja, formati i zakonsh\u00ebm i shitjeve offline t\u00eb \"Sportmaster\" u ndal, dhe ngarkesa n\u00eb kanal online, sidomos n\u00eb aspektin e dor\u00ebzimeve n\u00eb adres\u00eb t\u00eb klient\u00ebve, u rrit 10 her\u00eb. Brenda disa","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. \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. \u0417\u0430 \u043d\u0435\u0441\u043a\u043e\u043b\u044c\u043a\u043e","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"},"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}]}}