I’ve seen an app that has terrible performance. It’s written in Node. Ergo Node doesn’t scale. Q.E.D.
Something like this happens frequently on Twitter and Hacker News — mostly because performance is usually an after-thought: often code gets deployed without being properly benchmarked (or tested for security).
When developers hit a scalability problem they tend to:
- blame the host
- blame the platform
- blame the database
- blame the platform again
- blame someone else’s code
- try to guess and fix
- problem wasn’t fixed?
- iterations < 10 ? go to 1
- else REWRITE EVERYTHING
What we need is less of this:
and more of this:
To avoid this:
YLD is teaming up with ^Lift Security to deliver a one day training on Node.js performance and security in London on September 16th.
Delivered by Matthew Lowe and Pedro Teixeira, with a little help from David Dias, Adam Baldwin and Luke Bond, you will have the opportunity to learn about:
Performance:
- Defining and measuring the performance of a Node app
- Techniques for monitoring
- Understanding the Event Loop
- Measuring Event Loop Lag
- Understanding what the CPU is doing using Dtrace and V8 profiling
- How Garbage Collection works and its impact on performance
- How to use tools like Heap-dump and MDB to analyse V8 memory
- Fixing I/O-bound processes
- Fixing CPU-bound processes
- Fixing memory-bound processes
- Techniques to improve performance of hot code paths
Security:
- Approaches for building securely with both Hapi and Express
- Authentication, Authorisation and Session Management
- Handling Sensitive Data
- Cross-Site Scripting (XSS)
- Cross-Site Request Forgery (CSRF)
- SQL Injection / Command Injection
- Directory Traversal
- Mass Assignment
- Security Headers
- Security Misconfiguration
- Using the Node Security Project to identify known vulnerabilities
Sittings are limited, reserve yours here.