Shulou(Shulou.com)06/02 Report--

In this issue, Xiaobian will bring you about why we want to migrate from Node.JS to Ruby on Rails. The article is rich in content and analyzed and described from a professional perspective. After reading this article, I hope you can gain something.

Disclaimer: This article is by no means a diatribe about the merits of Node.JS versus Ruby on Rails. It describes just some of the thinking that goes into our decision-making process, the reasons behind our decisions. Both frameworks are excellent, and both do their job well, which is why some of our modules still run on Node.JS.

I'm a big fan of Node.JS and think it's a very exciting technology and I believe it's going to get more popular. I really appreciate this technology-although we recently migrated the Targeter App from Node.JS to Ruby on Rails.

The reason we developed it using Node.JS was simple. I have a package that gets our app online quickly (it took us 54 hours to do it) and I use JavaScript more often than Ruby. Because our technical architecture involves MongoDB, my expertise only makes sense in the Node.JS environment. However, as the app grew in size, I realized that choosing Node.JS to implement the app was the wrong choice. Let me outline why.

Node.JS is ideal for applications that have a large number of short-lived requests. For traditional CRUD applications, it's also fine, but not ideal. PHP, Ruby, Python all have well-established, optimized frameworks for handling this kind of application. The idea that everything in Node.JS executes asynchronously has no effect on CRUD apps. Popular frameworks in other languages provide excellent caching techniques that meet all your needs, including asynchronous execution.

Node.JS is a very young technical framework, and its surrounding libraries are not very mature. I don't mean this in any way to offend the code donors, they're great, they've developed great libraries. However, most libraries need to be improved, and Node.JS's fast-growing environment means that each release comes with a lot of changes; when you're using a cutting-edge technology, it's important to keep up with the latest releases as quickly as possible. This creates a lot of trouble for entrepreneurial businesses.

Another reason is about testing. The testing framework in Node.JS is good, but it's not as good as the one on Django or RoR. For an app that gets a lot of code committed every day and is due to be released in a day or two, it's critical that the program doesn't go wrong, or your hard work won't pay off. No one wants to spend a day fixing some *** bug.

*** Even though our app is growing, with tens of thousands of hits per second, there are never a lot of requests; this is not a chat app! The main program tops out at 1000RPS, which is nothing compared to Ruby on Rails and Nginx.

If you're reading this post right now, you've seen all I have to say, and you're probably dying to know where our app still uses Node.JS. Well, our app consists of two parts. One is the interface, the part that users see, the other is the part responsible for report management, as well as the function of doing logs. The latter is a *** usage scenario for Node.JS where there are a lot of short-cycle requests. This part of the action needs to be done as soon as possible, even before our data push is complete. This is important because when the request is not finished, the browser continues to wait for the response to finish, which affects the user experience. The asynchronous nature of Node.JS saved us. The data is either stored in a database or processed, and once the request has been executed, the browser can start doing other important things.

The above is why we want to migrate from Node.JS to Ruby on Rails. If you happen to have similar doubts, you may wish to refer to the above analysis for understanding. If you want to know more about it, please pay attention to the industry information channel.

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.