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

Summary


We talked about various architectural styles in this chapter, starting from layered architecture, MVC architecture, service-oriented architecture, microservices, and, finally, serverless architecture. One obvious question that comes to mind is: Which is the best among these styles of designing an application. The answer to this question is also pretty obvious—it depends on the problem at hand. Well, if there was one architecture that could apply to all the problems, everyone would have been using that, and we would have talked only about that particular architecture style.

An important thing to note here is that these architectural styles are not mutually exclusive; in fact, they complement one another. So, most of the time, you may end up using a hybrid of these architectural styles. For example, if we are working on a service-oriented architecture-based design, we may see that the internal implementation of these services may be done based on layered or MVC architectures. Also,...