In this section, we saw debugging and core aspects involved in profiling. We learned how to diagnose a leak or observe heap dump memory to analyze a service request. We saw how a proxy can often help, even if it increases a network hop:
- To avoid overloading, we have a module providing as in, code 503 middleware. Refer to https://github.com/davidmarkclements/overload-protection for implementation details.
- Chrome Inspector is a very useful tool for debugging Node.js microservices, as it not only provides a debugging interface, but also heap snapshots and CPU profiling.
- VS Code is also a very user-friendly tool.
- Node.js embraced node-inspector and included it in the core module, thus making remote debugging very easy. ...