same for me 😅

Hahaha should be sharper now

No, I don't 🙂

@@SoftwareDeveloperDiaries which country do you live in?

I do, even more than that 😂

I'm thinking about making a separate course on JS performance, so stay tuned!

@@SoftwareDeveloperDiaries great news, thank you!

Thanks for the insight!

Thanks for your questions, I will try to answer them 🙂 1. If the payment fails, no event will be emitted. But once it is emitted, the service forgets it. That's what was meant by "forgetting". 2. You have multiple strategies depending on your use case and needs: a. Retry Mechanism: Implement a retry mechanism in your microservice. If the database operation fails, the service can try again after a certain period. b. Dead Letter Queue: If the error persists after several retries, you can send the message to a Dead Letter Queue (DLQ). The DLQ stores messages that could not be processed successfully. You can later analyze these messages and decide how to handle them. c.Event Sourcing: If a failure occurs, you can replay the events to bring your application back to a consistent state. d. Compensating Transactions: If your operation has side effects, you might need to execute a compensating transaction to undo the changes in case of failures. 3. No, the broker doesn't have to ACK back. It's more of a "fire and forget" pattern, meaning the event publisher usually doesn't wait for an ACK. 4. Agree :) 5. It doesn't. 6. Exactly.

Indeed, they are individual patterns. But EDA often relies on those :)

I'll cover that in a separate video soon!

Will do in one of the next videos 🤙

I can! Just stay tuned 😊

@@SoftwareDeveloperDiaries great will wait for it.

​@@SoftwareDeveloperDiariesHey that's awesome brother 🔥. Would like to see a payment integration using event driven architecture ❤.

Already have one! 🙂

By default - no, everything will run on a single core. But with the cluster mode - yes.

Glad I could help! 🤓

Hey mate, it's called "Palenight (Mild Contrast)"

Hey mate! Thanks for watching the video and for your thoughtful question! When it comes to handling concurrency in Node.js, there are indeed several options like child processes, Node.js cluster mode, and tools like PM2. Each has its own strengths and best-fit scenarios. Child processes: These are great when you need to run separate tasks concurrently, like handling CPU-intensive operations or interacting with external processes. Imagine you're building a web server with Node.js, and you need to generate PDF reports on the fly in response to user requests. However, generating PDFs is a CPU-intensive task that could block the event loop. Here, you could offload the PDF generation to a child process, allowing your main server to continue handling incoming requests without being blocked. Node.js cluster mode: This is specifically designed for scaling your Node.js application across multiple CPU cores. It's ideal for network-bound applications where you want to take advantage of parallelism to handle multiple requests simultaneously. Suppose you're developing a chat application where multiple users can connect simultaneously. Each incoming connection triggers some processing on the server, such as authentication and message handling. By using cluster mode, you can spawn multiple instances of your application across CPU cores, allowing you to handle more concurrent connections efficiently. PM2: PM2 is more of a process manager that helps in running and managing Node.js applications in production environments. It can handle clustering, monitoring, and auto-restarting of processes, making it convenient for deployment scenarios. Let's say you have a production-grade API serving hundreds of requests per minute. You want to ensure high availability and automatic restarts in case of failures. PM2 can manage your Node.js process, keeping it running smoothly by automatically restarting it if it crashes. Additionally, PM2 can monitor CPU and memory usage, allowing you to scale your application vertically or horizontally as needed. As for whether to use all of them in the same app, it really depends on your specific use case. Generally, you wouldn't use child processes and cluster mode together since they serve similar purposes. However, PM2 can complement either of them by providing additional management features. Hope this was helpful 😊

More to come! 😎