{"id":37650,"date":"2019-10-31T22:18:50","date_gmt":"2019-10-31T19:18:50","guid":{"rendered":"https:\/\/prohoster.info\/blog\/arhitektura-billinga-novogo-pokoleniya-transformatsiya-s-perehodom-na-tarantool\/"},"modified":"2019-10-31T22:18:50","modified_gmt":"2019-10-31T19:18:50","slug":"arhitektura-billinga-novogo-pokoleniya-transformatsiya-s-perehodom-na-tarantool","status":"publish","type":"post","link":"https:\/\/prohoster.info\/cs\/blog\/administrirovanie\/arhitektura-billinga-novogo-pokoleniya-transformatsiya-s-perehodom-na-tarantool","title":{"rendered":"Architektura nov\u00e9ho generace billingov\u00fdch syst\u00e9m\u016f: transformace s p\u0159echodem na Tarantool","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"

Pro\u010d pot\u0159ebuje takov\u00e1 korporace jako MegaFon Tarantool v billingu? Na prvn\u00ed pohled to vypad\u00e1, \u017ee dodavatel p\u0159ijde, p\u0159inese n\u011bjakou velkou krabici, zapoj\u00ed ji do z\u00e1suvky \u2014 a voil\u00e0, m\u00e1te billing! To takhle kdysi bylo, ale dnes je to archaick\u00e9 a takov\u00ed dinosau\u0159i u\u017e vym\u00edraj\u00ed nebo u\u017e vyhynuli. P\u016fvodn\u011b byl billing syst\u00e9m pro vystavov\u00e1n\u00ed \u00fa\u010dt\u016f \u2014 kalkula\u010dka pro po\u010d\u00edt\u00e1n\u00ed. V modern\u00edm telekomunika\u010dn\u00edm sektoru je to syst\u00e9m automatizace cel\u00e9ho \u017eivotn\u00edho cyklu interakce se z\u00e1kazn\u00edkem od uzav\u0159en\u00ed smlouvy a\u017e po jej\u00ed zru\u0161en\u00ed<\/b>, v\u010detn\u011b tarifikace v re\u00e1ln\u00e9m \u010dase, p\u0159ij\u00edm\u00e1n\u00ed plateb a mnoha dal\u0161\u00edch funkc\u00ed. Billing v telekomunika\u010dn\u00edch spole\u010dnostech je podobn\u00fd bojov\u00e9mu robotu \u2014 velk\u00e9mu, siln\u00e9mu a vybaven\u00e9mu nejmodern\u011bj\u0161\u00edmi zbran\u011bmi.<\/p>\n

\"Architektura
\n
\nA co m\u00e1 spole\u010dn\u00e9ho Tarantool? O tom se dozv\u00edte Oleg Ivlev<\/b> a\u00a0Andrej Knyazev<\/b>. Oleg je hlavn\u00ed architekt spole\u010dnosti MegaFon<\/a><\/noindex> s bohat\u00fdmi zku\u0161enostmi z pr\u00e1ce v zahrani\u010dn\u00edch firm\u00e1ch, Andrej je \u0159editelem pro obchodn\u00ed syst\u00e9my. Z jejich prezentace na\u00a0Tarantool Conference 2018<\/a><\/noindex>\u00a0se dozv\u00edte, jak\u00fd v\u00fdznam m\u00e1 R&D v korporac\u00edch, co je Tarantool, jak k \u00fapadku vertik\u00e1ln\u00edho \u0161k\u00e1lov\u00e1n\u00ed a globalizaci do\u0161lo a staly se p\u0159edpoklady pro vznik t\u00e9to DB ve spole\u010dnosti, o technologick\u00fdch v\u00fdzv\u00e1ch, transformaci architektury a jak se technologick\u00fd stack MegaFon podob\u00e1 Netflixu, Googlu a Amazonu.
\n<\/a><\/noindex>
\n

\r\n \"P\u0159ehr\u00e1t\r\n
<\/div>\r\n <\/div><\/center><\/p>\n

Projekt \u201eJednotn\u00fd billing\u201c<\/h2>\n

\nProjekt, o kter\u00e9m bude \u0159e\u010d, se naz\u00fdv\u00e1 \u201eJednotn\u00fd billing\u201c. Pr\u00e1v\u011b v n\u011bm Tarantool prok\u00e1zal sv\u00e9 nejlep\u0161\u00ed vlastnosti. <\/p>\n

\"Architektura
\n
\nR\u016fst v\u00fdkonu Hi-End za\u0159\u00edzen\u00ed nedok\u00e1zal dr\u017eet krok s r\u016fstem u\u017eivatelsk\u00e9 z\u00e1kladny a po\u010dtem slu\u017eeb, o\u010dek\u00e1val se dal\u0161\u00ed r\u016fst po\u010dtu u\u017eivatel\u016f a slu\u017eeb d\u00edky M2M, IoT, a m\u00edstn\u00ed zvl\u00e1\u0161tnosti vedly ke zhor\u0161en\u00ed time-to-market. Spole\u010dnost se rozhodla vytvo\u0159it jedin\u00e9 obchodn\u00ed syst\u00e9m s unik\u00e1tn\u00ed modul\u00e1rn\u00ed architekturou sv\u011btov\u00e9 \u00farovn\u011b, jako n\u00e1hradu za 8 r\u016fzn\u00fdch sou\u010dasn\u00fdch billingov\u00fdch syst\u00e9m\u016f.<\/p>\n

MegaFon je osm spole\u010dnost\u00ed v jedn\u00e9<\/b>. V roce 2009 byla dokon\u010dena reorganizace: pobo\u010dky po cel\u00e9 Rusku se spojily do jedin\u00e9 spole\u010dnosti OAO \u201eMegaFon\u201c (nyn\u00ed PAO). Tak se ve spole\u010dnosti objevilo 8 billingov\u00fdch syst\u00e9m\u016f s vlastn\u00edmi 'custom' \u0159e\u0161en\u00edmi, m\u00edstn\u00edmi rysy a r\u016fznou organiza\u010dn\u00ed strukturou, IT a marketingem.<\/p>\n

V\u0161e bylo v po\u0159\u00e1dku, dokud jsme nespustili jeden spole\u010dn\u00fd feder\u00e1ln\u00ed produkt. Objevilo se mnoho probl\u00e9m\u016f: u n\u011bkoho se \u00fa\u010dtov\u00e1n\u00ed zaokrouhluje nahoru, u n\u011bkoho dol\u016f, a n\u011bkdo m\u00e1 pr\u016fm\u011brn\u00e9 aritmetick\u00e9 z\u00fa\u010dtov\u00e1n\u00ed. Takov\u00fdch situac\u00ed jsou tis\u00edce.<\/p>\n

I kdy\u017e je verze billingov\u00e9ho syst\u00e9mu jedna, dodavatel je stejn\u00fd, nastaven\u00ed se li\u0161ila natolik, \u017ee jejich sjednocen\u00ed trvalo dlouho. Sna\u017eili jsme se sn\u00ed\u017eit jejich po\u010det a narazili jsme na dal\u0161\u00ed probl\u00e9m, kter\u00fd je zn\u00e1m mnoha korporac\u00edm.<\/p>\n

Vertik\u00e1ln\u00ed \u0161k\u00e1lov\u00e1n\u00ed<\/b>. I to nejlep\u0161\u00ed hardwarov\u00e9 vybaven\u00ed v t\u00e9 dob\u011b nespl\u0148ovalo pot\u0159eby. Pou\u017e\u00edvali jsme za\u0159\u00edzen\u00ed od Hewlett-Packard, modely Superdome Hi-End, ale ani to nezvl\u00e1dlo pot\u0159eby dvou pobo\u010dek. Cht\u011blo to horizont\u00e1ln\u00ed \u0161k\u00e1lov\u00e1n\u00ed bez vysok\u00fdch provozn\u00edch n\u00e1klad\u016f a kapit\u00e1lov\u00fdch investic.<\/p>\n

O\u010dek\u00e1v\u00e1n\u00ed r\u016fstu po\u010dtu abonent\u016f a slu\u017eeb<\/b>. Konzultanti p\u0159inesli do telekomunika\u010dn\u00edho sv\u011bta p\u0159\u00edb\u011bhy o IoT a M2M: nastanou \u010dasy, kdy ka\u017ed\u00fd telefon a \u017eehl\u00edc\u00ed prkno bude m\u00edt SIM kartu, a v ledni\u010dce budou dv\u011b. Dnes m\u00e1me ur\u010dit\u00e9 mno\u017estv\u00ed abonent\u016f, ale v bl\u00edzk\u00e9 budoucnosti jich bude o \u0159\u00e1d v\u00edce.<\/p>\n

Technologick\u00e9 v\u00fdzvy<\/h2>\n

\nTyto \u010dty\u0159i d\u016fvody n\u00e1s vedly k v\u00e1\u017en\u00fdm zm\u011bn\u00e1m. Byla volba mezi modernizac\u00ed syst\u00e9mu a n\u00e1vrhem od z\u00e1klad\u016f. Dlouho jsme p\u0159em\u00fd\u0161leli, p\u0159ij\u00edmali v\u00e1\u017en\u00e1 rozhodnut\u00ed, hr\u00e1li tendry. Nakonec jsme se rozhodli navrhnout zcela od za\u010d\u00e1tku a pustili jsme se do zaj\u00edmav\u00fdch v\u00fdzev \u2013 technologick\u00fdch v\u00fdzev.<\/p>\n

\u0160k\u00e1lovatelnost<\/h3>\n

\nPokud d\u0159\u00edve bylo, \u0159ekn\u011bme 8 billing\u016f pro 15 milion\u016f abonent\u016f<\/b>, te\u010f by m\u011blo vyj\u00edt 100 milion\u016f abonent\u016f a v\u00edce<\/b>\u00a0\u2013 z\u00e1t\u011b\u017e je o \u0159\u00e1d vy\u0161\u0161\u00ed.<\/p>\n

Stali jsme se srovnateln\u00fdmi co do velikosti s velk\u00fdmi internetov\u00fdmi hr\u00e1\u010di jako Mail.ru nebo Netflix.<\/p><\/blockquote>\n

\nAv\u0161ak dal\u0161\u00ed zvy\u0161ov\u00e1n\u00ed z\u00e1t\u011b\u017ee a po\u010dtu abonent\u016f p\u0159ineslo v\u00e1\u017en\u00e9 \u00fakoly.<\/p>\n

Geografie na\u0161\u00ed obrovsk\u00e9 zem\u011b<\/h3>\n

\nMezi Kaliningradem a Vladivostokem 7500 km a 10 \u010dasov\u00fdch p\u00e1sem<\/b>. Rychlost sv\u011btla je kone\u010dn\u00e1 a na takov\u00fdch vzd\u00e1lenostech jsou zpo\u017ed\u011bn\u00ed ji\u017e v\u00fdznamn\u00e1. 150 ms na nejmodern\u011bj\u0161\u00edch optick\u00fdch kan\u00e1lech je pro real-time \u00fa\u010dtov\u00e1n\u00ed, jak\u00e9 se dnes pou\u017e\u00edv\u00e1 v telekomunikac\u00edch v Rusku, p\u0159\u00edli\u0161. Nav\u00edc je t\u0159eba prov\u00e1d\u011bt aktualizace b\u011bhem jednoho pracovn\u00edho dne, a to s r\u016fzn\u00fdmi \u010dasov\u00fdmi p\u00e1smy p\u0159edstavuje probl\u00e9m.<\/p>\n

Nehodl\u00e1me pouze poskytovat slu\u017eby za p\u0159edplatn\u00e9, m\u00e1me slo\u017eit\u00e9 tarify, bal\u00ed\u010dky a r\u016fzn\u00e9 modifik\u00e1tory. Nen\u00ed na\u0161\u00edm c\u00edlem jen povolit nebo zak\u00e1zat vol\u00e1n\u00ed p\u0159edplatiteli, ale poskytnout mu ur\u010ditou kv\u00f3tu \u2013 po\u010d\u00edtat hovory a \u010dinnosti v re\u00e1ln\u00e9m \u010dase tak, aby si toho nev\u0161iml.<\/p>\n

Odolnost proti v\u00fdpadk\u016fm<\/h3>\n

<\/p>\n

To je druh\u00e1 strana centralizace.<\/p><\/blockquote>\n

\nPokud shrom\u00e1\u017ed\u00edme v\u0161echny p\u0159edplatitele v jednom syst\u00e9mu, jak\u00e9koli havarijn\u00ed ud\u00e1losti a katastrofy mohou b\u00fdt pro podnik\u00e1n\u00ed katastrof\u00e1ln\u00ed. Proto navrhujeme syst\u00e9m tak, aby se minimalizoval vliv hav\u00e1ri\u00ed na celou z\u00e1kladnu p\u0159edplatitel\u016f.<\/p>\n

To je op\u011bt d\u016fsledkem odm\u00edtnut\u00ed vertik\u00e1ln\u00edho \u0161k\u00e1lov\u00e1n\u00ed. Kdy\u017e jsme p\u0159e\u0161li k horizont\u00e1ln\u00edmu \u0161k\u00e1lov\u00e1n\u00ed, zv\u00fd\u0161ili jsme po\u010det server\u016f ze stovek na tis\u00edce. Je t\u0159eba je \u0159\u00eddit, vybudovat vz\u00e1jemnou zastupitelnost, automaticky z\u00e1lohovat IT-infrastrukturu a obnovit distribuovan\u00fd syst\u00e9m.<\/p>\n

St\u00e1ly p\u0159ed n\u00e1mi zaj\u00edmav\u00e9 v\u00fdzvy. Navrhli jsme syst\u00e9m a v tu chv\u00edli jsme se pokusili naj\u00edt sv\u011btovou nejlep\u0161\u00ed praxi, abychom zjistili, jak jsme na tom s trendem, jak dodr\u017eujeme modern\u00ed technologie.<\/p>\n

Sv\u011btov\u00e1 praxe<\/h2>\n

<\/p>\n

Je p\u0159ekvapuj\u00edc\u00ed, \u017ee v glob\u00e1ln\u00edm telekomunika\u010dn\u00edm pr\u016fmyslu jsme nena\u0161li \u017e\u00e1dnou referenci.<\/p><\/blockquote>\n

\nEvropa vypadla z hlediska po\u010dtu p\u0159edplatitel\u016f a rozsahu, USA z d\u016fvodu plochosti sv\u00fdch tarif\u016f. N\u011bco jsme se pod\u00edvali v \u010c\u00edn\u011b, a n\u011bco jsme na\u0161li v Indii a vzali odborn\u00edky z Vodafone India.<\/p>\n

Pro anal\u00fdzu architektury jsme sestavili Dream Team veden\u00fd IBM \u2013 architekty z r\u016fzn\u00fdch oblast\u00ed. Tito lid\u00e9 mohli adekv\u00e1tn\u011b posoudit, co d\u011bl\u00e1me, a p\u0159in\u00e9st do na\u0161\u00ed architektury ur\u010dit\u00e9 znalosti.<\/p>\n

\u0160k\u00e1lov\u00e1n\u00ed<\/h2>\n

\nN\u011bkolik \u010d\u00edsel pro ilustraci.<\/p>\n

Navrhujeme syst\u00e9m pro 80 milion\u016f p\u0159edplatitel\u016f s rezervou na miliardu<\/b>. T\u00edm odstra\u0148ujeme budouc\u00ed prahy. Nen\u00ed to proto, \u017ee bychom m\u011bli v pl\u00e1nu dob\u00fdt \u010c\u00ednu, ale kv\u016fli n\u00e1poru IoT a M2M.<\/p>\n

300 milion\u016f dokument\u016f je zpracov\u00e1v\u00e1no v re\u00e1ln\u00e9m \u010dase<\/b>. A\u010dkoli m\u00e1me 80 milion\u016f p\u0159edplatitel\u016f, pracujeme i s potenci\u00e1ln\u00edmi klienty a s t\u011bmi, kte\u0159\u00ed od n\u00e1s ode\u0161li, pokud je t\u0159eba vym\u00e1hat pohled\u00e1vky. Skute\u010dn\u00e9 objemy jsou proto v\u00fdrazn\u011b vy\u0161\u0161\u00ed.<\/p>\n

2 miliardy transakc\u00ed<\/b> ka\u017ed\u00fd den m\u011bn\u00ed z\u016fstatek \u2013 jsou to platby, p\u0159ipo\u010d\u00edt\u00e1n\u00ed, hovory a dal\u0161\u00ed ud\u00e1losti.\u00a0200 TB dat se aktivn\u011b m\u011bn\u00ed<\/b>, o n\u011bco pomaleji se m\u011bn\u00ed 8 PB dat<\/b>, a to nejsou archivy, ale \u017eiv\u00e1 data v jednom billingov\u00e9m syst\u00e9mu. Rozsah podle datov\u00fdch center \u2014 5 tis\u00edc server\u016f na 14 m\u00edstech<\/b>.<\/p>\n

Technologick\u00fd stack<\/h2>\n

\nKdy\u017e jsme pl\u00e1novali architekturu a za\u010dali budovat syst\u00e9m, importovali jsme si ty nejzaj\u00edmav\u011bj\u0161\u00ed a nejmodern\u011bj\u0161\u00ed technologie. Vznikl technologick\u00fd stack, kter\u00fd znaj\u00ed v\u0161ichni internetov\u00ed hr\u00e1\u010di a korporace vyv\u00edjej\u00edc\u00ed vysoce zat\u00ed\u017een\u00e9 syst\u00e9my. <\/p>\n

\"Architektura
\n
\nStack je podobn\u00fd stack\u016fm jin\u00fdch velk\u00fdch hr\u00e1\u010d\u016f: Netflix, Twitter, Viber. Skl\u00e1d\u00e1 se ze 6 komponent, ale my chceme jeho velikost zkr\u00e1tit a unifikovat.<\/p>\n

Flexibilita je dobr\u00e1, ale ve velk\u00e9 korporaci je bez unifikace nemo\u017en\u00e9.<\/p><\/blockquote>\n

\nNepl\u00e1nujeme nahradit Oracle Tarantool. V realit\u011b velk\u00fdch spole\u010dnost\u00ed je to utopie, nebo k\u0159\u00ed\u017eov\u00e1 v\u00fdprava na 5-10 let s nejist\u00fdm v\u00fdsledkem. Ale Cassandra a Couchbase mohou b\u00fdt klidn\u011b nahrazeny Tarantool, a tomu se chceme p\u0159ibl\u00ed\u017eit.<\/p>\n

Pro\u010d Tarantool?<\/h2>\n

\nExistuj\u00ed 4 jednoduch\u00e9 krit\u00e9ria, pro\u010d jsme vybrali tuto datab\u00e1zi.<\/p>\n

Rychlost<\/b>. Provedli jsme z\u00e1t\u011b\u017eov\u00e9 testy na pr\u016fmyslov\u00fdch syst\u00e9mech MegaFon. Tarantool vyhr\u00e1l \u2014 uk\u00e1zal nejlep\u0161\u00ed v\u00fdkon.<\/p>\n

Nen\u00ed pravda, \u017ee by jin\u00e9 syst\u00e9my neuspokojovaly pot\u0159eby MegaFon. Sou\u010dasn\u00e1 \u0159e\u0161en\u00ed v pam\u011bti jsou tak v\u00fdkonn\u00e1, \u017ee firma m\u00e1 dostate\u010dn\u00e9 rezervy. Ale n\u00e1s zaj\u00edm\u00e1 spolupracovat s l\u00eddrem, a ne s t\u00edm, kdo t\u00e1pe vzadu, v\u010detn\u011b v\u00fdsledk\u016f z\u00e1t\u011b\u017eov\u00fdch test\u016f.<\/p>\n

Tarantool pokr\u00fdv\u00e1 pot\u0159eby spole\u010dnosti i z dlouhodob\u00e9ho hlediska.<\/p><\/blockquote>\n

\nN\u00e1klady TCO<\/b>. Podpora Couchbase na objemech MegaFon stoj\u00ed astronomick\u00e9 pen\u00edze, zat\u00edmco situace s Tarantool je mnohem p\u0159\u00edjemn\u011bj\u0161\u00ed, a co se funkcionality t\u00fd\u010de, jsou si bl\u00edzk\u00e9.<\/p>\n

Dal\u0161\u00ed p\u0159\u00edjemnou vlastnost\u00ed, kter\u00e1 m\u00edrn\u011b ovlivnila na\u0161e rozhodov\u00e1n\u00ed \u2014 Tarantool l\u00e9pe pracuje s pam\u011bt\u00ed ne\u017e ostatn\u00ed datab\u00e1ze. Ukazuje maxim\u00e1ln\u00ed efektivitu<\/b>.<\/p>\n

Spolehlivost<\/b>. MegaFon investuje do spolehlivosti, asi jako nikdo jin\u00fd. Proto, kdy\u017e jsme se pod\u00edvali na Tarantool, zjistili jsme, \u017ee ho mus\u00edme upravit tak, aby spl\u0148oval na\u0161e po\u017eadavky.<\/p>\n

Investovali jsme sv\u016fj \u010das a finance a spole\u010dn\u011b s Mail.ru vytvo\u0159ili enterprise verzi, kter\u00e1 se nyn\u00ed pou\u017e\u00edv\u00e1 ji\u017e v n\u011bkolika dal\u0161\u00edch spole\u010dnostech.<\/p>\n

Tarantool-enterprise n\u00e1s pln\u011b uspokojil z hlediska bezpe\u010dnosti, spolehlivosti a logov\u00e1n\u00ed.<\/p><\/blockquote>\n

<\/p>\n

Partnerstv\u00ed<\/h3>\n

\nNejd\u016fle\u017eit\u011bj\u0161\u00ed pro m\u011b je p\u0159\u00edm\u00fd kontakt s v\u00fdvoj\u00e1\u0159em<\/b>. To je p\u0159esn\u011b to, \u010d\u00edm n\u00e1s lid\u00e9 z Tarantool z\u00edskali.<\/p>\n

Pokud p\u0159ijde\u0161 k hr\u00e1\u010di, zejm\u00e9na k tomu, kter\u00fd pracuje s kl\u00ed\u010dov\u00fdm klientem, a \u0159\u00edk\u00e1\u0161, \u017ee pot\u0159ebuje\u0161, aby datab\u00e1ze um\u011bla toto, to a to, obvykle odpov\u00edd\u00e1:<\/p>\n

\u2014 Dob\u0159e, dejte po\u017eadavky na dno t\u00e9 hromady \u2014 n\u011bkdy se k nim asi dostaneme.<\/i><\/p>\n

Mnoz\u00ed maj\u00ed roadmap na p\u0159\u00ed\u0161t\u00ed 2-3 roky a je t\u00e9m\u011b\u0159 nemo\u017en\u00e9 se do toho zapojit, zat\u00edmco v\u00fdvoj\u00e1\u0159i Tarantoolu okouzluj\u00ed otev\u0159enost\u00ed, a to nejen s MegaFonem, a p\u0159izp\u016fsobuj\u00ed sv\u016fj syst\u00e9m z\u00e1kazn\u00edk\u016fm. To je skv\u011bl\u00e9 a n\u00e1m se to opravdu l\u00edb\u00ed.<\/p>\n

Kde jsme pou\u017eili Tarantool<\/h2>\n

\nU n\u00e1s se Tarantool pou\u017e\u00edv\u00e1 v n\u011bkolika prvc\u00edch. Prvn\u00ed \u2014 v pilotn\u00edm projektu<\/b>, kter\u00fd jsme vytvo\u0159ili na syst\u00e9mu adresn\u00edho katalogu. V ur\u010dit\u00e9m okam\u017eiku jsme cht\u011bli, aby to byl syst\u00e9m, kter\u00fd by vypadal jako Yandex.Maps a Google Maps, ale dopadlo to pon\u011bkud jinak. <\/p>\n

Pro p\u0159\u00edklad, adresn\u00ed katalog v prodejn\u00edm rozhran\u00ed. Na Oracle trv\u00e1 vyhled\u00e1n\u00ed pot\u0159ebn\u00e9 adresy 12-13 s \u2014 to jsou nep\u0159\u00edjemn\u00e1 \u010d\u00edsla. Kdy\u017e p\u0159epneme na Tarantool, vym\u011bn\u00edme Oracle za jinou datab\u00e1zi v konzoli a provedeme to sam\u00e9 vyhled\u00e1n\u00ed, z\u00edsk\u00e1me zrychlen\u00ed 200kr\u00e1t! M\u011bsto se zobraz\u00ed po t\u0159et\u00edm p\u00edsmenu. Nyn\u00ed p\u0159izp\u016fsobujeme rozhran\u00ed, aby se to dalo prov\u00e9st po prvn\u00edm. P\u0159esto je rychlost reakce zcela jin\u00e1 \u2014 u\u017e milisekundy m\u00edsto sekund.<\/p>\n

Druh\u00e9 pou\u017eit\u00ed \u2014 m\u00f3dn\u00ed t\u00e9ma, kter\u00e1 se naz\u00fdv\u00e1 dvourychlostn\u00ed IT<\/b>. To proto, \u017ee konzultanti z ka\u017ed\u00e9ho kouta \u0159\u00edkaj\u00ed, \u017ee korporace by m\u011bly j\u00edt t\u00edmto sm\u011brem.<\/p>\n

\"Architektura
\n
\nTady je vrstva infrastruktury, nad n\u00ed dom\u00e9ny, nap\u0159\u00edklad faktura\u010dn\u00ed syst\u00e9m, jako u telekomunikac\u00ed, firemn\u00ed syst\u00e9my, firemn\u00ed reporty. To je j\u00e1dro, kter\u00e9 se nem\u00e1 dot\u00fdkat. To znamen\u00e1, \u017ee samoz\u0159ejm\u011b je mo\u017en\u00e9, ale paranoidn\u011b zaji\u0161\u0165ovat kvalitu, proto\u017ee to p\u0159in\u00e1\u0161\u00ed korporaci pen\u00edze.<\/p>\n

D\u00e1le je vrstva mikroslu\u017eeb \u2014 to, co diferencuje oper\u00e1tora nebo jin\u00e9ho hr\u00e1\u010de. Mikroslu\u017eby je mo\u017en\u00e9 rychle vytv\u00e1\u0159et na z\u00e1klad\u011b ur\u010dit\u00fdch cache, p\u0159i\u010dem\u017e se zde zvedaj\u00ed data z r\u016fzn\u00fdch dom\u00e9n. Tady je pole pro experimenty<\/b>\u00a0\u2014 pokud n\u011bco nevy\u0161lo, uzav\u0159e\u0161 jednu mikroslu\u017ebu, otev\u0159e\u0161 jinou. To opravdu zaji\u0161\u0165uje zkr\u00e1cen\u00fd time-to-market a zvy\u0161uje spolehlivost a rychlost spole\u010dnosti.<\/p>\n

Mikroslu\u017eby \u2014 to je pravd\u011bpodobn\u011b hlavn\u00ed role Tarantoolu v MegaFonu. <\/p><\/blockquote>\n

<\/p>\n

Kde pl\u00e1nujeme pou\u017e\u00edt Tarantool<\/h2>\n

\nPokud srovn\u00e1me n\u00e1\u0161 \u00fasp\u011b\u0161n\u00fd projekt fakturace s transforma\u010dn\u00edmi programy ve Deutsche Telekom, Svyaznoy, Vodafone India, je \u00fa\u017easn\u011b dynamick\u00fd a kreativn\u00ed. V pr\u016fb\u011bhu realizace tohoto projektu se nejen transformoval MegaFon a jeho struktura, ale vznikla tak\u00e9 Tarantool-enterprise u Mail.ru a n\u00e1\u0161 dodavatel Nexign (d\u0159\u00edve \u00abPeter-Service\u00bb) \u2014 BSS Box (krabicov\u00e9 faktura\u010dn\u00ed \u0159e\u0161en\u00ed).<\/p>\n

Toto je v jist\u00e9m smyslu historick\u00fd projekt pro rusk\u00fd trh. Lze ho p\u0159irovnat k tomu, co je pops\u00e1no v knize Fredericka Brookse \u201eMythical Man-Month\u201c. Tehdy, v 60. letech, pro v\u00fdvoj nov\u00e9ho opera\u010dn\u00edho syst\u00e9mu OS\/360 pro mainframy IBM zapojil 5 000 lid\u00ed. U n\u00e1s je to m\u00e9n\u011b \u2014 1 800, ale na\u0161i lid\u00e9 jsou v pruhovan\u00e9m, a s ohledem na pou\u017eit\u00ed open-source a nov\u00e9 p\u0159\u00edstupy pracujeme efektivn\u011bji.<\/p>\n

N\u00ed\u017ee jsou uvedeny dom\u00e9ny fakturace nebo, pokud to \u0159ekneme \u0161\u00ed\u0159eji, \u2014 podnikov\u00fdch syst\u00e9m\u016f. Lid\u00e9 z enterprise skv\u011ble znaj\u00ed CRM. Ostatn\u00ed syst\u00e9my by m\u011bly m\u00edt ji\u017e v\u0161ichni: Open API, API Gateway.<\/p>\n

\"Architektura
\n<\/p>\n

Open API<\/h3>\n

\nPod\u00edvejme se op\u011bt na \u010d\u00edsla a na to, jak nyn\u00ed funguje Open API. Jeho z\u00e1t\u011b\u017e je \u2014 10 000 transakc\u00ed za sekundu<\/b>. Vzhledem k tomu, \u017ee pl\u00e1nujeme aktivn\u011b rozv\u00edjet vrstvu mikroslu\u017eeb a budovat ve\u0159ejn\u00fd API MegaFon, o\u010dek\u00e1v\u00e1me v budoucnu v\u011bt\u0161\u00ed r\u016fst pr\u00e1v\u011b v t\u00e9to \u010d\u00e1sti.\u00a0100 000 transakc\u00ed ur\u010dit\u011b bude<\/b>.<\/p>\n

Nev\u00edm, zda se vyrovn\u00e1me v SSO s Mail.ru \u2014 kluci maj\u00ed \u00fadajn\u011b 1 000 0000 transakc\u00ed za sekundu. Jejich \u0159e\u0161en\u00ed je pro n\u00e1s velice zaj\u00edmav\u00e9 a pl\u00e1nujeme p\u0159evz\u00edt jejich zku\u0161enosti \u2014 nap\u0159\u00edklad ud\u011blat funk\u010dn\u00ed z\u00e1lohu SSO pomoc\u00ed Tarantool. Nyn\u00ed se t\u00edm zab\u00fdvaj\u00ed v\u00fdvoj\u00e1\u0159i z Mail.ru u n\u00e1s.<\/p>\n

CRM<\/h2>\n

\nCRM \u2014 to jsou ti 80 milion\u016f p\u0159edplatitel\u016f, kter\u00e9 chceme dostat na miliardu, proto\u017ee u\u017e existuje 300 milion\u016f dokument\u016f, kter\u00e9 zahrnuj\u00ed t\u0159\u00edletou historii. Opravdu o\u010dek\u00e1v\u00e1me nov\u00e9 slu\u017eby a zde bude r\u016fstov\u00fd bod \u2014 to jsou p\u0159ipojen\u00e9 slu\u017eby<\/b>. Toto je oblast, kter\u00e1 poroste, proto\u017ee slu\u017eeb bude st\u00e1le v\u00edce. Podle toho budeme pot\u0159ebovat historii, nechceme na tom klop\u00fdtat.<\/p>\n

Samotn\u00e1 fakturace v \u010d\u00e1sti vystavov\u00e1n\u00ed \u00fa\u010dt\u016f, pr\u00e1ce s pohled\u00e1vkami klient\u016f se transformovala na samostatnou dom\u00e9nu<\/b>. Abychom zv\u00fd\u0161ili produktivitu, byl pou\u017eit architektonick\u00fd vzor dom\u00e9nov\u00e9 architektury<\/b>.<\/p>\n

Syst\u00e9m je rozd\u011blen do dom\u00e9n, zat\u00ed\u017een\u00ed je rozlo\u017eeno a zaji\u0161t\u011bna je odolnost proti v\u00fdpadk\u016fm. D\u00e1le jsme pracovali s distribuovanou architekturou.<\/p><\/blockquote>\n

\nV\u0161echno ostatn\u00ed jsou \u0159e\u0161en\u00ed na \u00farovni enterprise. Ve skladu hovor\u016f \u2013 2 miliardy denn\u011b<\/b>, 60 miliard m\u011bs\u00ed\u010dn\u011b. N\u011bkdy je pot\u0159eba je p\u0159epo\u010d\u00edtat za m\u011bs\u00edc, a je lep\u0161\u00ed to ud\u011blat rychle. Finan\u010dn\u00ed monitoring<\/b>\u00a0\u2013 to jsou pr\u00e1v\u011b t\u011bch 300 milion\u016f, kter\u00e9 trvale rostou a rostou: abonenti \u010dasto p\u0159eskakuj\u00ed mezi oper\u00e1tory, \u010d\u00edm\u017e zvy\u0161uj\u00ed tuto \u010d\u00e1st.<\/p>\n

Nejv\u00edce telekomunika\u010dn\u00ed komponenta z mobiln\u00edho spojen\u00ed \u2013 to je on-line tariface<\/b>. To jsou ty syst\u00e9my, kter\u00e9 v\u00e1m umo\u017e\u0148uj\u00ed volat nebo nevolat, p\u0159ij\u00edmaj\u00ed rozhodnut\u00ed v re\u00e1ln\u00e9m \u010dase. Zde je z\u00e1t\u011b\u017e 30 000 transakc\u00ed za sekundu, ale s ohledem na rostouc\u00ed p\u0159enos dat pl\u00e1nujeme 250 000 transakc\u00ed<\/b>, a proto se velmi zaj\u00edm\u00e1me o Tarantool.<\/p>\n

P\u0159edchoz\u00ed obr\u00e1zek ukazuje dom\u00e9ny, kde m\u00e1me v \u00famyslu aplikovat Tarantool. Samoz\u0159ejm\u011b je CRM \u0161ir\u0161\u00ed a m\u00e1me v \u00famyslu jej pou\u017e\u00edt p\u0159\u00edmo v j\u00e1dru. <\/p>\n

Moje odhadovan\u00e1 \u010d\u00edsla TTX na 100 milion\u016f abonent\u016f m\u011b jako architekta znepokojuj\u00ed \u2013 co kdy\u017e to bude 101 milion\u016f? Zase v\u0161echno p\u0159ed\u011bl\u00e1vat? Abychom tomu p\u0159ede\u0161li, pou\u017e\u00edv\u00e1me cache, \u010d\u00edm\u017e zvy\u0161ujeme dostupnost.<\/p>\n

\"Architektura
\n
\nCelkov\u011b existuj\u00ed dva p\u0159\u00edstupy k aplikaci Tarantool. Prvn\u00ed \u2013 vybudovat v\u0161echny cache na \u00farovni mikroslu\u017eeb.<\/b>Jak to ch\u00e1pu, t\u00edmto sm\u011brem jde VympelCom, kter\u00fd vytv\u00e1\u0159\u00ed cache klient\u016f.<\/p>\n

My jsme m\u00e9n\u011b z\u00e1visl\u00ed na dodavatel\u00edch, m\u011bn\u00edme j\u00e1dro BSS, proto m\u00e1me jednotnou kartot\u00e9ku klient\u016f ji\u017e z krabice. Ale chceme ji roz\u0161\u00ed\u0159it. Proto aplikujeme m\u00edrn\u011b jin\u00fd p\u0159\u00edstup \u2013 vytv\u00e1\u0159\u00edme cache uvnit\u0159 syst\u00e9m\u016f.<\/b>.<\/p>\n

Tak je m\u00edn\u011bn men\u0161\u00ed desynchronizace \u2013 jeden syst\u00e9m odpov\u00edd\u00e1 jak za cache, tak za hlavn\u00ed master zdroj.<\/p><\/blockquote>\n

\nTento zp\u016fsob se dob\u0159e hod\u00ed do p\u0159\u00edstupu Tarantool s transak\u010dn\u00edm skeletonem, kdy se aktualizuj\u00ed pouze \u010d\u00e1sti, kter\u00e9 se t\u00fdkaj\u00ed aktualizac\u00ed, tedy zm\u011bny dat. V\u0161echno ostatn\u00ed lze uchov\u00e1vat n\u011bkde jinde. Nen\u00ed tu obrovsk\u00e9 datov\u00e9 jezero, ne\u0159\u00edzen\u00e1 glob\u00e1ln\u00ed cache. Cache jsou navrhov\u00e1ny pro syst\u00e9m, bu\u010f podle produkt\u016f, nebo podle klient\u016f, nebo aby usnadnily \u017eivot \u00fadr\u017eb\u011b. Kdy\u017e vol\u00e1 zklaman\u00fd abonent ohledn\u011b kvality, chceme ho kvalitn\u011b obslou\u017eit.<\/p>\n

RTO a RPO<\/h2>\n

\nV IT existuj\u00ed dva term\u00edny \u2013 RTO<\/b> a\u00a0RPO<\/b>. <\/p>\n

Recovery time objective<\/b>\u00a0\u2014 to je doba obnovy slu\u017eby po selh\u00e1n\u00ed. RTO = 0 znamen\u00e1, \u017ee i kdy\u017e n\u011bco sel\u017ee, slu\u017eba pokra\u010duje v provozu.<\/p>\n

C\u00edlov\u00fd c\u00edl obnovy<\/b>\u00a0\u2014 to je doba obnovy dat, kolik dat m\u016f\u017eeme ztratit za ur\u010dit\u00e9 \u010dasov\u00e9 obdob\u00ed. RPO = 0 znamen\u00e1, \u017ee neztr\u00e1c\u00edme \u017e\u00e1dn\u00e1 data.<\/p>\n

\u00daloha pro Tarantool<\/h2>\n

\nPoj\u010fme se pokusit vy\u0159e\u0161it \u00falohu pro Tarantool.<\/p>\n

D\u00e1no<\/b>: v\u0161em zn\u00e1m\u00fd ko\u0161\u00edk \u017e\u00e1dost\u00ed, nap\u0159\u00edklad na Amazonu nebo kdekoli jinde. Po\u017eaduje se<\/b> aby ko\u0161\u00edk fungoval 24 hodin 7 dn\u00ed v t\u00fddnu, tedy 99,99 % \u010dasu. Objedn\u00e1vky, kter\u00e9 k n\u00e1m p\u0159ich\u00e1zej\u00ed, mus\u00ed zachovat po\u0159\u00e1dek, proto\u017ee nem\u016f\u017eeme chaoticky zap\u00ednat nebo vyp\u00ednat spojen\u00ed abonent\u016fm \u2014 v\u0161e mus\u00ed b\u00fdt p\u0159\u00edsn\u011b sekven\u010dn\u00ed. P\u0159edchoz\u00ed p\u0159edplatn\u00e9 ovliv\u0148uje n\u00e1sleduj\u00edc\u00ed, proto jsou data d\u016fle\u017eit\u00e1 \u2014 nic nesm\u00ed zmizet.<\/p>\n

\u0158e\u0161en\u00ed<\/b>. M\u016f\u017eeme se pokusit to \u0159e\u0161it p\u0159\u00edmo a zeptat se v\u00fdvoj\u00e1\u0159\u016f DB, ale \u00faloha se matematicky ned\u00e1 vy\u0159e\u0161it. M\u016f\u017eeme vzpomenout na teoremy, z\u00e1kony zachov\u00e1n\u00ed, kvantovou fyziku, ale pro\u010d \u2014 nen\u00ed to mo\u017en\u00e9 vy\u0159e\u0161it na \u00farovni DB.<\/p>\n

Zde funguje osv\u011bd\u010den\u00fd architektonick\u00fd p\u0159\u00edstup \u2014 je t\u0159eba dob\u0159e zn\u00e1t obor a za jeho \u00fa\u010det vy\u0159e\u0161it tuto h\u00e1danku.<\/p>\n

\"Architektura
\n
\nNa\u0161e \u0159e\u0161en\u00ed: vytv\u00e1\u0159\u00edme distribuovan\u00fd registr \u017e\u00e1dost\u00ed na Tarantool \u2014 geo-distribuovan\u00fd klastr<\/b>. Na sch\u00e9matu to jsou t\u0159i r\u016fzn\u00e9 datov\u00e9 centra \u2014 dv\u011b p\u0159ed Uralem, jedno za Uralem, a distribujeme v\u0161echny \u017e\u00e1dosti mezi t\u011bmito centry.<\/p>\n

Netflix, kter\u00fd je nyn\u00ed pova\u017eov\u00e1n za jednoho z l\u00eddr\u016f v IT, m\u011bl do roku 2012 jen jedno datov\u00e9 centrum. Na \u0160t\u011bdr\u00fd den 24. prosince toto datov\u00e9 centrum selhalo. U\u017eivatel\u00e9 v Kanad\u011b a USA z\u016fstali bez sv\u00fdch obl\u00edben\u00fdch film\u016f, byli velmi rozru\u0161en\u00ed a napsali o tom na soci\u00e1ln\u00ed s\u00edt\u011b. Nyn\u00ed m\u00e1 Netflix t\u0159i datov\u00e1 centra na z\u00e1padn\u00edm a v\u00fdchodn\u00edm pob\u0159e\u017e\u00ed a jedno v z\u00e1padn\u00ed Evrop\u011b. <\/p>\n

Od po\u010d\u00e1tku budujeme geo-distribuovan\u00e9 \u0159e\u0161en\u00ed \u2014 d\u016fle\u017eit\u00e1 je pro n\u00e1s odolnost proti selh\u00e1n\u00ed. <\/p><\/blockquote>\n

\nTak\u017ee m\u00e1me klastr, ale jak to ud\u011blat s RPO = 0 a RTO = 0? \u0158e\u0161en\u00ed je jednoduch\u00e9, to z\u00e1vis\u00ed na p\u0159edm\u011btu.<\/p>\n

Co je d\u016fle\u017eit\u00e9 v \u017e\u00e1dostech? Dv\u011b \u010d\u00e1sti: n\u00e1vrh ko\u0161\u00edku\u00a0P\u0158ED<\/b> rozhodnut\u00edm o koupi, a\u00a0PO<\/b>. \u010c\u00e1st P\u0158ED v telekomunikac\u00edch obvykle naz\u00fdv\u00e1me zachycov\u00e1n\u00ed objedn\u00e1vek<\/b> nebo vyjedn\u00e1v\u00e1n\u00ed objedn\u00e1vek<\/b>. V telekomunikac\u00edch to m\u016f\u017ee b\u00fdt mnohem slo\u017eit\u011bj\u0161\u00ed ne\u017e v internetov\u00e9m obchod\u011b, proto\u017ee je t\u0159eba obslou\u017eit z\u00e1kazn\u00edka, nab\u00eddnout 5 mo\u017enost\u00ed, a to v\u0161e prob\u00edh\u00e1 n\u011bjakou dobu, ale ko\u0161\u00edk se pln\u00ed. V tuto chv\u00edli m\u016f\u017ee doj\u00edt k chyb\u011b, ale to nen\u00ed tak hrozn\u00e9, proto\u017ee se to d\u011bje v interaktivn\u00edm re\u017eimu pod dohledem \u010dlov\u011bka. <\/p>\n

Pokud moskevsk\u00e9 datov\u00e9 centrum n\u00e1hle sel\u017ee, automaticky p\u0159epneme na jin\u00e9 datov\u00e9 centrum a budeme pokra\u010dovat v pr\u00e1ci. Teoreticky m\u016f\u017ee doj\u00edt ke ztr\u00e1t\u011b jednoho produktu v ko\u0161\u00edku, ale to vid\u00edte, znovu dopln\u00edte ko\u0161\u00edk a pokra\u010dujete. V tomto p\u0159\u00edpad\u011b je RTO = 0.<\/p>\n

Ve stejn\u00e9m okam\u017eiku existuje druh\u00e1 mo\u017enost: kdy\u017e stiskneme \u00abodeslat\u00bb, chceme, aby se data neztratila. Od tohoto okam\u017eiku za\u010dne fungovat automatika \u2013 to u\u017e je RPO = 0. Pou\u017eit\u00ed t\u011bchto dvou r\u016fzn\u00fdch vzor\u016f v jednom p\u0159\u00edpad\u011b m\u016f\u017ee b\u00fdt prost\u011b geograficky distribuovan\u00fd cluster s jedn\u00edm p\u0159ep\u00ednan\u00fdm mistrem, v jin\u00e9m p\u0159\u00edpad\u011b n\u011bjak\u00fd quorum z\u00e1znam. \u0160ablony se mohou li\u0161it, ale my \u0159e\u0161\u00edme probl\u00e9m.<\/p>\n

D\u00e1le, m\u00edt distribuovan\u00fd registr \u017e\u00e1dost\u00ed, m\u016f\u017eeme to v\u0161e i \u0161k\u00e1lovat - m\u00edt mnoho dispe\u010der\u016f a vykonavatel\u016f, kte\u0159\u00ed se obracej\u00ed na tento registr.<\/p>\n

\"Architektura
\n<\/p>\n

Cassandra a Tarantool spolu<\/h2>\n

\nExistuje je\u0161t\u011b jeden p\u0159\u00edpad - \u00abvitr\u00edna z\u016fstatk\u016f\u00bb<\/b>. Tady je pr\u00e1v\u011b zaj\u00edmav\u00fd p\u0159\u00edpad spole\u010dn\u00e9ho pou\u017eit\u00ed Cassandry a Tarantoolu.<\/p>\n

Pou\u017e\u00edv\u00e1me Cassandru, proto\u017ee 2 miliardy hovor\u016f denn\u011b \u2013 to nen\u00ed limit, a bude jich v\u00edce. Market\u00e9\u0159i r\u00e1di rozd\u011bluj\u00ed provoz podle zdroj\u016f, objevuje se st\u00e1le v\u00edce detail\u016f o soci\u00e1ln\u00edch s\u00edt\u00edch, nap\u0159\u00edklad. To v\u0161e zvy\u0161uje historii.<\/p>\n

Cassandra umo\u017e\u0148uje horizont\u00e1ln\u00ed \u0161k\u00e1lov\u00e1n\u00ed na jak\u00e9koli objemy.<\/p><\/blockquote>\n

\nC\u00edt\u00edme se komfortn\u011b s Cassandrou, ale m\u00e1 jeden probl\u00e9m - nen\u00ed dobr\u00e1 na \u010dten\u00ed. Na z\u00e1pisu je v\u0161e v po\u0159\u00e1dku, 30 000 za sekundu nen\u00ed probl\u00e9m - probl\u00e9m je v \u010dten\u00ed<\/b>.<\/p>\n

Proto se objevilo t\u00e9ma o cache a z\u00e1rove\u0148 jsme vy\u0159e\u0161ili dal\u0161\u00ed probl\u00e9m: existuje star\u00fd tradi\u010dn\u00ed p\u0159\u00edpad, kdy za\u0159\u00edzen\u00ed od p\u0159ep\u00edna\u010de od online tariface p\u0159ich\u00e1z\u00ed do soubor\u016f, kter\u00e9 nahr\u00e1v\u00e1me do Cassandry. Pot\u00fdkali jsme se s probl\u00e9mem spolehliv\u00e9ho nahr\u00e1v\u00e1n\u00ed t\u011bchto soubor\u016f, dokonce jsme pou\u017eili na radu IBM manager file transfer \u2013 existuj\u00ed takov\u00e1 \u0159e\u0161en\u00ed, kter\u00e1 efektivn\u011b \u0159\u00edd\u00ed p\u0159enos soubor\u016f pomoc\u00ed protokolu UDP, nap\u0159\u00edklad, a ne TCP. To je dobr\u00e9, ale st\u00e1le to trv\u00e1 minuty, a dokud to v\u0161echno nenahr\u00e1v\u00e1me, oper\u00e1tor v call centru nem\u016f\u017ee klientovi \u0159\u00edct, co se stalo s jeho z\u016fstatkem \u2013 je t\u0159eba \u010dekat.<\/p>\n

Aby se tomu zabr\u00e1nilo, my\u00a0pou\u017e\u00edv\u00e1me paraleln\u00ed funk\u010dn\u00ed rezervu<\/b>. Kdy\u017e pos\u00edl\u00e1me ud\u00e1lost p\u0159es Kafka do Tarantool, p\u0159epo\u010d\u00edt\u00e1v\u00e1me agreg\u00e1ty v re\u00e1ln\u00e9m \u010dase, nap\u0159\u00edklad za dne\u0161ek, a z\u00edsk\u00e1v\u00e1me cache z\u016fstatk\u016f<\/b>, kter\u00e1 m\u016f\u017ee dod\u00e1vat z\u016fstatky jakoukoli rychlost\u00ed, nap\u0159\u00edklad 100 tis\u00edc transakc\u00ed za sekundu a stejn\u00e9 2 sekundy.<\/p>\n

C\u00edlem je, aby po proveden\u00ed hovoru byl u\u017e za 2 sekundy v osobn\u00edm \u00fa\u010dtu nejen zm\u011bn\u011bn\u00fd z\u016fstatek, ale tak\u00e9 informace o tom, pro\u010d se zm\u011bnil.<\/p>\n

Z\u00e1v\u011br<\/h2>\n

\nTo byly p\u0159\u00edklady pou\u017eit\u00ed Tarantool. Velmi se n\u00e1m l\u00edbila otev\u0159enost Mail.ru, jejich ochota zva\u017eovat r\u016fzn\u00e9 p\u0159\u00edpady. <\/p>\n

Konzultant\u016fm z BCG nebo McKinsey, Accenture nebo IBM u\u017e je t\u011b\u017ek\u00e9 n\u00e1s n\u011b\u010d\u00edm nov\u00fdm p\u0159ekvapit \u2013 mnoho z toho, co nab\u00edzej\u00ed, u\u017e bu\u010f d\u011bl\u00e1me, nebo jsme ud\u011blali, nebo pl\u00e1nujeme ud\u011blat. Mysl\u00edm, \u017ee Tarantool v na\u0161em technologick\u00e9m stacku zaujme d\u016fstojn\u00e9 m\u00edsto a nahrad\u00ed mnoho ji\u017e existuj\u00edc\u00edch technologi\u00ed. Jsme ve f\u00e1zi aktivn\u00edho rozvoje tohoto projektu.<\/p>\n

P\u0159edn\u00e1\u0161ka Olega a Andrey je jednou z nejlep\u0161\u00edch na Tarantool Conference lo\u0148sk\u00e9ho roku, a u\u017e 17. \u010dervna Oleg Ivlev vystoup\u00ed na\u00a0T+ Conference 2019<\/a><\/noindex>\u00a0s p\u0159edn\u00e1\u0161kou \u201ePro\u010d Tarantool v Enterprise\u201c<\/a><\/noindex>. Tak\u00e9 od Megafonu vystoup\u00ed Alexander Deulin s p\u0159edn\u00e1\u0161kou \u201eCache Tarantool a replikace z Oracle\u201c<\/a><\/noindex>. Zjist\u00edme, co se zm\u011bnilo, jak\u00e9 pl\u00e1ny se poda\u0159ilo realizovat. P\u0159ipojte se \u2013 konference je zdarma, sta\u010d\u00ed se zaregistrovat<\/a><\/noindex>. V\u0161echny p\u0159edn\u00e1\u0161ky jsou p\u0159ijaty<\/a><\/noindex> a program konference je sestaven: nov\u00e9 p\u0159\u00edpady, nov\u00e9 zku\u0161enosti s pou\u017e\u00edv\u00e1n\u00edm Tarantool, architektura, enterprise, tutori\u00e1ly a mikroservisy.<\/p><\/blockquote>\n

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

\u0417\u0430\u0447\u0435\u043c \u0442\u0430\u043a\u043e\u0439 \u043a\u043e\u0440\u043f\u043e\u0440\u0430\u0446\u0438\u0438, \u043a\u0430\u043a \u041c\u0435\u0433\u0430\u0424\u043e\u043d, Tarantool \u0432\u00a0\u0431\u0438\u043b\u043b\u0438\u043d\u0433\u0435? \u0421\u043e \u0441\u0442\u043e\u0440\u043e\u043d\u044b \u043a\u0430\u0436\u0435\u0442\u0441\u044f, \u0447\u0442\u043e \u043e\u0431\u044b\u0447\u043d\u043e \u043f\u0440\u0438\u0445\u043e\u0434\u0438\u0442 \u0432\u0435\u043d\u0434\u043e\u0440, \u043f\u0440\u0438\u043d\u043e\u0441\u0438\u0442 \u043a\u0430\u043a\u0443\u044e-\u0442\u043e \u0431\u043e\u043b\u044c\u0448\u0443\u044e \u043a\u043e\u0440\u043e\u0431\u043a\u0443, \u0432\u0442\u044b\u043a\u0430\u0435\u0442 \u0448\u0442\u0435\u043a\u0435\u0440 \u0432\u00a0\u0440\u043e\u0437\u0435\u0442\u043a\u0443\u00a0\u2014 \u0432\u043e\u0442 \u0438\u00a0\u0431\u0438\u043b\u043b\u0438\u043d\u0433! \u041a\u043e\u0433\u0434\u0430-\u0442\u043e \u0442\u0430\u043a \u0438\u00a0\u0431\u044b\u043b\u043e, \u043d\u043e\u00a0\u0441\u0435\u0439\u0447\u0430\u0441 \u044d\u0442\u043e \u0430\u0440\u0445\u0430\u0438\u043a\u0430, \u0438\u00a0\u0442\u0430\u043a\u0438\u0435 \u0434\u0438\u043d\u043e\u0437\u0430\u0432\u0440\u044b \u0443\u0436\u0435 \u0432\u044b\u043c\u0435\u0440\u043b\u0438 \u0438\u043b\u0438 \u0432\u044b\u043c\u0438\u0440\u0430\u044e\u0442. \u0418\u0437\u043d\u0430\u0447\u0430\u043b\u044c\u043d\u043e \u0431\u0438\u043b\u043b\u0438\u043d\u0433 \u044d\u0442\u043e \u0441\u0438\u0441\u0442\u0435\u043c\u0430 \u0434\u043b\u044f \u0432\u044b\u0441\u0442\u0430\u0432\u043b\u0435\u043d\u0438\u044f \u0441\u0447\u0435\u0442\u043e\u0432\u00a0\u2014 \u0441\u0447\u0438\u0442\u0430\u043b\u043a\u0430 \u0438\u043b\u0438 \u043a\u0430\u043b\u044c\u043a\u0443\u043b\u044f\u0442\u043e\u0440. \u0412\u00a0\u0441\u043e\u0432\u0440\u0435\u043c\u0435\u043d\u043d\u043e\u043c \u0442\u0435\u043b\u0435\u043a\u043e\u043c\u0435\u00a0\u2014 \u044d\u0442\u043e \u0441\u0438\u0441\u0442\u0435\u043c\u0430 \u0430\u0432\u0442\u043e\u043c\u0430\u0442\u0438\u0437\u0430\u0446\u0438\u0438 \u0432\u0441\u0435\u0433\u043e \u0436\u0438\u0437\u043d\u0435\u043d\u043d\u043e\u0433\u043e \u0446\u0438\u043a\u043b\u0430 \u0432\u0437\u0430\u0438\u043c\u043e\u0434\u0435\u0439\u0441\u0442\u0432\u0438\u044f \u0441\u00a0\u0430\u0431\u043e\u043d\u0435\u043d\u0442\u043e\u043c […]<\/p>\n","protected":false,"gt_translate_keys":[{"key":"rendered","format":"html"}]},"author":1,"featured_media":28258,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[688],"tags":[],"class_list":["post-37650","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\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\udd47Architektura billingov\u00e9ho syst\u00e9mu nov\u00e9 generace: transformace s p\u0159echodem na Tarantool | ProHoster","description":"Pro\u010d pot\u0159ebuje takov\u00e1 korporace jako Megafon Tarantool v billingov\u00e9m syst\u00e9mu? Z vn\u011bj\u0161ku to vypad\u00e1, \u017ee dodavatel obvykle p\u0159inese n\u011bjakou velkou krabici, zapoj\u00ed ji do z\u00e1suvky \u2014 a je to!","canonical_url":"https:\/\/prohoster.info\/cs\/blog\/administrirovanie\/arhitektura-billinga-novogo-pokoleniya-transformatsiya-s-perehodom-na-tarantool","robots":"max-image-preview:large","keywords":"","webmasterTools":{"miscellaneous":""},"schema":null,"og:locale":"cs_CZ","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\u0410\u0440\u0445\u0438\u0442\u0435\u043a\u0442\u0443\u0440\u0430 \u0431\u0438\u043b\u043b\u0438\u043d\u0433\u0430 \u043d\u043e\u0432\u043e\u0433\u043e \u043f\u043e\u043a\u043e\u043b\u0435\u043d\u0438\u044f: \u0442\u0440\u0430\u043d\u0441\u0444\u043e\u0440\u043c\u0430\u0446\u0438\u044f \u0441 \u043f\u0435\u0440\u0435\u0445\u043e\u0434\u043e\u043c \u043d\u0430 Tarantool | ProHoster","og:description":"\u0417\u0430\u0447\u0435\u043c \u0442\u0430\u043a\u043e\u0439 \u043a\u043e\u0440\u043f\u043e\u0440\u0430\u0446\u0438\u0438, \u043a\u0430\u043a \u041c\u0435\u0433\u0430\u0424\u043e\u043d, Tarantool \u0432 \u0431\u0438\u043b\u043b\u0438\u043d\u0433\u0435? \u0421\u043e \u0441\u0442\u043e\u0440\u043e\u043d\u044b \u043a\u0430\u0436\u0435\u0442\u0441\u044f, \u0447\u0442\u043e \u043e\u0431\u044b\u0447\u043d\u043e \u043f\u0440\u0438\u0445\u043e\u0434\u0438\u0442 \u0432\u0435\u043d\u0434\u043e\u0440, \u043f\u0440\u0438\u043d\u043e\u0441\u0438\u0442 \u043a\u0430\u043a\u0443\u044e-\u0442\u043e \u0431\u043e\u043b\u044c\u0448\u0443\u044e \u043a\u043e\u0440\u043e\u0431\u043a\u0443, \u0432\u0442\u044b\u043a\u0430\u0435\u0442 \u0448\u0442\u0435\u043a\u0435\u0440 \u0432 \u0440\u043e\u0437\u0435\u0442\u043a\u0443 \u2014 \u0432\u043e\u0442 \u0438 \u0431\u0438\u043b\u043b\u0438\u043d\u0433!","og:url":"https:\/\/prohoster.info\/cs\/blog\/administrirovanie\/arhitektura-billinga-novogo-pokoleniya-transformatsiya-s-perehodom-na-tarantool","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-31T19:18:50+00:00","article:modified_time":"2019-10-31T19:18:50+00:00","article:publisher":"https:\/\/www.facebook.com\/prohoster","article:author":"https:\/\/www.facebook.com\/prohoster"},"aioseo_meta_data":{"post_id":"37650","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-23 18:44:19","breadcrumb_settings":null,"limit_modified_date":false,"reviewed_by":null,"ai":null,"created":"2021-03-01 01:23:06","updated":"2026-01-23 18:44:19","focus_keyword":null,"additional_keywords":null,"truseo_locale":null},"gt_translate_keys":[{"key":"link","format":"url"}],"_links":{"self":[{"href":"https:\/\/prohoster.info\/cs\/wp-json\/wp\/v2\/posts\/37650","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/prohoster.info\/cs\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/prohoster.info\/cs\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/prohoster.info\/cs\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/prohoster.info\/cs\/wp-json\/wp\/v2\/comments?post=37650"}],"version-history":[{"count":0,"href":"https:\/\/prohoster.info\/cs\/wp-json\/wp\/v2\/posts\/37650\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/prohoster.info\/cs\/wp-json\/wp\/v2\/media\/28258"}],"wp:attachment":[{"href":"https:\/\/prohoster.info\/cs\/wp-json\/wp\/v2\/media?parent=37650"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/prohoster.info\/cs\/wp-json\/wp\/v2\/categories?post=37650"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/prohoster.info\/cs\/wp-json\/wp\/v2\/tags?post=37650"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}