Akka Streams Kafka

If you aren’t familiar with Akka you should read up on this fabulous new approach to Java performance development. Kafka streams of course is one of the best ways to implement streaming data to the datastore of your choice. The two together – marvelous!

Continue reading “Akka Streams Kafka”

DevOps Application Release and Deploy for Managers: The Payoff is Worth the Pursuit

By Peter Spung  (Credited to IBM DeveloperWorks Peter Spung)

Organizations that pursue DevOps application deployment automation and release management achieve significant payoff on their investment. These payoffs take two forms: operational payoffs, and economic outcome payoffs.2 Both of these types of payoffs are critical to the viability of the growing DevOps movement. As discussed in my first blog entry in this series, without a clear economic return to managers and organization leaders, the white-hot DevOps movement will cool and interest will wane. Continuing to add momentum and heat to the movement is an organization’s purpose of pursuing DevOps: delivering software based innovation and efficiency gains which is an organizational imperative worth pursuing, as discussed in my second blog post in this series. Continue reading “DevOps Application Release and Deploy for Managers: The Payoff is Worth the Pursuit”

Determine the Root Cause: The 5 Whys

Asking “Why?” may be a favorite technique of your three year old child in driving you crazy, but it could teach you a valuable Six Sigma quality lesson. The 5 Whys is a technique used in the Analyze phase of the Six Sigma DMAIC (Define, Measure, Analyze, Improve, Control) methodology. It is a great Six Sigma tool that does not involve data segmentation, hypothesis testing, regression or other advanced statistical tools, and in many cases can be completed without a data collection plan. Continue reading “Determine the Root Cause: The 5 Whys”

Thread.State in Java? BLOCKED vs WAITING

Article From GeekExplains Thursday, July 3, 2008

Difference between BLOCKED state and WAITING / TIMED_WAITING states?

When a thread calls Object.wait method, it releases all the acquired monitors and is put into WAITING (or TIMED_WAITING if we call the timeout versions of the wait method) state. Now when the thread is notified either by notify() or by notifyAll() call on the same object then the waiting state of the thread ends and the thread starts attempting to regain all the monitors which it had acquired at the time of wait call. At one time there may be several threads trying to regain (or maybe gain for the first time) their monitors. If more than one threads attempt to acquire the monitor of a particular object then only one thread (selected by the JVM scheduler) is granted the monitor and all other threads are put into BLOCKED state. Got the difference? Continue reading “Thread.State in Java? BLOCKED vs WAITING”

%d bloggers like this: