Bangalore, May 25th

[gireeshpunathil]

We (@thefourtheye and me) are planning to run a Node.js Clinic (not to be confused with node-clinic tool) in Bangalore on May 25th.

In a first of its kind event, the objective is to provide an open platform for developers using Node.js technology, to seek resolutions for issues they are facing in their node projects; connect them with experienced community members to identify fixes / answers / clarifications.

The exercise will be run as part of the next instance of Polyglot-Languages-Runtimes meetup. IBM office space will be used for the event. Count of expected participants is unknown at the moment.

Your support is highly appreciated, thanks in advance.

Here is what we have in mind:

• Address as many issues as we can at onsite.
• If anyone is willing to join us through webex to listen to questions and respond, much appreicated!
• Issues that are unresolved / needing wider collaboration and iteration we raise it in nodejs/help repo.

Thanks!

As of 16/05, 43 people going for the meetup As of 18/05, 130 As of 20/05, 147 As of 22/05, 173 As of 24/05, 190

[gireeshpunathil]

The clinic part of session will start in ~6 hours from now (11 AM UTC). Request collaborators to be on standby on help repo. Please 👍 here if you can be counted on.

[gireeshpunathil]

current RSVP count is ~200, realistic expectation is ~50 with ~25 problems / questions / issues. Please 👍 here if you are willing to join the session through webex to help with problem solving.

thanks in advance!

[gireeshpunathil]

the event was a great success, meeting its stated purpose of improving Node.js developer experience.

some features:

• ~40 attendees
• 3 sessions
• 2 hours clinic
• ~40 questions

As no one brought proprietary code, all the clinic activity were performed in full view, like a panel session.

[gireeshpunathil]

posting the questions that were asked here for posterity:

• how does an asynchronous API brings the original execution context of the call site in the callback?
• how does one know if an API is an asynchronous one or not?
• how is an asynchronous API implemented?
• what are the implications to the program if there is a blocking call in it?
• how do I go about having to deal with code that is computation intensive?
• what is the real world need of Buffers? Can you please give examples?
• when does allocated buffer objects get destroyed?
• what are the considerations between cluster module and horizontal scaling?
• differentiate between setImmediate and setTimeout?
• are there internal prioritization between scheduled functions?
• how does JSON schema validation help? what libraries are vailable?
• are the native addon code ran inside the JS execution engine?
• how does Node.js support mult-threading under the cover?
• how is it different from child_process?
• if threads cannot share data, how can they interact each other?
• what exactly made node.js faster than say java - in terms of threads, architecture?
• how do node communicate with the system, in particular, perform system calls?
• can you explain the architecture of libuv?
• what are the functions of background threads created with libuv?
• as node is already asynchronous, do we still need queuing mechanism for messages?
• is there a way to track specific nodejs API calls?
• is VueJS also using libuv?
• what qualifies an API to be asynchronous? those which makes calls to libuv?
• are the bindings for libuv the same for browsers as well?
• does the queue have to be exhausted before micro tasks are executed?
• is libuv specific to node.js?
• what modules can be used for JSON schema validation?
• what is an ideal way to learn node.js, knowing the components alongside?
• how does event loop work if asynchronous tasks, wrapped in a promise, are in a loop?
• if there is a table, and there is a after-create hook that updates data elsewhere, do we have to use transactions, or will there be race conditions?
• how do we use the functional semantics in node js?
• in AWS, can we write reusable Node.js code like in Lambda?