Upgrade to Pro — share decks privately, control downloads, hide ads and more …
Sign up for free

The Node.js Scalability Myth

Avatar for Felix Geisendörfer Felix Geisendörfer
June 16, 2012
Programming
1.3k
6

The Node.js Scalability Myth

Talk given at the Munich Node.js Meetup on 14.06.2012.

Avatar for Felix Geisendörfer

Felix Geisendörfer

June 16, 2012

More Decks by Felix Geisendörfer

See All by Felix Geisendörfer
tus.io - Resumable File Uploads (Lightning Talk)
Avatar for Felix Geisendörfer felixge
2
870
Programming flying robots with JavaScript
Avatar for Felix Geisendörfer felixge
2
1k
Programming flying robots with JavaScript
Avatar for Felix Geisendörfer felixge
0
670
Programming an AR Drone Firmware with JS (de)
Avatar for Felix Geisendörfer felixge
1
680
Faster than C?
Avatar for Felix Geisendörfer felixge
1
1.3k
Flying robots over a 10.000 mile distance with JavaScript.
Avatar for Felix Geisendörfer felixge
0
570
Faster than C?
Avatar for Felix Geisendörfer felixge
1
720
The power of node.js (with quadcopters)
Avatar for Felix Geisendörfer felixge
0
560
Faster than C?
Avatar for Felix Geisendörfer felixge
0
500

Other Decks in Programming

See All in Programming
Apple Intelligenceとオンデバイス時代の到来
Avatar for Yahiro Sugiyama yahir0
0
170
JIS keyboard support in Omarchy
Avatar for LEF lef237
0
170
個人開発者よ、Honoを使え（おじさんver）
Avatar for tanahiro2010 tanahiro2010
2
290
AI時代のFlutter品質設計 — アプリ品質を守るQuality Layers
Avatar for omatty198 omatty198
0
320
當我們開始不讀 Code - AI Agent 時代，Code Review 與 Clean Code 還剩下什麼？
Avatar for James Wang jame2408
1
340
AI主導のプログラミング学習アプリを作ってみた
Avatar for econanringo econanringo
0
200
AI時代のシニアエンジニアとは
Avatar for Yosuke Furukawa yosuke_furukawa
PRO
12
11k
Python Lambdaにおけるテストしやすい設計とAI支援の活用 / Designing Testable Python Lambda Functions with AI
Avatar for Kitano Yuichi kitano_yuichi
1
250
Kotlinize Is Not Just Converting to Kotlin
Avatar for Kazuki Chigita chigichan24
1
200
Kotlinの15年とServer-Side Kotlin
Avatar for Takehata Naoto n_takehata
1
170
Railsのためのパスキー実践入門 〜マルチテナントSaaSでの意思決定〜
Avatar for utakaha utakaha
3
1.8k
Optunaを作ったときにやりたかったこと、その後 (2026/10/16, Optuna Meetup #3)
Avatar for Takuya Akiba iwiwi
4
1.4k

Featured

See All Featured
Heart Work Chapter 1 - Part 1
Avatar for Lake Fama lfama
PRO
10
37k
svc-hook: hooking system calls on ARM64 by binary rewriting
Avatar for Akira Moroo retrage
2
660
SEOcharity - Dark patterns in SEO and UX: How to avoid them and build a more ethical web
Avatar for Sara Fernández Carmona sarafernandez
0
310
The SEO Collaboration Effect
Avatar for Kristina Bergwall kristinabergwall1
1
610
BBQ
Avatar for Matthew Crist matthewcrist
90
10k
How to build an LLM SEO readiness audit: a practical framework
Avatar for Nick Samuel nmsamuel
2
960
The Straight Up "How To Draw Better" Workshop
Avatar for Dennis Kardys denniskardys
239
140k
Utilizing Notion as your number one productivity tool
Avatar for Mfonobong Umondia mfonobong
4
630
Leveraging LLMs for student feedback in introductory data science courses - posit::conf(2025)
Avatar for Mine Cetinkaya-Rundel minecr
1
460
Building Better People: How to give real-time feedback that sticks.
Avatar for Will Jessup wjessup
371
20k
Amusing Abliteration
Avatar for ianozsvald ianozsvald
1
370
How to Think Like a Performance Engineer
Avatar for Harry Roberts csswizardry
28
2.9k

Transcript

  1. The Node.js Scalability Myth Felix Geisendörfer 14.06.2012 at Munich node.js

    user group
  2. None

  3. Felix Geisendörfer

  4. transloadit.com

  5. core contributor

  6. npm modules

  7. node-formidable

  8. node-mysql

  9. ~50 modules total

  10. (@)felixge(.de)

  11. Background

  12. I need to build an über-scalable web service. It will

    be the next big thing!

  13. Easy! I will use node.js and MongoDB!

  14. Easy! I will use node.js and MongoDB!

  15. Because node.js is “scalable”, right?

  16. None

  17. This Talk

  18. #1 Consider Reality

  19. Using node for performance reasons?

  20. Measuring performance in production?

  21. 1000 req / s

  22. 100 req / s

  23. 10 req / s 10 req / s

  24. ~1 million requests per day

  25. ~1 million units of value

  26. None

  27. #2 Node Scales Vertically

  28. Adding more resources to a single node

  29. None

  30. CPU

  31. Google V8

  32. JS -> Assembly

  33. Crankshaft JIT

  34. Fast

  35. Single Threaded* * For most parts

  36. Computers of the future will have hundreds of cores!

  37. Node’s Multi-Core Story

  38. Pre-fork

  39. IPC

  40. Like Ruby, Python, PHP, etc.

  41. But ... shared memory?

  42. Your problem requires shared memory?

  43. JavaScript is not your language

  44. Good Luck

  45. Memory

  46. No hard limit on 64bit (since node-0.6 / v8-3.7)

  47. However

  48. Avoid huge heaps

  49. Disk

  50. Done in thread pool

  51. Along with DNS

  52. No sendfile()

  53. None

  54. Network

  55. None

  56. Non-blocking I/O

  57. tl;dr

  58. pre-fork & non-blocking i/o

  59. #3 Horizontal Scaling is hard

  60. CAP

  61. Network Partitions

  62. Consistency

  63. Availability

  64. Some Tips

  65. Shared Nothing

  66. Messaging

  67. Monitoring

  68. The Node.js Scalability Myth

  69. Threads do not scale Node.js scales

  70. Threads do not scale Node.js scales

  71. Node is a tool

  72. None
  73. None
  74. None

  75. If you can’t duc it F#@k it

  76. Questions? Slides will be available at felixge.de

  77. Thanks

  78. Tool Demo