1. REPL (Read-Eval-Print Loop): An interactive programming environment that takes single user inputs, executes them, and returns the result to the user, often used for testing snippets of code.
2. EventEmitter: A core class in Node.js that allows objects to emit events and listen for them, facilitating event-driven programming.
3. Child Process: A module in Node.js that allows the creation of child processes to execute shell commands or run other Node.js scripts concurrently.
4. CORS (Cross-Origin Resource Sharing): A security feature implemented in web browsers that restricts web pages from making requests to a different domain than the one that served the web page, often configured in Node.js applications.
5. dotenv: A popular Node.js package used to load environment variables from a
.env file into process.env, simplifying configuration management.6. WebSocket: A protocol that provides full-duplex communication channels over a single TCP connection, enabling real-time data transfer between clients and servers.
7. Body Parser: A middleware function in Express.js that parses incoming request bodies and makes the data available under
req.body, commonly used for handling form submissions.8. Rate Limiting: A technique used to control the number of requests a client can make to a server within a certain time frame, helping to prevent abuse and overload.
9. Authentication: The process of verifying the identity of a user or service, often implemented using strategies like JWT (JSON Web Tokens) or OAuth in Node.js applications.
10. Authorization: The process of determining whether a user has permission to perform a specific action or access certain resources after authentication has been completed.
11. Logging: The practice of recording application events and errors for monitoring and debugging purposes, often implemented using libraries like
winston or morgan.12. Static Files: Files served directly by the web server without any processing, such as HTML, CSS, JavaScript, images, and fonts, often handled by middleware in Express.js.
13. Proxy: A server that acts as an intermediary for requests from clients seeking resources from other servers, commonly used for load balancing and security.
14. Template Engine: A library used to generate HTML dynamically by embedding JavaScript code into HTML templates, examples include EJS, Pug, and Handlebars.
15. Session Management: The process of storing user session data on the server side to maintain state across multiple requests, often using libraries like
express-session.16. API Gateway: A server that acts as an entry point for client requests to various microservices, handling routing, authentication, and request aggregation.
17. Microservices: An architectural style where an application is composed of small, independent services that communicate over APIs, allowing for better scalability and maintainability.
18. Load Balancer: A device or software that distributes network traffic across multiple servers to ensure no single server becomes overwhelmed, improving performance and reliability.
19. Debugging Tools: Software tools used to test and debug Node.js applications, such as Chrome DevTools, Node Inspector, and Visual Studio Code's built-in debugger.
20. Deployment Pipeline: A set of automated processes that allow developers to build, test, and deploy applications consistently and reliably across different environments.