addressalign-toparrow-leftarrow-rightbackbellblockcalendarcameraccwcheckchevron-downchevron-leftchevron-rightchevron-small-downchevron-small-leftchevron-small-rightchevron-small-upchevron-upcircle-with-checkcircle-with-crosscircle-with-pluscrossdots-three-verticaleditemptyheartexporteye-with-lineeyefacebookfolderfullheartglobegmailgooglegroupsimageimagesinstagramlinklocation-pinm-swarmSearchmailmessagesminusmoremuplabelShape 3 + Rectangle 1outlookpersonJoin Group on CardStartprice-ribbonShapeShapeShapeImported LayersImported LayersImported Layersshieldstartickettrashtriangle-downtriangle-uptwitteruseryahoo

December SFNode Meetup

  • to
  • NodeSource

    577 2nd Street, Suite 204, San Francisco, CA (map)

    0.000000 0.000000

  • NodeSource hosts SFNode in their new office! Come on by to hear Joe Doyle talks about common operations challenges with and how to solve them. Then for the second presentation of the night Daniel Khan discussing debugging < profiling < tracing < monitoring. To close out the night we'll have open mic and social time.

    6:30pm - Doors Open 
    7:00pm - Common Operations Challenges with Node.js and How to Solve Them - Joe Doyle
    7:30pm - debugging < profiling < tracing < monitoring -  Daniel Khan
    8:00pm - Open Mic and Social time
    9:00pm - Doors close

    Common Operations Challenges with Node.js and How to Solve Them
    As more companies use Node.js in production, they often run into common operational issues. We'll cover topics such as recommendations for installing Node.js, selecting the right modules, keeping your Node.js process running, and look at some common performance issues. We'll also see how N|Solid can help with some of these challenges.

    About Joe Doyle
    Joe Doyle (@JoeDoyle23) is the Solutions Architect Manager at NodeSource. He has been working with Node.js and JavaScript for the last 5 years. Today much of his focus is on helping customers be successful with N|Solid and working to support the Node.js community.

    debugging < profiling < tracing < monitoring
    For each stage of your applications lifecycle there are viable ways to get insights into Node.js. Let’s explore- and also understand the theory behind them. What happens if we attach a debugger or what does the V8 profiling facility give us and what does it cost? How can we monitor Node in production, which metrics are important and why is it so hard to trace through Node.js’ execution? Let’s also cover which new ways to get telemetry we can expect in upcoming versions of Node, shall we?

    This session will cover all of that and in the end you will have the knowledge and tools to properly introspect your Node.js applications no matter what.

Join or login to comment.

Want to go?

Join and RSVP

198 going

Our Sponsors

  • NodeSource

    Thank you NodeSource for sponsoring video production and archives.

People in this
Meetup are also in:

Sign up

Meetup members, Log in

By clicking "Sign up" or "Sign up using Facebook", you confirm that you accept our Terms of Service & Privacy Policy