Nice view on the succesfactors of change. These are overlooked frequently by lots of organizations wanting to change.
Nice view on the succesfactors of change. These are overlooked frequently by lots of organizations wanting to change.
The reason for introducing @Query is that we support some additional quirks (defining a count query e.g.) in it besides the fact which Fabian mentioned. Regarding the potential change of being able to use @NamedQuery on a method I don't think this is gonna happen as this does not make sense in a pure...
Hi Dan, I do not know dynaTrace 4.1. so I cannot tell you anything about the improvement but would be happy to get more information about this - maybe I can adjust my ratings. As I stated above, this was not a test of APM solutions but my personal opinion and experience with the tools....
dynaTrace has a new 4.1 release - it appears to address many configuration issues as well as scalability..... which version did you use in your analysis?
Thanks, this is informative! And there is a typo on "map -dump:file=path_to_file java_process_id": it is "jmap" rather than "map", right?
This is quite a good explanation. I'm a java developer and the first time I developed in objective-c I never saw all these similarities. Nice Post!
Thank you. Also could you write something on benchmarking.I hear this term very often at my organization where people talk writing benchmarking code to measure performance and sometimes using JMX to read application metrics?
Nice article!!! Would it possible to cover JVM parameters/flags and GC in a similar series down the road.