May 24, 2018

    User Rating: 0 / 5

    Star InactiveStar InactiveStar InactiveStar InactiveStar Inactive

    By PubNub

    Blog post: pubnub.com/blog/node-background-jobs-async-processing-for-async-language/

    Full library of programming talks (something for everyone!): pubnub.com/blog/category/talks/

    In this talk from the SFNode meetup, Evan Tahler gives an overview of some of the many ways you can perform node background jobs, including examples and how node makes it better. Topics include:

    - Possible Task Strategies
    - Foreground (in-line)
    - Parallel (threaded-ish)
    - Local Messages
    - Remote Messages
    - Remote Queues (Resque-ish)
    - Event Bus (Kafka-ish)

    Tags:

    User Rating: 0 / 5

    Star InactiveStar InactiveStar InactiveStar InactiveStar Inactive

    By Microsoft Visual Studio

    The traditional full stack was web frontend development and cloud platform backend work, but if you talk to developers today this has vastly changed. A new full stack is emerging that includes the traditional web frontend and cloud platform backend, but also includes mobile phones and tablets, API services, desktop (who thought that would explode?) and IoT. Developers are tasked to build and manage one application that has to manage all of this. And, the program environment of choice for the full stack developer: Node.js. This presentation is delivered by the Node.js Foundation community manager, who talks a bit about the history of Node.js; why it's becoming the first choice for the full stack developer; and how Node.js functions everywhere from web frontend development to IoT to create a single platform for developers to create the herculean applications of today.

    Tags:

    User Rating: 0 / 5

    Star InactiveStar InactiveStar InactiveStar InactiveStar Inactive

    By LearnCode.academy

    Get the code here! https://gist.github.com/learncodeacad...

    Many Node.js developers don't know that Node by default only uses one core of your processor. It's intentional and it's a great move. It just means that you have to run cluster to get the full capacity out of your server.

    When cluster.js runs, it spins up one copy (fork) of your application for each core on your machine, and balances the traffic between them. It also listens to each fork, so if one dies, it spins up a new one in it's place.

    Clustering is a great way to add stability to your application and drastically increase it's load capacity.

    Tags:

    Page 5 of 9

    © 2017 AngularGeek.com

    Please publish modules in offcanvas position.