Skip to main content

What are Event Emitters in Node.js? Provide an example.

 Event Emitters in Node.js

In Node.js, an Event Emitter is a fundamental concept used to handle asynchronous events. It is part of the events module, and it allows an object to emit events and allow listeners to respond to those events.

The EventEmitter class in Node.js provides an interface for creating objects that can emit events and register event listeners (callbacks) for those events.

What are Event Emitters in Node.js? Provide an example.

Key Concepts:

  1. Emit: When something happens (an event occurs), an emitter can emit that event.

  2. Listen: The system listens for events and executes specific code when the event is triggered.

  3. Event Handling: Allows asynchronous handling of events.

How to Use Event Emitters

1. Import the events module

To use event emitters, you first need to import the events module.


const EventEmitter = require('events');

2. Create an instance of EventEmitter

You create an instance of EventEmitter using the new keyword. Then, you can use this instance to emit events and add listeners.


const emitter = new EventEmitter();

3. Add Listeners to Events

You can listen for specific events using the .on() method. When the event is emitted, the corresponding callback function is executed.


emitter.on('greet', (message) => { console.log(message); });
  • .on('event', callback) is used to register an event listener.

  • In the example, we're listening for the greet event and printing the passed message when it's triggered.

4. Emit Events

You can trigger (emit) an event using the .emit() method. This will execute all the functions that are listening for that specific event.

emitter.emit('greet', 'Hello, Event Emitters!');
  • .emit('event', ...) triggers the event, and any listeners that are attached to that event are invoked.

Example: EventEmitter in Action

Here’s a complete example that demonstrates creating a custom event, adding listeners, and emitting the event.

const EventEmitter = require('events'); // Create an instance of EventEmitter const myEmitter = new EventEmitter(); // Add a listener for the 'greet' event myEmitter.on('greet', (message) => { console.log(`Received message: ${message}`); }); // Emit the 'greet' event with a message myEmitter.emit('greet', 'Hello, world!'); // Another listener can also listen to the same event myEmitter.on('greet', (message) => { console.log(`Another listener: ${message}`); }); // Emit the event again myEmitter.emit('greet', 'Node.js is awesome!');

Output:

Received message: Hello, world! Another listener: Hello, world! Received message: Node.js is awesome! Another listener: Node.js is awesome!

Event Handling Flow:

  1. The first listener listens for the greet event and logs the message.

  2. The second listener also listens for the greet event and logs the message again.

  3. When the event is emitted, both listeners are triggered, and the message is logged.

Other Methods Available for EventEmitters

  • .once(eventName, listener): Listens to an event only once and removes the listener after it is triggered.

    myEmitter.once('onceEvent', () => { console.log('This will only run once'); }); myEmitter.emit('onceEvent'); // Logs 'This will only run once' myEmitter.emit('onceEvent'); // Does nothing
  • .removeListener(eventName, listener): Removes a specific listener for an event.


    const greetListener = (message) => { console.log(`Listener removed: ${message}`); }; myEmitter.on('greet', greetListener); myEmitter.removeListener('greet', greetListener); myEmitter.emit('greet', 'This will not be logged');
  • .removeAllListeners([eventName]): Removes all listeners for a particular event or for all events.

    myEmitter.removeAllListeners('greet'); myEmitter.emit('greet', 'No listeners anymore');

When to Use Event Emitters

Event Emitters are ideal for scenarios like:

Popular posts from this blog

How does BGP prevent routing loops? Explain AS_PATH and loop prevention mechanisms.

 In Border Gateway Protocol (BGP), preventing routing loops is critical — especially because BGP is the inter-domain routing protocol used to connect Autonomous Systems (ASes) on the internet. πŸ”„ How BGP Prevents Routing Loops The main mechanism BGP uses is the AS_PATH attribute . πŸ” What is AS_PATH? AS_PATH is a BGP path attribute that lists the sequence of Autonomous Systems (AS numbers) a route has traversed. Each time a route is advertised across an AS boundary, the local AS number is prepended to the AS_PATH. Example: If AS 65001 → AS 65002 → AS 65003 is the route a prefix has taken, the AS_PATH will look like: makefile AS_PATH: 65003 65002 65001 It’s prepended in reverse order — so the last AS is first . 🚫 Loop Prevention Using AS_PATH ✅ Core Mechanism: BGP routers reject any route advertisement that contains their own AS number in the AS_PATH. πŸ” Why It Works: If a route makes its way back to an AS that’s already in the AS_PATH , that AS kno...

What’s the impact of BGP full routes on router memory and performance?

Receiving full BGP routes (i.e., the full global BGP routing table) has a significant impact on a router's memory and performance. Here's a breakdown of the key impacts: πŸ”§ 1. Memory Usage (RAM) A full BGP table typically contains ~1 million IPv4 routes and growing (~200k+ IPv6 routes). Each BGP route consumes tens to hundreds of bytes of memory, depending on attributes (AS path, communities, etc.). This translates to hundreds of megabytes to several gigabytes of RAM just for storing the BGP RIB (Routing Information Base). The FIB (Forwarding Information Base) , which is installed into the router's hardware or kernel for actual packet forwarding, also consumes memory (especially in TCAM for hardware routers). ❗ Example A router might require 4–8 GB of RAM (or more) to comfortably handle full BGP routes with headroom for growth and stability. 🧠 2. CPU Utilization High CPU load during: Initial BGP session establishment (parsing all rout...

Explain the OSPF LSDB (Link State Database) and how SPF (Shortest Path First) algorithm works.

OSPF (Open Shortest Path First) is a link-state routing protocol , and the LSDB (Link-State Database) and SPF (Shortest Path First) algorithm are core to how OSPF calculates the best paths . Let’s break them down. 🧠 What is the OSPF LSDB (Link-State Database)? The LSDB is a map of the entire OSPF network area — each router stores a complete topology of its area. πŸ” Details: Built from LSAs (Link-State Advertisements) exchanged between routers. Contains info about: Routers and their interfaces Network segments Neighbor relationships Each OSPF router maintains an identical LSDB within the same area. ✅ Key Characteristics: Feature Description Scope One LSDB per OSPF area Source Built from received LSAs Consistency All routers in an area have identical LSDBs Purpose Used as input for SPF algorithm to calculate best paths ⚙️ How the SPF Algorithm Works in OSPF OSPF uses Dijkstra’s Shortest Path First (SPF) algorithm to compute the shortest (lowest-cost)...