11–20 of 29 posts
We've just released our internal application powered by Node.js — our first. Since releasing we've been experiencing random 504 errors with no way of tracking them down, since they run in a Dokku container. Attaching to the logs displays nothing either.
This will really help! Thanks guys!
Does anyone know if New Relic can be used in a more limited capacity with unsupported languages? I've been building an OpenResty/Lapis app (Lua) and would love to be able to get some visibility into my Heroku dynos.
We're working on a somehow similar product that works by understanding the network traffic received and sent by your application. This means it can be language independent. http://packetbeat.com/
On a side note, the font you guys use for parts of your site is way too thin. It's really hard to read. See the items in the bottom/middle: http://cl.ly/image/2H0r1d1b210p
Earlier quoted context omitted.
We're working on a somehow similar product that works by understanding the network traffic received and sent by your application. This means it can be language independent. http://packetbeat.com/
That's really cool! Great name, too. Probably a little less comprehensive than New Relic's offering, but I like that you don't have to do any kind of integration. On a side note, the font you guys use for parts of your site is way too thin. It's really hard to read. See the items in the bottom/middle: http://cl.ly/image/2H0r1d1b210p
Since node's native support won't land until 0.12, does anyone know what the downsides of the polyfill are? Is there a much larger performance hit?
Is the best reason to use Node.js really just that it supports asynchrony? I'm sure Go also has that and Erlang has existed for a long time. There are many other options, so why Node?
I don't have any experience with Go or Erlang, but Node's particular brand of asynchrony is all about non-blocking IO. There are no threads -- all instructions happen in one thread.
Is the best reason to use Node.js really just that it supports asynchrony? I'm sure Go also has that and Erlang has existed for a long time. There are many other options, so why Node?
It also helps that tools like Grunt are Node based, causing frontend devs to look to Node when they need to stand up a back end. At least, Grunt was a pathway into Node for me anyway.
Is the best reason to use Node.js really just that it supports asynchrony? I'm sure Go also has that and Erlang has existed for a long time. There are many other options, so why Node?
Anyway, the reason probably has rather to do with JavaScript (V8's speed) and node's eco-system (tools, libraries).
[1]: https://docs.newrelic.com/docs/python/python-agent-and-torna...