Book Image

Building Microservices with Spring

By : Dinesh Rajput, Rajesh R V
Book Image

Building Microservices with Spring

By: Dinesh Rajput, Rajesh R V

Overview of this book

Getting Started with Spring Microservices begins with an overview of the Spring Framework 5.0, its design patterns, and its guidelines that enable you to implement responsive microservices at scale. You will learn how to use GoF patterns in application design. You will understand the dependency injection pattern, which is the main principle behind the decoupling process of the Spring Framework and makes it easier to manage your code. Then, you will learn how to use proxy patterns in aspect-oriented programming and remoting. Moving on, you will understand the JDBC template patterns and their use in abstracting database access. After understanding the basics, you will move on to more advanced topics, such as reactive streams and concurrency. Written to the latest specifications of Spring that focuses on Reactive Programming, the Learning Path teaches you how to build modern, internet-scale Java applications in no time. Next, you will understand how Spring Boot is used to deploying serverless autonomous services by removing the need to have a heavyweight application server. You’ll also explore ways to deploy your microservices to Docker and managing them with Mesos. By the end of this Learning Path, you will have the clarity and confidence for implementing microservices using Spring Framework. This Learning Path includes content from the following Packt products: • Spring 5 Microservices by Rajesh R V • Spring 5 Design Patterns by Dinesh Rajput
Table of Contents (22 chapters)
Title Page
Copyright
About Packt
Contributors
Preface
Index

Core AOP terminology and concepts


As with other technologies, AOP has its own vocabularies. Let's start to learn some core AOP concepts and terminology. Spring used the AOP paradigm for the Spring AOP module. But unfortunately, terms used in the Spring AOP Framework are Spring-specific. These terms are used to describe AOP modules and features, but these aren't intuitive. In spite of this, these terms are used in order to understand AOP. Without an understanding of the AOP idiom you will not be able to understand AOP functionality. Basically, AOP is defined in terms of advice, pointcuts, and join points. Let's see the following figure that illustrates about the core AOP concepts and how they are tied together in the framework:

In the preceding figure, you can see an AOP functionality, it is known as Advices and it is implemented into multiple points. These points are known as Joint Points, these are defined by using an expression. These expression are known as pointcuts. Let's understand...