Previously I wrote about the difference in technology today compared to when MQ first came out. One of the areas that is most notable is network speed and how that relates to I/O as well as reliability.
1. Performance analysis for 3rd party Java software
- Deploy agent into 3rd party java apps, capture traces and see where the bottlenecks are
2.
RemoraJ is an open source Java byte code instrumentation agent designed to help developers profile running Java apps with little overhead.
The focal point of RemoraJ is to provide visibility into what’s coming in and out of your java app by tracking calls such as HTTP, JDBC, JMS, WebSocket, IO Streams, Kafka and other inter JVM/IPC communications.
I recently had a technical problem to solve that had me stumped. My first reflex was to read the available documentation, hoping to find an answer. I didn’t find what I was looking for.
I thought I’d share our experiences of running Solr in production. So far Solr 6.6.6 has been very stable provided GC, memory and other system resources are carefully managed. Here are some of the technical details which I hope will be useful to anyone considering this platform.
It is amazing how MQ has managed to stay relevant over all of these years. Looking back to when it first came out in the 1990’s, we were dealing with 2400 baud modems connected to remote locations running a number of different technologies, over spotty telephone lines using token ring protocols.
While we all continue to shelter in place, many companies are now going through the process of getting ready to reopen offices. Here in New York the government has put in place a rigorous reopening plan (one that I suspect is similar to that of most other countries and states).