But what to do if something bad and unexpected happens? So, what should we do with our Node.js processes? Letting them crash. A lot of them in the market will give you way more visibility around the health of your Node.js processes, and you can live in peace when you are making sure your Node is running properly. So, in order to make sure that everything is running fine, you will need to have tools, some very known tools, New Relic, App Dynamics, Dynatrace, and N|Solid.
Julián: And also, rely on APM, some tools that are going to monitor the performance and the health of your Node.js Processes. So you are making sure that everything is fine. If you are using a reverse proxy, or a load balancer like nginx, or HAProxy, or you're using ELB, ALB, any type of application that is being the top layer of your Node.js process being constantly monitoring that the health check is returning okay. You can do it at your loa balancer level. So, pretty much as our recommendation, add a health check route, it's a simple route that is going to return a 200 status code, and you will need to set something to monitor that route.
#Xmodgames connection error crash how to#
She's going to also mention about how to add health checks to you Node.js processes. Julián: First, before getting into the bad place or when bad things happen, how to make sure that everything is good? What do we need to do to our Node applications to make sure they are running properly? So, first, as a recommendation, and there is going to be a workshop later about this specific thing, cloud native JS, don't miss this worship by Beth. You can do those things on Erlang, but still, Node is pretty lightweight, and you can easily restart and recover from a crash.
#Xmodgames connection error crash code#
And I always think about how to bring the same experience into Node.js, is not the same because you can't do whole code reloading or function swapping on Node. When I started learning Erlang back in 2014, I loved the fault tolerance options that these platform and language has. If you know about Erlang or leaks related crashes, just like a term that it's very common in that community. These best practices applies pretty much for web and network based applications because we are going to cover also the graceful shutdowns, but you can use them for other type of Node.js applications that are constantly running. We add a couple other more things to make sure you have a very good exit strategy for your Node.js Processes. Julián: If you go to the documentation, there are going to be pretty much the same recommendations that I'm going to be speaking about today. They were experiencing downtime, and we started to collect in a set of best practices and recommendations for them, that are aligned with the overall Node.js community. They were missing the very important information about why the Node processes were having issues or were crashing.
They didn't have logging strategies in place. And I saw a lot of different bad patterns out there on how other companies were doing error handling, and especially when the process were crashing or the process were dying. I was doing consulting work as a solutions architect, pleasing the customer, making sure they were using Node.js properly and they were successfully using Node. These are pretty much lessons learned while I was working at NodeSource, previously. Julián: So, a little bit of some background about this talk, why I presented this. Let's wait until my talk finish, and we can have some coffee to keep us awake. So, I know if you are like me right now, you are needing coffee. One is the NodeConf Colombia and the other is the JSConf Colombia. Sadly, I'm away from my country, but I always constantly in communication with my community, and that's pretty much true to main conferences that I organize. Right now, I work as a senior developer advocate for Heroku. That we have an amazing community, as Brian said. So, if you haven't gone there, please visit us. I come from a very beautiful town in Columbia called Medellín. So, as Brian said, my name is Julián Duque, it will be in proper Spanish.
0 kommentar(er)
