Book Image

Design Patterns and Best Practices in Java

By : Kamalmeet Singh, Adrian Ianculescu, Lucian-Paul Torje
Book Image

Design Patterns and Best Practices in Java

By: Kamalmeet Singh, Adrian Ianculescu, Lucian-Paul Torje

Overview of this book

Having a knowledge of design patterns enables you, as a developer, to improve your code base, promote code reuse, and make the architecture more robust. As languages evolve, new features take time to fully understand before they are adopted en masse. The mission of this book is to ease the adoption of the latest trends and provide good practices for programmers. We focus on showing you the practical aspects of smarter coding in Java. We'll start off by going over object-oriented (OOP) and functional programming (FP) paradigms, moving on to describe the most frequently used design patterns in their classical format and explain how Java’s functional programming features are changing them. You will learn to enhance implementations by mixing OOP and FP, and finally get to know about the reactive programming model, where FP and OOP are used in conjunction with a view to writing better code. Gradually, the book will show you the latest trends in architecture, moving from MVC to microservices and serverless architecture. We will finish off by highlighting the new Java features and best practices. By the end of the book, you will be able to efficiently address common problems faced while developing applications and be comfortable working on scalable and maintainable projects of any size.
Table of Contents (15 chapters)
Title Page
Packt Upsell
Contributors
Preface
Index

What should be expected in Java 11?


Java 11 is expected to be released somewhere around September 2018. It is worth taking a look at some of the important features expected in Java 11:

  • Local variable syntax for Lambda expression: Java 10 brought in a feature where we can use var while declaring the local variables, but it is not allowed to be used with Lambda expression right now. This restriction is supposed to go away with Java 11.
  • Epsilon-low overhead garbage collector: This JEP or JDK enhancement proposal talks about implementing a no-op garbage collector. In other words, this garbage collector is supposed to mainly focus on memory allocation and not implement any memory reclamation mechanism. It may be hard to imagine an application that does not need any garbage collections, but this is targeted at a set of applications that do not allocate too much heap memory or reuse the objects allocated, where in a sense, not too many objects become inaccessible or short-lived jobs. There are different...