Some recent discussion in the WatchMeCode slack spawned a bit of research into creating custom errors through factory methods, while keeping the stack trace for those errors clean, in Node.js After a bit of digging, I found a good solution using Node’s Error.captureStackTrace method, and recorded a quick screencast to highlight it’s use.
In the previous episode, the Keen.io code for the analytics service was moved into a separate process using RabbitMQ. Toward the end of the episode, however, there were a number of issues that we ran into – most notably was an error in syntax not being reported correctly. In this episode, you’ll see the root […]
Working with errors and stack traces in your development environment is fairly simple. You probably have a console window open and are looking at the errors as they happen. You read the stack trace, look at the code that failed and fix the bug, because you’re working with the application right now. But what happens […]
In this interview, Derick talks to Aria Stewart, a software developer formerly at PayPal on the Kraken.js team. They delve into her talk, “Design for Retry: Microservices, REST, message busses and why idempotency is the only way to scale,” that she gave at Nodevember 2015 to discuss message queuing with services like RabbitMQ and Gearman.
Now that you have your application split out in to services, communicating through RabbitMQ, you need to know how to handle errors in the back-end code. What happens when the code throws an error and the processes crashes? How do you recover from that? With RabbitMQ, this is easier than you might think. And by […]
Error handling is an important part of any application. You don’t always want the application to just crash. Sometimes you want to be a little more graceful than that. This is true of any app – web or otherwise – including Express apps. Fortunately, Express provides a rather unique and very powerful way of handling […]