JSFoo: round the year submissions

JSFoo: round the year submissions

Submit talks on JavaScript and full stack engineering round the year

Gireesh Punathil

@gireeshpunam

Memory efficiency with Javascript Closures

Submitted Aug 3, 2018

Memory Leaks leading to undesired growth and exhaustion of memory are by far the most common production problem reported on enterprise scale Node applications. Closure, a powerful semantic feature in functional programs which are used pervasively in Node.js programs to support asynchronous and event driven programming model, is a prominent source of unanticipated memory leaks. In this presentation, I will explain three most common use cases where Closures are used in Node. The intent is to illustrate critical importance of closures in the functional programming, demonstrate peculiar ways in which closures retain memory resources and provide best practices in addressing those scenarios to help developers write efficient Javascript programs.

Outline

  • Introduction to Functional Programming
  • Introduction to Closures
  • Different use cases of Closures in Node.js
  • Showcase potential memory leaks through Closures
  • Showcase programming best practices with Closures

Requirements

None

Speaker bio

Gireesh Punathil is an Architect and Software developer with IBM India Software Labs, predominantly working in Java and Node.js. In 15 years of his career, he has been porting, developing and debugging web servers, virtual machines and compilers. His expertise is in problem isolation and determination of large and complex software modules. He has spoken at several Node.js and Java conferences.

Comments

{{ gettext('Login to leave a comment') }}

{{ gettext('Post a comment…') }}
{{ gettext('New comment') }}
{{ formTitle }}

{{ errorMsg }}

{{ gettext('No comments posted yet') }}

Hosted by

JSFoo is a forum for discussing UI engineering; fullstack development; web applications engineering, performance, security and design; accessibility; and latest developments in #JavaScript. Follow JSFoo on Twitter more