ConcurrentHashMap is used extensively in multi-threaded applications. The examples of multi-threaded applications are online gaming applications, chat applications, it adds the benefit of concurrency to the application. To make application more concurrent in nature, ConcurrentHashMap introduces a concept called ‘Parallelism’.
Continue reading “Parallelism in ConcurrentHashMap”
I am slightly hesitant to write this post, as it might attract some criticism. Nevertheless, I told myself there is nothing wrong with sharing my point of view (even though it might not be well accepted). I would like to share my personal experience regarding yesterday’s Monolithic and today’s Microservice architecture in this post.
Continue reading “Is today’s microservice more bloated than yesterday’s monolith?”
Java applications tend to contain hundreds (sometimes thousands) of threads. The majority of these threads are in WAITING, TIMED_WAITING (i.e., dormant) state, while only a small portion of the threads are actively executing lines of code. So, we were curious to know whether dormant threads consume less memory than active threads.
To figure out an answer to this question, we conducted a small study. Our findings were interesting, thus sharing with you.
Continue reading “Java threads – may not be memory effecient?”
If you want to learn about the architecture of the application, performance characteristics of the application, effectiveness of the engineering organization – lot of times (if not all the times), we will look at the Word documents, PowerPoint decks, Excel spreadsheets that have been put together by the engineers/managers/executives of that application. In these artifacts truth can be exaggerated, truth can be untold, truth can be misstated. In some cases, it can even contain lie. What do we mean by it?
Continue reading “WORD/POWERPOINT/EXCEL OR GC/THREAD/HEAP DUMPS”