nivstein

While JS is old, node.js, which spans many projects on GitHub, is a relatively new architecture, which has only gained traction in the last couple of years. This stands in comparison to Java, which has a much higher degree of consolidation due to its maturity as a server-side language (this is also true to an extend with Ruby).

I understand what you're saying, but I think the OP meant how often do you deploy on average. That is, take all the deployments you mentioned, regardless of the reason they happened, and average out.

Takipi lets you attach your own source code to the project, so you will see your original source code when viewing exceptions and other events, instead of decompiled Java. Support for prettier stack traces is in the planning.

Both the RAM and CPU overhead are configurable by you. The default values are max 5% CPU, and max 5% RAM.

We are currently in the process of adding a Heroku add-on :)

Hi Steve. These are some valid points you're making. We are currently considering an on-premises solution for precisely this situation you are describing.

Takipi's agent records information which is relevant to the issues which are detected (exceptions, latency problems, custom conditions set by the developer). The data and source code are then encrypted with your secret 256-bit AES key and stored by Takipi. This data is in turn decrypted in your browser and viewed by you at app.takipi.com.

This is actually a feature which is currently under consideration.

Very practical :) Takipi fully supports Glassfish, as well as all other major web servers and containers.

I'm sorry, Android development is currently not supported.