Welcome Miroslav Wengner - Most under-appreciated patterns?

A few patterns which are not that common, but would add immense benefit?
And which patterns give the most bang for the buck, as they say?

Hi Wadnerkar,
it's interesting question and I hope I'm understanding it properly.
IMHO: although it may seems to be logical the usage of creational patterns is underestimated in Java, followed by structural or behavioural patterns. Concurrency patterns become important because any framework may not fully offer the full package of required functionalities, in other words a custom solutions are usually required.  

In the book, I expanded on the traditional GoF patterns and adapted them to today's context and expectations based on my experience with customers across industries over last decades. All patterns do contains the discussion about their effective implementation in regards to the platform itself.

back to your 1st question "A few patterns which are not that common, but would add immense benefit?"
answer: depends on the context and many times a combination of patterns, it is important to stay consistent with the Java platform itself. Pick any of pressented patterns, you will see benefits on many levels, the most important maintainability which means clarity and so on. (Book Chapters 1-6)

2nd question: "And which patterns give the most bang for the buck, as they say?"
answer: Check the Chapter 7 in my book: "Understanding Common Anti-patterns" there are some that can hurt a lot, including cloud environments

I hope it helps

Hi Miro,

Talking about GoF patterns. Did you left any of those patterns out of your book because they are outdated or not relevant in the modern days? Which ones would not be possible to implement with Java?

Hi There,
I didn't exclude any of them because they are still very relevant, even if the implementation varies depending on the platform and syntax knowledge. The book reveals the challenges of adopting newly added enhancements and their elegance. One of my goals was to help the reader use them effectively and provide not only links to the platform itself, but also the reason why. During my career I have seen many attempts to implement design patterns from the GoF book, primarily written in SmallTalk or C++, the result was not always as expected.

In my book, I expanded these patterns to 42, although many more can be found, but IMHO: they are just derivatives of already existing ones or collections of them.

The Anti-patterns section uncovers and explores a collection of common cases that can be observed at various stages of application development across industries.

to your question: "Which would not be possible to implement using Java?"

IMHO Java has limits but not implementation ones. It is one of the most powerful and efficient tools we have in the market, thanks to its ongoing renaissance, it provides more and more beauty in the implementation of maintainable code. Of course, in specific cases a deep knowledge of the platform is necessary, especially in today's largely concurrent nature of the required solutions.

  One of my goals was to enable readers to explore these details, show where to start, understand them, and use them,
I hope it helps!