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

Service-oriented architecture


When we talk about the service-oriented architecture (SOA) approach, we are talking about our application in terms of various services or reusable units. For example, let's take a look at an e-commerce shopping system, such as Amazon. It can be thought of as a combination of multiple services rather than a single application. We can think of a search service responsible for implementing a products search, a shopping cart service that will implement the maintenance of a shopping cart, a payment handling service that is independently handling payments, and so on. The idea is to break your application into services that can be developed, deployed, and maintained independently of one another.

To understand the advantage of the service-oriented architecture approach, let's consider a case where we are able to divide the application into 10 independent services. So, we have reduced the complexity of the architecture by 10 times. We are able to divide the team into...