Node.js je b\u011bhov\u00e9 prost\u0159ed\u00ed pro JavaScript postaven\u00e9 nad enginem V8, kter\u00e9 umo\u017e\u0148uje spou\u0161t\u011bt JS mimo prohl\u00ed\u017ee\u010d. D\u00edky event-driven<\/strong> a non-blocking I\/O<\/strong> architektu\u0159e se hod\u00ed pro s\u00ed\u0165ov\u00e9 aplikace s vysokou paraleln\u00ed z\u00e1t\u011b\u017e\u00ed (API, realtime komunikace, proxy, streamovac\u00ed br\u00e1ny). Silnou str\u00e1nkou je jednotn\u00fd jazyk nap\u0159\u00ed\u010d frontendem i backendem, bohat\u00fd ekosyst\u00e9m bal\u00ed\u010dk\u016f a snadn\u00e1 pr\u00e1ce se JSONem.<\/p>\n Node.js pou\u017e\u00edv\u00e1 event loop<\/em> v jednom hlavn\u00edm vl\u00e1kn\u011b pro \u0159\u00edzen\u00ed asynchronn\u00edch operac\u00ed (\u010dasova\u010de, I\/O, s\u00ed\u0165). Blokuj\u00edc\u00ed \u00falohy (nap\u0159. kryptografie, komprese) prov\u00e1d\u00ed v pozad\u00ed libuv<\/em> pomoc\u00ed thread poolu<\/em>. Pro CPU-intenzivn\u00ed pr\u00e1ci lze vyu\u017e\u00edt worker_threads<\/strong> nebo horizont\u00e1ln\u00ed \u0161k\u00e1lov\u00e1n\u00ed p\u0159es cluster<\/strong>. Kl\u00ed\u010dov\u00e9 je navrhovat k\u00f3d tak, aby neblokoval smy\u010dku (vyhnout se synchronn\u00edm I\/O, dlouh\u00fdm smy\u010dk\u00e1m, velk\u00fdm serializac\u00edm na hlavn\u00edm vl\u00e1kn\u011b).<\/p>\n Node.js podporuje CommonJS<\/strong> (require\/module.exports) i ESM<\/strong> (import\/export). Volba ovliv\u0148uje zp\u016fsob na\u010d\u00edt\u00e1n\u00ed, cache i interoperabilitu. Doporu\u010den\u00fd sm\u011br je ESM, kter\u00fd je standardem v JS ekosyst\u00e9mu. Konfigurace prob\u00edh\u00e1 pomoc\u00ed Bal\u00ed\u010dky se spravuj\u00ed p\u0159es npm<\/strong>, yarn<\/strong> nebo pnpm<\/strong>. Pro v\u011bt\u0161\u00ed k\u00f3dov\u00e9 z\u00e1kladny je b\u011b\u017en\u00e1 organizace do monorepa s workspaces<\/em> a n\u00e1stroji jako Turborepo \u010di Nx. D\u016fle\u017eit\u00e9 je uzamykat p\u0159esn\u00e9 verze ( REST je srozumiteln\u00fd a dob\u0159e cacheovateln\u00fd. RPC<\/strong> (nap\u0159. tRPC) zjednodu\u0161uje typovou bezpe\u010dnost mezi klientem a serverem. GraphQL<\/strong> je vhodn\u00fd pro slo\u017eit\u00e9 klientsk\u00e9 aplikace s pot\u0159ebou flexibiln\u00edch dotaz\u016f; vy\u017eaduje v\u0161ak d\u016fsledn\u00fd query cost<\/em> management, dataloadery a per-field autorizaci.<\/p>\n Preferujte async\/await<\/strong> pro \u010ditelnost, av\u0161ak dbejte na paralelizaci pomoc\u00ed JWT a PASETO jsou b\u011b\u017en\u00e9 pro stateless p\u0159\u00edstupov\u00e9 tokeny, session<\/em> s podepsan\u00fdm cookie je vhodn\u00e1 pro tradi\u010dn\u00ed weby. Dbejte na rotaci kl\u00ed\u010d\u016f (JWKS), kr\u00e1tkou \u017eivotnost tokenu, refresh token<\/em> flow a RBAC\/ABAC<\/strong> v aplika\u010dn\u00ed vrstv\u011b. Na API br\u00e1n\u011b aplikujte rate limiting<\/em>, IP allow-list<\/em>, mTLS<\/em> dle pot\u0159eby.<\/p>\n Konfigurace pat\u0159\u00ed do prom\u011bnn\u00fdch prost\u0159ed\u00ed. Odd\u011blte build<\/em> a run<\/em> f\u00e1zi, logujte do STDOUT, pou\u017e\u00edvejte immutable buildy<\/strong>. Udr\u017eujte idempotentn\u00ed start (bez postrann\u00edch efekt\u016f). Zave\u010fte feature flags<\/em> pro \u0159\u00edzen\u00e9 nasazov\u00e1n\u00ed.<\/p>\n Node.js um\u00ed spolehliv\u011b b\u011b\u017eet jako dlouhotrvaj\u00edc\u00ed proces (HTTP servery, WebSocket huby), ale je tak\u00e9 vhodn\u00fd pro cron<\/strong> a d\u00e1vky (nap\u0159. s knihovnami pro pl\u00e1nov\u00e1n\u00ed). V prost\u0159ed\u00ed serverless<\/strong> je nutn\u00e1 inicializace bez stav\u016f, rychl\u00fd cold start, kr\u00e1tk\u00e9 p\u0159ipojen\u00ed k DB (pooling p\u0159es proxy) a idempotence handler\u016f.<\/p>\n Pro realtime notifikace pou\u017eijte WebSockety nebo SSE. D\u016fle\u017eit\u00e9 je \u0161k\u00e1lovat pub\/sub<\/em> vrstvu (Redis, NATS) a \u0159e\u0161it presence<\/em>, backoff<\/em> a resubscribe<\/em> po v\u00fdpadku. Rate-limitujte ud\u00e1losti a m\u011bjte kv\u00f3ty per-tenant.<\/p>\n Velk\u00e9 uploady obsluhujte p\u0159es multipart streaming<\/em> a ukl\u00e1dejte do objektov\u00fdch \u00falo\u017ei\u0161\u0165 s podpisovan\u00fdmi URL (pre-signed). Stahov\u00e1n\u00ed serv\u00edrujte p\u0159es CDN, server v Node.js pouze generuje odkazy a kontroluje p\u0159\u00edstupov\u00e1 pr\u00e1va.<\/p>\n Pro integraci s nativn\u00edm k\u00f3dem slou\u017e\u00ed N-API<\/strong> a node-addon-api<\/strong>. Vy\u017eaduje to pe\u010dliv\u00e9 verzov\u00e1n\u00ed a CI pro r\u016fzn\u00e9 platformy. Alternativou jsou extern\u00ed mikroslu\u017eby v jin\u00e9m jazyce komunikuj\u00edc\u00ed p\u0159es HTTP\/gRPC, co\u017e zjednodu\u0161uje build, ale p\u0159id\u00e1v\u00e1 s\u00ed\u0165ovou latenci.<\/p>\n Vyu\u017e\u00edvejte Nasazujte na LTS<\/strong> \u0159ad\u00e1ch, sjedno\u0165te verzi pomoc\u00ed Node.js je vhodn\u00e9 pro lehk\u00e9 mikroslu\u017eby: ka\u017ed\u00e1 m\u00e1 jasn\u00fd bounded context, smluven\u00e9 kontrakty (OpenAPI\/AsyncAPI), backward-compatible zm\u011bny a verzov\u00e1n\u00ed endpoint\u016f. Dodr\u017eujte consumer-driven contracts<\/em> a CI validace sch\u00e9mat.<\/p>\n Preferujte bezstavovost a stav ukl\u00e1dejte do extern\u00edch syst\u00e9m\u016f (DB, cache, fronty). Pokud je stav nevyhnuteln\u00fd (nap\u0159. hern\u00ed realtime), pou\u017eijte sticky sessions<\/em>, robustn\u00ed replikaci a conflict resolution<\/em>. Pl\u00e1nujte rebalance<\/em> p\u0159i \u0161k\u00e1lov\u00e1n\u00ed.<\/p>\n Node.js je vyzr\u00e1l\u00e9 a v\u00fdkonn\u00e9 prost\u0159ed\u00ed pro serverov\u00e9 skriptov\u00e1n\u00ed. Vynik\u00e1 tam, kde je kl\u00ed\u010dov\u00e1 asynchronn\u00ed I\/O pr\u00e1ce, rychl\u00fd v\u00fdvoj a sd\u00edlen\u00fd jazyk nap\u0159\u00ed\u010d stackem. \u00dasp\u011b\u0161n\u00e1 produkce stoj\u00ed na spr\u00e1vn\u00e9m asynchronn\u00edm n\u00e1vrhu, kvalitn\u00ed observabilit\u011b, bezpe\u010dnosti, typov\u00e9 discipl\u00edn\u011b a promy\u0161len\u00e9m nasazen\u00ed. Dodr\u017een\u00edm uveden\u00fdch z\u00e1sad z\u00edsk\u00e1te \u0161k\u00e1lovatelnou, spolehlivou a ekonomicky efektivn\u00ed platformu pro modern\u00ed backendov\u00e9 slu\u017eby.<\/p>\n","protected":false},"excerpt":{"rendered":" Tvorba server\u016f v Node.js: Express, asynchronn\u00ed I\/O a skripty. Nau\u010d\u00edte se stav\u011bt API, n\u00e1stroje CLI i robustn\u00ed logging a monitoring.<\/p>\n","protected":false},"author":46,"featured_media":84169,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[617],"tags":[1962,1963,1964,1965,1608,1966,1967,1968],"class_list":["post-44169","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-telekomunikacie","tag-async-i-o","tag-cli","tag-express","tag-logovani","tag-monitoring","tag-node-js-a-serverove-skriptovani","tag-npm","tag-worker-threads"],"yoast_head":"\nUd\u00e1lostn\u00ed smy\u010dka, vl\u00e1kna a model konkurence<\/h2>\n
Moduly: CommonJS vs. ECMAScript Modules<\/h2>\n
type<\/code> v package.json<\/code> a\/nebo p\u0159\u00edpon .mjs<\/code>\/.cjs<\/code>. P\u0159i n\u00e1vrhu knihoven dbejte na jasnou distribuci (dual-package, export mapy) a pe\u010dliv\u00e9 ur\u010den\u00ed engines<\/code> (minim\u00e1ln\u00ed verze Node.js).<\/p>\nSpr\u00e1va z\u00e1vislost\u00ed a monorepa<\/h2>\n
package-lock.json<\/code>\/pnpm-lock.yaml<\/code>), pe\u010dovat o audit zranitelnost\u00ed a pou\u017e\u00edvat semantic versioning<\/em>. P\u0159i b\u011bhu v produkci preferujte --omit=dev<\/code> (instalace bez dev z\u00e1vislost\u00ed) a deterministick\u00e9 buildy.<\/p>\nServerov\u00e9 frameworky a architektonick\u00e9 styly<\/h2>\n
\n
API vrstvy: REST, RPC a GraphQL<\/h2>\n
Asynchronn\u00ed programov\u00e1n\u00ed: Promise, async\/await, streamy<\/h2>\n
Promise.all<\/code> tam, kde to d\u00e1v\u00e1 smysl. Streamy<\/strong> (Readable\/Writable\/Transform\/Duplex) jsou kl\u00ed\u010dov\u00e9 pro efektivn\u00ed pr\u00e1ci s velk\u00fdmi daty (upload\/download, komprese, parsov\u00e1n\u00ed). Pou\u017e\u00edvejte backpressure<\/em> a pipeline<\/em> utilitu pro bezpe\u010dn\u00e9 \u0159et\u011bzen\u00ed.<\/p>\nPr\u00e1ce s datab\u00e1zemi a datovou vrstvou<\/h2>\n
\n
Autentizace a autorizace<\/h2>\n
Bezpe\u010dnost serveru a z\u00e1vislost\u00ed<\/h2>\n
\n
.env<\/code> v repozit\u00e1\u0159i, ale bezpe\u010dn\u00fd trezor; rotace a audit p\u0159\u00edstup\u016f.<\/li>\nKonfigurace, 12-Factor a prost\u0159ed\u00ed<\/h2>\n
Logov\u00e1n\u00ed, metriky a observabilita<\/h2>\n
\n
V\u00fdkon a \u0161k\u00e1lov\u00e1n\u00ed<\/h2>\n
\n
fs.createReadStream<\/code> \u2192 res<\/code>).<\/li>\n<\/ul>\nTestov\u00e1n\u00ed a kvalita<\/h2>\n
\n
Typy b\u011bhu: dlouho b\u011b\u017e\u00edc\u00ed slu\u017eby, cron a serverless<\/h2>\n
Nasazen\u00ed: kontejnery, orchestr\u00e1tory a procesn\u00ed mana\u017eery<\/h2>\n
\n
HTTP, WebSocket a realtime<\/h2>\n
Souborov\u00fd syst\u00e9m, uploady a CDN<\/h2>\n
Mezijazykov\u00e1 interoperabilita a nativn\u00ed dopl\u0148ky<\/h2>\n
Stabilita, odolnost a vzory spolehlivosti<\/h2>\n
\n
Mezin\u00e1rodn\u00ed prost\u0159ed\u00ed, lokalizace a form\u00e1tov\u00e1n\u00ed<\/h2>\n
Intl<\/code> API pro form\u00e1tov\u00e1n\u00ed \u010d\u00edsel, m\u011bn a \u010das\u016f, vyvarujte se manu\u00e1ln\u00edho parsingu. \u010cas v\u017edy ukl\u00e1dejte jako UTC, u\u017eivateli prezentujte v jeho \u010dasov\u00e9 z\u00f3n\u011b. Pro lokalizaci zpr\u00e1v pou\u017e\u00edvejte ICU message form\u00e1t a extern\u00ed slovn\u00edky.<\/p>\nSpr\u00e1va verz\u00ed Node.js a LTS strategie<\/h2>\n
.nvmrc<\/code> nebo engines<\/code> v package.json<\/code>. P\u0159i CI implementujte matrix buildy pro c\u00edlov\u00e9 verze a pravideln\u011b testujte kompatibilitu. Sledujte deprecace a zm\u011bny v API (fs\/promises, URL, WHATWG Streams).<\/p>\nObservabilita v\u00fdkonu a profilov\u00e1n\u00ed<\/h2>\n
\n
Mikroslu\u017eby a kontrakty<\/h2>\n
Bezstavov\u00e9 vs. stavov\u00e9 slu\u017eby<\/h2>\n
Praktick\u00e9 z\u00e1sady pro produkci<\/h2>\n
\n
Typick\u00e9 antipatterny a jak se jim vyhnout<\/h2>\n
\n
Z\u00e1v\u011br<\/h2>\n