{"id":30792,"date":"2019-10-31T21:37:27","date_gmt":"2019-10-31T18:37:27","guid":{"rendered":"https:\/\/prohoster.info\/blog\/nash-opyt-sozdaniya-api-gateway\/"},"modified":"2019-10-31T21:37:27","modified_gmt":"2019-10-31T18:37:27","slug":"nash-opyt-sozdaniya-api-gateway","status":"publish","type":"post","link":"https:\/\/prohoster.info\/sk\/blog\/administrirovanie\/nash-opyt-sozdaniya-api-gateway","title":{"rendered":"Na\u0161a sk\u00fasenos\u0165 s vytvoren\u00edm API Gateway","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"<p>Niektor\u00e9 spolo\u010dnosti, vr\u00e1tane na\u0161ich klientov, rozv\u00edjaj\u00fa produkt prostredn\u00edctvom partnerskej siete. Napr\u00edklad ve\u013ek\u00e9 internetov\u00e9 obchody s\u00fa integrovan\u00e9 so slu\u017ebou doru\u010denia \u2014 objedn\u00e1vate si tovar a \u010doskoro dostanete sledovacie \u010d\u00edslo z\u00e1sielky. \u010eal\u0161\u00edm pr\u00edkladom je, \u017ee spolu s letenkou si zak\u00fapite poistenie alebo l\u00edstok na aerotrain.<\/p>\n<p>Na tento \u00fa\u010del sa pou\u017e\u00edva jeden API, ktor\u00fd je potrebn\u00e9 poskytn\u00fa\u0165 partnerom prostredn\u00edctvom API Gateway. Tento \u00fakol sme sa rozhodli vyrie\u0161i\u0165. V tomto \u010dl\u00e1nku sa podel\u00edme o podrobnosti.<\/p>\n<p>M\u00e1me: ekosyst\u00e9m a API port\u00e1l s rozhran\u00edm, na ktorom s\u00fa zaregistrovan\u00ed pou\u017e\u00edvatelia, z\u00edskavaj\u00fa inform\u00e1cie at\u010f. Potrebujeme urobi\u0165 pohodln\u00fd a spo\u013eahliv\u00fd API Gateway. V procese mus\u00edme zabezpe\u010di\u0165 <\/p>\n<ul>\n<li>registr\u00e1ciu, <\/li>\n<li>kontrolu pripojenia k API, <\/li>\n<li>monitorovanie toho, ako pou\u017e\u00edvatelia vyu\u017e\u00edvaj\u00fa koncov\u00fa syst\u00e9m, <\/li>\n<li>sledovanie obchodn\u00fdch ukazovate\u013eov.<\/li>\n<\/ul>\n<p>\n<img decoding=\"async\" alt=\"Na\u0161a sk\u00fasenos\u0165 s vytvoren\u00edm API Gateway\" src=\"\/wp-content\/uploads\/2019\/04\/4fa66fd4573af16b0bc78aa61173f907.png\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<br \/>\nV \u010dl\u00e1nku sa podel\u00edme o na\u0161e sk\u00fasenosti s vytv\u00e1ran\u00edm API Gateway, pri ktorom sme rie\u0161ili nasleduj\u00face \u00falohy:<\/p>\n<ul>\n<li>autentifik\u00e1ciu pou\u017e\u00edvate\u013ea,<\/li>\n<li>autoriz\u00e1ciu pou\u017e\u00edvate\u013ea,<\/li>\n<li>modifik\u00e1ciu p\u00f4vodn\u00e9ho dopytu,<\/li>\n<li>proxy dopytu,<\/li>\n<li>postprocessing odpovede.<\/li>\n<\/ul>\n<p>\n<noindex><a rel=\"nofollow\" name=\"habracut\"><\/a><\/noindex><br \/>\nExistuj\u00fa dva typy spr\u00e1vy API:<\/p>\n<p>1. \u0160tandardn\u00fd, ktor\u00fd funguje nasleduj\u00facim sp\u00f4sobom. Pred pripojen\u00edm si pou\u017e\u00edvate\u013e testuje mo\u017enosti, potom plat\u00ed a integruje na svoju str\u00e1nku. Naj\u010dastej\u0161ie sa pou\u017e\u00edva v malom a strednom podnikan\u00ed.<\/p>\n<p>2. Ve\u013ek\u00fd B2B API Management, ke\u010f spolo\u010dnos\u0165 najsk\u00f4r prijme obchodn\u00e9 rozhodnutie o pripojen\u00ed, stane sa partnerom spolo\u010dnosti s zmluvnou povinnos\u0165ou, po \u010dom sa pripoj\u00ed k API. A a\u017e po vybaven\u00ed v\u0161etk\u00fdch form\u00e1lnost\u00ed spolo\u010dnos\u0165 dostane testovac\u00ed pr\u00edstup, podst\u00fapi testovanie a prejde do produkcie. Ale to nie je mo\u017en\u00e9 bez riadiaceho rozhodnutia o pripojen\u00ed. <\/p>\n<p><img decoding=\"async\" alt=\"Na\u0161a sk\u00fasenos\u0165 s vytvoren\u00edm API Gateway\" src=\"\/wp-content\/uploads\/2019\/04\/b9ab53d6c64d5a971c4950cd340ad42e.png\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<\/p>\n<h3> Na\u0161e rie\u0161enie<\/h3>\n<p>\nV tejto \u010dasti sa podel\u00edme o vytv\u00e1ranie API Gateway.<\/p>\n<p>Kone\u010dn\u00ed pou\u017e\u00edvatelia vytv\u00e1ran\u00e9ho API Gateway s\u00fa partneri n\u00e1\u0161ho klienta. Pre ka\u017ed\u00e9ho z nich u\u017e m\u00e1me ulo\u017een\u00e9 potrebn\u00e9 zmluvy. Budeme musie\u0165 len roz\u0161\u00edri\u0165 funkcionalitu, pri\u010dom ozna\u010d\u00edme poskytnut\u00fd pr\u00edstup k gateway. To si vy\u017eaduje kontrolovan\u00fd proces pripojenia a spr\u00e1vy.<\/p>\n<p>Samozrejme, bolo by mo\u017en\u00e9 vybra\u0165 nejak\u00e9 hotov\u00e9 rie\u0161enie pre spr\u00e1vu API a vytv\u00e1ranie API Gateway konkr\u00e9tne. Napr\u00edklad to mohlo by\u0165<noindex><a rel=\"nofollow\" href=\"https:\/\/docs.microsoft.com\/en-us\/azure\/api-management\/\"> Azure API Management<\/a><\/noindex>Pre n\u00e1s to nebolo vhodn\u00e9, preto\u017ee v na\u0161om pr\u00edpade sme u\u017e mali API port\u00e1l a obrovsk\u00fd ekosyst\u00e9m vybudovan\u00fd okolo neho. V\u0161etci pou\u017e\u00edvatelia boli u\u017e zaregistrovan\u00ed, vedeli, kde a ako m\u00f4\u017eu z\u00edska\u0165 potrebn\u00e9 inform\u00e1cie. V API port\u00e1li u\u017e existovali potrebn\u00e9 rozhrania, potrebovali sme len API Gateway. Na jeho v\u00fdvoji sme sa vlastne aj podie\u013eali. <\/p>\n<p>To, \u010do naz\u00fdvame API Gateway, je ak\u00fdsi proxy. Aj tu sme mali na v\u00fdber \u2014 mohli sme nap\u00edsa\u0165 svoj vlastn\u00fd proxy, alebo si vybra\u0165 nie\u010do u\u017e hotov\u00e9. V tomto pr\u00edpade sme zvolili druh\u00fa cestu a vybrali kombin\u00e1ciu nginx+Lua. Pre\u010do? Potrebovali sme spo\u013eahliv\u00fd, testovan\u00fd softv\u00e9r, ktor\u00fd podporuje \u0161k\u00e1lovanie. Nechceli sme po implement\u00e1cii testova\u0165 a overova\u0165 spr\u00e1vnos\u0165 obchodnej logiky a spr\u00e1vnos\u0165 fungovania proxy. <\/p>\n<p>Ka\u017ed\u00fd webov\u00fd server m\u00e1 potrubie na spracovanie po\u017eiadaviek. V pr\u00edpade nginx vyzer\u00e1 nasledovne:<\/p>\n<p><img decoding=\"async\" alt=\"Na\u0161a sk\u00fasenos\u0165 s vytvoren\u00edm API Gateway\" src=\"\/wp-content\/uploads\/2019\/04\/b4cba1d37cc769202f92df052b45c77e.png\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<br \/>\n(sch\u00e9ma z <noindex><a rel=\"nofollow\" href=\"https:\/\/github.com\/openresty\/lua-nginx-module\">GitHub Lua Nginx<\/a><\/noindex>)<\/p>\n<p>Na\u0161\u00edm cie\u013eom bolo integrova\u0165 sa do tohto potrubia v momente, ke\u010f m\u00f4\u017eeme modifikova\u0165 p\u00f4vodn\u00fa po\u017eiadavku. <\/p>\n<p>Chceme vytvori\u0165 transparentn\u00fd proxy, aby po\u017eiadavka zostala tak\u00e1, ak\u00e1 pri\u0161la. Len kontrolujeme pr\u00edstup k kone\u010dn\u00e9mu API, pom\u00e1hame po\u017eiadavke dosta\u0165 sa k nemu. V pr\u00edpade, \u017ee po\u017eiadavka bola nespr\u00e1vna, chybu m\u00e1 nahl\u00e1si\u0165 kone\u010dn\u00e9 API, nie my. Jedin\u00fdm d\u00f4vodom, pre ktor\u00fd m\u00f4\u017eeme odmietnu\u0165 po\u017eiadavku, je nedostatok pr\u00edstupu pre klienta. <\/p>\n<p>Pre nginx u\u017e existuje <noindex><a rel=\"nofollow\" href=\"https:\/\/github.com\/openresty\/lua-nginx-module\">roz\u0161\u00edrenie<\/a><\/noindex> na <noindex><a rel=\"nofollow\" href=\"http:\/\/www.lua.ru\/\">Lua<\/a><\/noindex>. Lua je skriptovac\u00ed jazyk, je ve\u013emi \u013eahk\u00fd a jednoducho sa osvojite\u013en\u00fd. Tak\u00fdmto sp\u00f4sobom sme potrebn\u00fa logiku implementovali pomocou Lua. <\/p>\n<p>Konfigur\u00e1cia nginxu (anal\u00f3gia s routou aplik\u00e1cie), kde sa vykon\u00e1va cel\u00e1 pr\u00e1ca, je celkom zrozumite\u013en\u00e1. Pozoruhodn\u00e1 je posledn\u00e1 direkt\u00edva \u2014 post_action.<\/p>\n<pre><code class=\"nginx\">location \/middleware {\n      more_clear_input_headers Accept-Encoding;\n      lua_need_request_body on;\n      rewrite_by_lua_file 'middleware\/rewrite.lua';\n      access_by_lua_file 'middleware\/access.lua';\n      proxy_pass https:\/\/someurl.com;\n      body_filter_by_lua_file 'middleware\/body_filter.lua';\n      post_action \/process_session;\n}\n<\/code><\/pre>\n<p>\nPozrime sa, \u010do sa deje v tejto konfigur\u00e1cii: <br \/>\n<b>more_clear_input_headers<\/b> \u2014 \u010dist\u00ed hodnotu uveden\u00fdch hlavi\u010diek po direkt\u00edve. <br \/>\n<b>lua_need_request_body <\/b>\u2014 reguluje, \u010di m\u00e1 by\u0165 pred vykonan\u00edm direkt\u00edv rewrite\/access\/access_by_lua pre\u010d\u00edtan\u00e9 p\u00f4vodn\u00e9 telo po\u017eiadavky. Predvolene nginx ne\u010d\u00edta telo po\u017eiadavky klienta a ak potrebujete k nemu z\u00edska\u0165 pr\u00edstup, t\u00e1to direkt\u00edva by mala ma\u0165 hodnotu on.<br \/>\n<b>rewrite_by_lua_file<\/b> \u2014 cesta k skriptu, kde je op\u00edsan\u00e1 logika na modifik\u00e1ciu po\u017eiadavky<br \/>\n<b>access_by_lua_file <\/b>\u2014 cesta k skriptu, kde je op\u00edsan\u00e1 logika, ktor\u00e1 kontroluje pr\u00edstup k zdroju. <br \/>\n<b>proxy_pass <\/b>\u2014 url, na ktor\u00fd bude po\u017eiadavka proxyvan\u00e1.<br \/>\n<b>body_filter_by_lua_file <\/b>\u2014 cesta k skriptu, kde je op\u00edsan\u00e1 logika na filtrovanie po\u017eiadavky pred jej vr\u00e1ten\u00edm klientovi.<br \/>\nA nakoniec, <b>post_action<\/b> \u2014 ofici\u00e1lne nedokumentovan\u00e1 direkt\u00edva, pomocou ktorej je mo\u017en\u00e9 vykon\u00e1va\u0165 e\u0161te \u010fal\u0161ie akcie po tom, ako je odpove\u010f odovzdan\u00e1 klientovi. <\/p>\n<p>Teraz sa postupne porozpr\u00e1vame, ako sme rie\u0161ili svoje \u00falohy.<\/p>\n<h3>Autoriz\u00e1cia\/audifik\u00e1cia a modifik\u00e1cia po\u017eiadavky<\/h3>\n<p>\n<b>Autoriz\u00e1cia<\/b><\/p>\n<p>Autoriz\u00e1ciu a autentifik\u00e1ciu sme postavili pomocou pr\u00edstupov na z\u00e1klade certifik\u00e1tu. Existuje kore\u0148ov\u00fd certifik\u00e1t. Ka\u017ed\u00e9mu nov\u00e9mu klientovi z\u00e1kazn\u00edka je generovan\u00fd jeho osobn\u00fd certifik\u00e1t, s ktor\u00fdm m\u00f4\u017ee z\u00edska\u0165 pr\u00edstup k API. Tento certifik\u00e1t je nastaven\u00fd v sekcii server konfigur\u00e1ci\u00ed nginx.<\/p>\n<pre><code class=\"nginx\">ssl on;\nssl_certificate \/usr\/local\/openresty\/nginx\/ssl\/cert.pem;\nssl_certificate_key \/usr\/local\/openresty\/nginx\/ssl\/cert.pem;\nssl_client_certificate \/usr\/local\/openresty\/nginx\/ssl\/ca.crt;\nssl_verify_client on;<\/code><\/pre>\n<p>\n<b>Modifik\u00e1cia<\/b><\/p>\n<p>M\u00f4\u017ee sa objavi\u0165 spravodliv\u00e1 ot\u00e1zka: \u010do robi\u0165 so certifikovan\u00fdm klientom, ak sme n\u00e1hle chceli jeho odpojenie zo syst\u00e9mu? Predsa nebudeme znovu vyd\u00e1va\u0165 certifik\u00e1ty pre v\u0161etk\u00fdch ostatn\u00fdch klientov. <\/p>\n<p>Tak sme pomaly pre\u0161li k \u010fal\u0161ej \u00falohe \u2014 modifik\u00e1cii p\u00f4vodnej po\u017eiadavky. P\u00f4vodn\u00e1 po\u017eiadavka klienta, celkom povedan\u00e9, nie je platn\u00e1 pre kone\u010dn\u00fd syst\u00e9m. Jednou z \u00faloh je dop\u00edsa\u0165 do po\u017eiadavky ch\u00fdbaj\u00face \u010dasti, aby bola platn\u00e1. Z\u00e1kladom je, \u017ee ch\u00fdbaj\u00face \u00fadaje s\u00fa r\u00f4zne pre ka\u017ed\u00e9ho klienta. Vieme, \u017ee klient k n\u00e1m prich\u00e1dza s certifik\u00e1tom, z ktor\u00e9ho m\u00f4\u017eeme z\u00edska\u0165 otla\u010dok a vytiahnu\u0165 potrebn\u00e9 \u00fadaje o klientovi z datab\u00e1zy. <\/p>\n<p>Ak by v nejakom momente bolo potrebn\u00e9 odpoji\u0165 klienta od na\u0161ich slu\u017eieb, jeho \u00fadaje zmizn\u00fa z datab\u00e1zy a ni\u010d nebude m\u00f4c\u0165 robi\u0165. <\/p>\n<h3>Pr\u00e1ca s \u00fadajmi klienta<\/h3>\n<p>\nMuseli sme zabezpe\u010di\u0165 vysok\u00fa dostupnos\u0165 rie\u0161enia, najm\u00e4 toho, ako z\u00edskavame \u00fadaje klienta. Zlo\u017eitos\u0165 spo\u010d\u00edva v tom, \u017ee prim\u00e1rny zdroj t\u00fdchto \u00fadajov je tretia strana, ktor\u00e1 nezaru\u010duje bezprobl\u00e9mov\u00fa a dostato\u010dne vysok\u00fa r\u00fdchlos\u0165 pr\u00e1ce. <\/p>\n<p>Preto sme museli zabezpe\u010di\u0165 vysok\u00fa dostupnos\u0165 \u00fadajov klientov. Ako n\u00e1stroj sme vybrali <noindex><a rel=\"nofollow\" href=\"https:\/\/hazelcast.org\/\">Hazelcast<\/a><\/noindex>, ktor\u00fd n\u00e1m poskytuje:<\/p>\n<ul>\n<li>r\u00fdchly pr\u00edstup k \u00fadajom,<\/li>\n<li>mo\u017enos\u0165 usporiada\u0165 klaster z viacer\u00fdch uzlov s replikovan\u00fdmi na r\u00f4znych uzloch d\u00e1tami.<\/li>\n<\/ul>\n<p>\nRozhodli sme sa pre najjednoduch\u0161iu strat\u00e9giu dod\u00e1vania d\u00e1t do cache:<\/p>\n<p><img decoding=\"async\" alt=\"Na\u0161a sk\u00fasenos\u0165 s vytvoren\u00edm API Gateway\" src=\"\/wp-content\/uploads\/2019\/04\/0175d6f0fda543566ab13d4cae9d8cc1.png\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<br \/>\nPr\u00e1ca s kone\u010dn\u00fdm syst\u00e9mom prebieha v r\u00e1mci rel\u00e1ci\u00ed a je tu limit na maxim\u00e1lny po\u010det. Ak v\u0161ak klient neskon\u010dil rel\u00e1ciu, mus\u00edme to urobi\u0165 my. <\/p>\n<p>\u00dadaje o otvorenej rel\u00e1cii prich\u00e1dzaj\u00fa od kone\u010dn\u00e9ho syst\u00e9mu a spo\u010diatku sa spracov\u00e1vaj\u00fa na strane Lua. Rozhodli sme sa pou\u017ei\u0165 Hazelcast na uchov\u00e1vanie t\u00fdchto d\u00e1t pomocou jobu naprogramovan\u00e9ho v .NET. Potom pravidelne kontrolujeme pr\u00e1vo na \u017eivot otvoren\u00fdch rel\u00e1ci\u00ed a uzatv\u00e1rame vypr\u0161an\u00e9. <\/p>\n<h3>Pr\u00edstup k Hazelcast je mo\u017en\u00fd z Lua aj z .NET.<\/h3>\n<p>\nKlienti na Lua na pr\u00e1cu s Hazelcast neexistuj\u00fa, ale Hazelcast m\u00e1 REST API, ktor\u00e9 sme sa rozhodli vyu\u017ei\u0165. Pre .NET je dostupn\u00fd <noindex><a rel=\"nofollow\" href=\"https:\/\/hazelcast.org\/clients\/net\/\">sa dostal do backendu.<\/a><\/noindex>, cez ktor\u00fd sme pl\u00e1novali z\u00edska\u0165 pr\u00edstup k d\u00e1tam Hazelcast na strane .NET. Ale nebolo to tak\u00e9 jednoduch\u00e9.<\/p>\n<p><img decoding=\"async\" alt=\"Na\u0161a sk\u00fasenos\u0165 s vytvoren\u00edm API Gateway\" src=\"\/wp-content\/uploads\/2019\/04\/52c9437e5cd16073b56afc55a4f415da.png\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<br \/>\nPri uchov\u00e1van\u00ed d\u00e1t cez REST a ich z\u00edskavan\u00ed cez .NET klienta sa pou\u017e\u00edvaj\u00fa r\u00f4zne serializ\u00e1tory a deserializ\u00e1tory. Preto nie je mo\u017en\u00e9 ulo\u017ei\u0165 d\u00e1ta cez REST a z\u00edska\u0165 ich cez .NET klienta a naopak. <\/p>\n<p>Ak bud\u00fa z\u00e1ujemcovia, podrobnej\u0161ie sa o tomto probl\u00e9me dozviete v samostatnom \u010dl\u00e1nku. Spoiler \u2014 na sch\u00e9me. <\/p>\n<p><img decoding=\"async\" alt=\"Na\u0161a sk\u00fasenos\u0165 s vytvoren\u00edm API Gateway\" src=\"\/wp-content\/uploads\/2019\/04\/73bb11214fdaeca86ef10cdbd788e288.png\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<\/p>\n<h3>Logovanie a monitoring<\/h3>\n<p>\nN\u00e1\u0161 firemn\u00fd \u0161tandard pre logovanie cez .NET \u2014 Serilog, v\u0161etky logy nakoniec kon\u010dia v Elasticsearch, ich anal\u00fdzu vykon\u00e1vame cez Kibana. Nie\u010do podobn\u00e9 sme chceli dosiahnu\u0165 aj v tomto pr\u00edpade. Jedin\u00fd <noindex><a rel=\"nofollow\" href=\"https:\/\/github.com\/DhavalKapil\/elasticsearch-lua\">sa dostal do backendu.<\/a><\/noindex> n\u00e1stroj na pr\u00e1cu s Elastic na Lua, ktor\u00fd bol n\u00e1jden\u00fd, sa rozbil pri prvom require. A tak sme pou\u017eili Fluentd. <\/p>\n<p><noindex><a rel=\"nofollow\" href=\"https:\/\/www.fluentd.org\/\">Fluentd<\/a><\/noindex> \u2014 open source rie\u0161enie na zabezpe\u010denie jednotnej vrstvy logovania aplik\u00e1cie. Umo\u017e\u0148uje zbiera\u0165 logy z r\u00f4znych vrstiev aplik\u00e1cie a n\u00e1sledne ich pren\u00e1\u0161a\u0165 do jedn\u00e9ho zdroja. <\/p>\n<p>API Gateway be\u017e\u00ed v K8S, preto sme sa rozhodli prida\u0165 kontajner s Fluentd do tej istej pody, aby sme mohli zapisova\u0165 logy do existuj\u00faceho otvoren\u00e9ho tcp portu Fluentd. <\/p>\n<p>Rovnako sme sk\u00famali, ako sa Fluentd spr\u00e1va, ak nem\u00e1 spojenie s Elasticsearch. Po\u010das dvoch dn\u00ed do br\u00e1ny nepretr\u017eite prich\u00e1dzali po\u017eiadavky, do Fluentd sa posielali logy, ale IP Elastic bol zablokovan\u00fd. Po obnoven\u00ed spojenia Fluentd skvele preniesol v\u0161etky logy do Elastic.<\/p>\n<h3>Z\u00e1ver<\/h3>\n<p>\nZvolen\u00fd pr\u00edstup k implement\u00e1cii n\u00e1m umo\u017enil doda\u0165 skuto\u010dne funk\u010dn\u00fd produkt do prev\u00e1dzky za pouh\u00fdch 2,5 mesiaca.<\/p>\n<p>Ak raz budete musie\u0165 rie\u0161i\u0165 podobn\u00e9 veci, odpor\u00fa\u010dame v\u00e1m najprv jasne pochopi\u0165, ak\u00fa \u00falohu rie\u0161ite a ak\u00e9 zdroje u\u017e m\u00e1te k dispoz\u00edcii. Bu\u010fte pozorn\u00ed k zlo\u017eitostiam integr\u00e1cie s existuj\u00facimi syst\u00e9mami spr\u00e1vy API. <\/p>\n<p>Ujasnite si, \u010do presne pl\u00e1nujete vyvin\u00fa\u0165 \u2014 iba obchodn\u00fa logiku spracovania po\u017eiadaviek alebo, ako to bolo v na\u0161om pr\u00edpade, cel\u00fd proxy server. Nezab\u00fadajte, \u017ee v\u0161etko, \u010do si vytvor\u00edte sami, by malo by\u0165 n\u00e1sledne d\u00f4kladne otestovan\u00e9.<br \/>\n<br \/>Zdroj: <a content=\"nofollow\" rel=\"nofollow\" href=\"https:\/\/habr.com\/ru\/company\/true_engineering\/blog\/446438\/\">habr.com<\/a><\/p>","protected":false,"gt_translate_keys":[{"key":"rendered","format":"html"}]},"excerpt":{"rendered":"<p>\u041d\u0435\u043a\u043e\u0442\u043e\u0440\u044b\u0435 \u043a\u043e\u043c\u043f\u0430\u043d\u0438\u0438, \u0432 \u0442\u043e\u043c \u0447\u0438\u0441\u043b\u0435 \u043d\u0430\u0448 \u0437\u0430\u043a\u0430\u0437\u0447\u0438\u043a, \u0440\u0430\u0437\u0432\u0438\u0432\u0430\u044e\u0442 \u043f\u0440\u043e\u0434\u0443\u043a\u0442 \u0447\u0435\u0440\u0435\u0437 \u043f\u0430\u0440\u0442\u043d\u0435\u0440\u0441\u043a\u0443\u044e \u0441\u0435\u0442\u044c. \u041d\u0430\u043f\u0440\u0438\u043c\u0435\u0440, \u043a\u0440\u0443\u043f\u043d\u044b\u0435 \u0438\u043d\u0442\u0435\u0440\u043d\u0435\u0442-\u043c\u0430\u0433\u0430\u0437\u0438\u043d\u044b \u0438\u043d\u0442\u0435\u0433\u0440\u0438\u0440\u043e\u0432\u0430\u043d\u044b \u0441\u043e \u0441\u043b\u0443\u0436\u0431\u043e\u0439 \u0434\u043e\u0441\u0442\u0430\u0432\u043a\u0438 \u2014 \u0432\u044b \u0437\u0430\u043a\u0430\u0437\u044b\u0432\u0430\u0435\u0442\u0435 \u0442\u043e\u0432\u0430\u0440 \u0438 \u0432\u0441\u043a\u043e\u0440\u0435 \u043f\u043e\u043b\u0443\u0447\u0430\u0435\u0442\u0435 \u0442\u0440\u0435\u043a\u0438\u043d\u0433\u043e\u0432\u044b\u0439 \u043d\u043e\u043c\u0435\u0440 \u043f\u043e\u0441\u044b\u043b\u043a\u0438. \u0414\u0440\u0443\u0433\u043e\u0439 \u043f\u0440\u0438\u043c\u0435\u0440 \u2014 \u0432\u043c\u0435\u0441\u0442\u0435 \u0441 \u0430\u0432\u0438\u0430\u0431\u0438\u043b\u0435\u0442\u043e\u043c \u0432\u044b \u043f\u043e\u043a\u0443\u043f\u0430\u0435\u0442\u0435 \u0441\u0442\u0440\u0430\u0445\u043e\u0432\u043a\u0443 \u0438\u043b\u0438 \u0431\u0438\u043b\u0435\u0442 \u043d\u0430 \u0430\u044d\u0440\u043e\u044d\u043a\u0441\u043f\u0440\u0435\u0441\u0441. \u0414\u043b\u044f \u044d\u0442\u043e\u0433\u043e \u0438\u0441\u043f\u043e\u043b\u044c\u0437\u0443\u0435\u0442\u0441\u044f \u043e\u0434\u0438\u043d API, \u043a\u043e\u0442\u043e\u0440\u044b\u0439 \u043d\u0443\u0436\u043d\u043e \u0432\u044b\u0434\u0430\u0442\u044c \u043f\u0430\u0440\u0442\u043d\u0435\u0440\u0430\u043c \u0447\u0435\u0440\u0435\u0437 API Gateway. \u042d\u0442\u0443 [&hellip;]<\/p>\n","protected":false,"gt_translate_keys":[{"key":"rendered","format":"html"}]},"author":1,"featured_media":22777,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[688],"tags":[],"class_list":["post-30792","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-administrirovanie"],"aioseo_notices":[],"aioseo_head":"\n\t\t<!-- All in One SEO 5.0.4 - aioseo.com -->\n\t<meta name=\"description\" content=\"\u041d\u0435\u043a\u043e\u0442\u043e\u0440\u044b\u0435 \u043a\u043e\u043c\u043f\u0430\u043d\u0438\u0438, \u0432 \u0442\u043e\u043c \u0447\u0438\u0441\u043b\u0435 \u043d\u0430\u0448 \u0437\u0430\u043a\u0430\u0437\u0447\u0438\u043a, \u0440\u0430\u0437\u0432\u0438\u0432\u0430\u044e\u0442 \u043f\u0440\u043e\u0434\u0443\u043a\u0442 \u0447\u0435\u0440\u0435\u0437 \u043f\u0430\u0440\u0442\u043d\u0435\u0440\u0441\u043a\u0443\u044e \u0441\u0435\u0442\u044c.\" \/>\n\t<meta name=\"robots\" content=\"max-image-preview:large\" \/>\n\t<meta name=\"author\" content=\"Yuri Gagarin\"\/>\n\t<link rel=\"canonical\" href=\"https:\/\/prohoster.info\/sk\/blog\/administrirovanie\/nash-opyt-sozdaniya-api-gateway\" \/>\n\t\t<meta name=\"generator\" content=\"All in One SEO (AIOSEO) 5.0.4\" \/>\n\t\t<meta property=\"og:locale\" content=\"sk_SK\" \/>\n\t\t<meta property=\"og:site_name\" content=\"ProHoster | \u041a\u0443\u043f\u0438\u0442\u044c \u043d\u0430\u0434\u0435\u0436\u043d\u044b\u0439 \u0445\u043e\u0441\u0442\u0438\u043d\u0433 \u0434\u043b\u044f \u0441\u0430\u0439\u0442\u043e\u0432 \u0441 \u0437\u0430\u0449\u0438\u0442\u043e\u0439 \u043e\u0442 DDoS, VPS VDS \u0441\u0435\u0440\u0432\u0435\u0440\u044b\" \/>\n\t\t<meta property=\"og:type\" content=\"article\" \/>\n\t\t<meta property=\"og:title\" content=\"\ud83e\udd47\u041d\u0430\u0448 \u043e\u043f\u044b\u0442 \u0441\u043e\u0437\u0434\u0430\u043d\u0438\u044f API Gateway | ProHoster\" \/>\n\t\t<meta property=\"og:description\" content=\"\u041d\u0435\u043a\u043e\u0442\u043e\u0440\u044b\u0435 \u043a\u043e\u043c\u043f\u0430\u043d\u0438\u0438, \u0432 \u0442\u043e\u043c \u0447\u0438\u0441\u043b\u0435 \u043d\u0430\u0448 \u0437\u0430\u043a\u0430\u0437\u0447\u0438\u043a, \u0440\u0430\u0437\u0432\u0438\u0432\u0430\u044e\u0442 \u043f\u0440\u043e\u0434\u0443\u043a\u0442 \u0447\u0435\u0440\u0435\u0437 \u043f\u0430\u0440\u0442\u043d\u0435\u0440\u0441\u043a\u0443\u044e \u0441\u0435\u0442\u044c.\" \/>\n\t\t<meta property=\"og:url\" content=\"https:\/\/prohoster.info\/sk\/blog\/administrirovanie\/nash-opyt-sozdaniya-api-gateway\" \/>\n\t\t<meta property=\"og:image\" content=\"https:\/\/prohoster.info\/wp-content\/uploads\/2021\/11\/logo-350.jpg\" \/>\n\t\t<meta property=\"og:image:secure_url\" content=\"https:\/\/prohoster.info\/wp-content\/uploads\/2021\/11\/logo-350.jpg\" \/>\n\t\t<meta property=\"og:image:width\" content=\"350\" \/>\n\t\t<meta property=\"og:image:height\" content=\"350\" \/>\n\t\t<meta property=\"article:published_time\" content=\"2019-10-31T18:37:27+00:00\" \/>\n\t\t<meta property=\"article:modified_time\" content=\"2019-10-31T18:37:27+00:00\" \/>\n\t\t<meta property=\"article:publisher\" content=\"https:\/\/www.facebook.com\/prohoster\" \/>\n\t\t<meta property=\"article:author\" content=\"https:\/\/www.facebook.com\/prohoster\" \/>\n\t\t<!-- All in One SEO -->\n\n","aioseo_head_json":{"title":"\ud83e\udd47Na\u0161a sk\u00fasenos\u0165 s vytv\u00e1ran\u00edm API Gateway | ProHoster","description":"Niektor\u00e9 spolo\u010dnosti, vr\u00e1tane na\u0161ich klientov, rozv\u00edjaj\u00fa produkt prostredn\u00edctvom partnerskej siete.","canonical_url":"https:\/\/prohoster.info\/sk\/blog\/administrirovanie\/nash-opyt-sozdaniya-api-gateway","robots":"max-image-preview:large","keywords":"","webmasterTools":{"miscellaneous":""},"schema":null,"og:locale":"sk_SK","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\u041d\u0430\u0448 \u043e\u043f\u044b\u0442 \u0441\u043e\u0437\u0434\u0430\u043d\u0438\u044f API Gateway | ProHoster","og:description":"\u041d\u0435\u043a\u043e\u0442\u043e\u0440\u044b\u0435 \u043a\u043e\u043c\u043f\u0430\u043d\u0438\u0438, \u0432 \u0442\u043e\u043c \u0447\u0438\u0441\u043b\u0435 \u043d\u0430\u0448 \u0437\u0430\u043a\u0430\u0437\u0447\u0438\u043a, \u0440\u0430\u0437\u0432\u0438\u0432\u0430\u044e\u0442 \u043f\u0440\u043e\u0434\u0443\u043a\u0442 \u0447\u0435\u0440\u0435\u0437 \u043f\u0430\u0440\u0442\u043d\u0435\u0440\u0441\u043a\u0443\u044e \u0441\u0435\u0442\u044c.","og:url":"https:\/\/prohoster.info\/sk\/blog\/administrirovanie\/nash-opyt-sozdaniya-api-gateway","og:image":"https:\/\/prohoster.info\/wp-content\/uploads\/2021\/11\/logo-350.jpg","og:image:secure_url":"https:\/\/prohoster.info\/wp-content\/uploads\/2021\/11\/logo-350.jpg","og:image:width":350,"og:image:height":350,"article:published_time":"2019-10-31T18:37:27+00:00","article:modified_time":"2019-10-31T18:37:27+00:00","article:publisher":"https:\/\/www.facebook.com\/prohoster","article:author":"https:\/\/www.facebook.com\/prohoster"},"aioseo_meta_data":{"post_id":"30792","title":null,"description":null,"keywords":null,"keyphrases":null,"primary_term":null,"canonical_url":null,"og_title":null,"og_description":null,"og_object_type":"default","og_image_type":"default","og_image_url":null,"og_image_width":null,"og_image_height":null,"og_image_custom_url":null,"og_image_custom_fields":null,"og_video":null,"og_custom_url":null,"og_article_section":null,"og_article_tags":null,"twitter_use_og":false,"twitter_card":"default","twitter_image_type":"default","twitter_image_url":null,"twitter_image_custom_url":null,"twitter_image_custom_fields":null,"twitter_title":null,"twitter_description":null,"schema":{"blockGraphs":[],"customGraphs":[],"default":{"data":{"Article":[],"Course":[],"Dataset":[],"FAQPage":[],"Movie":[],"Person":[],"Product":[],"ProductReview":[],"Car":[],"Recipe":[],"Service":[],"SoftwareApplication":[],"WebPage":[]},"graphName":"","isEnabled":true},"graphs":[]},"schema_type":null,"schema_type_options":null,"pillar_content":false,"robots_default":true,"robots_noindex":false,"robots_noarchive":false,"robots_nosnippet":false,"robots_nofollow":false,"robots_noimageindex":false,"robots_noodp":false,"robots_notranslate":false,"robots_max_snippet":null,"robots_max_videopreview":null,"robots_max_imagepreview":"large","priority":null,"frequency":null,"local_seo":null,"seo_analyzer_scan_date":"2026-01-21 03:01:22","breadcrumb_settings":null,"limit_modified_date":false,"reviewed_by":null,"ai":null,"created":"2021-02-28 17:05:31","updated":"2026-01-21 03:01:22","focus_keyword":null,"additional_keywords":null,"truseo_locale":null},"gt_translate_keys":[{"key":"link","format":"url"}],"_links":{"self":[{"href":"https:\/\/prohoster.info\/sk\/wp-json\/wp\/v2\/posts\/30792","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/prohoster.info\/sk\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/prohoster.info\/sk\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/prohoster.info\/sk\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/prohoster.info\/sk\/wp-json\/wp\/v2\/comments?post=30792"}],"version-history":[{"count":0,"href":"https:\/\/prohoster.info\/sk\/wp-json\/wp\/v2\/posts\/30792\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/prohoster.info\/sk\/wp-json\/wp\/v2\/media\/22777"}],"wp:attachment":[{"href":"https:\/\/prohoster.info\/sk\/wp-json\/wp\/v2\/media?parent=30792"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/prohoster.info\/sk\/wp-json\/wp\/v2\/categories?post=30792"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/prohoster.info\/sk\/wp-json\/wp\/v2\/tags?post=30792"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}