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

Serverless architecture


In all the architectural styles we have discussed so far, there is one common factor: dependency on the infrastructure. Whenever we are designing for an application, we need to think about important factors, such as these: How will the system scale up or scale down? How will the performance needs of the system be met? How will the services be deployed? How many instances and servers will we need? What will be their capacity? And so on.

These questions are important and at the same time tricky to answer. We have already moved from dedicated hardware to cloud-based deployments, which has eased our deployments, but still we need to plan for infrastructure requirements and answer all the aforementioned questions. Once hardware is acquired, whether on the cloud or otherwise, we need to maintain the health of it, and make sure that services are getting scaled based on their need, for which heavy devops involvement is required. Another important issue is underusage or overusage...