What is Event-driven programming?

 Event-driven programming is building our application based on and respond to events. When an event occurs, like click or keypress, we are running a callback function which is registered to the element for that event.

Event driven programming follows mainly a publish-subscribe pattern.

Image for post

Comments

Post a Comment

Popular posts from this blog

Which node logger did you use in your project?

Following are the common logger modules: 1) logger SUMMARY A simple logging library that combines the simple APIs of Ruby's logger.rb and browser-js console.log() USAGE A logger has 5 different levels of logging in a specific order: 'fatal', 'error', 'warn', 'info', 'debug' Each of these log levels has its own method on the logging instance. You can set the maximum log level on a logger at runtime. By default, a logger writes to STDOUT, but given a writeable file path, it will log directly to a file. Instantiation: // node/common.js style var logger = require('./logger').createLogger(); // logs to STDOUT var logger = require('./logger').createLogger('development.log'); // logs to a file 2)  simple-node-logger A simple multi-level logger for console, file, and rolling file appenders. Features include: levels: trace, debug, info, warn, error and fatal levels (plus all and off) flexible ap...
Read more

What are clusters and worker threads, and when would you use them?

Worker threads are for when you want to run long-running synchronous tasks, and you don't want to block the event loop. It runs the code in a separate thread, and can communicate the results back to the main thread. Cluster workers are separate instances of your Node process, which are primarily used for load balancing incoming requests across multiple processes, to take advantage of multi-core processors.
Read more