Skip to main content

Aspect-Oriented Programming

 In the context of Spring Framework, AOP is used to separate these cross-cutting concerns from the main business logic of your application, leading to cleaner and more maintainable code. Spring provides a powerful AOP framework that enables you to define and manage aspects, which are modules that encapsulate these cross-cutting concerns.

Here's how AOP works in Spring:

  1. Aspect: An aspect is a module that encapsulates a cross-cutting concern. It defines what should happen at a particular point (called a "joinpoint") in your application's execution. Aspects are defined using regular Java classes and annotations.

  2. Joinpoint: A joinpoint is a specific point in your application's execution, such as a method call or an exception being thrown. Aspects are applied to these joinpoints to carry out specific actions.

  3. Advice: An advice is the actual action that an aspect takes at a specific joinpoint. There are different types of advice, such as "before," "after," "around," etc. Advice is the code that gets executed when the joinpoint is reached.

  4. Pointcut: A pointcut is an expression that specifies a set of joinpoints where an aspect's advice should be applied. It defines the conditions under which the aspect's behavior is triggered.

  5. Weaving: Weaving is the process of integrating the aspect code into your application's codebase. This can happen at various stages, like compile time, load time, or runtime. Spring's AOP framework uses runtime weaving by default.

A typical example in a Spring application would be logging. Instead of adding logging code directly into your business logic classes, you can define a logging aspect that specifies when and how logging should occur. The aspect's advice gets executed at specified joinpoints, such as before a method call, and performs the logging action.

Here's a simple code snippet illustrating the basic concepts of AOP in Spring:

java
import org.aspectj.lang.annotation.Aspect;
import org.aspectj.lang.annotation.Before;
import org.springframework.stereotype.Component;

@Aspect
@Component
public class LoggingAspect {

    @Before("execution(* com.example.service.*.*(..))")
    public void beforeServiceMethodExecution() {
        System.out.println("Logging before service method execution...");
    }
}

In this example, the LoggingAspect class defines a before advice that gets executed before any method in the com.example.service package is called. It's a simple demonstration of how AOP in Spring works to separate cross-cutting concerns from the main application logic.

Overall, AOP in Spring provides a way to improve modularity, reusability, and maintainability of your codebase by keeping cross-cutting concerns separate from your business logic.

Comments

Post a Comment

Popular posts from this blog

How to create Annotation in Spring boot

 To create Custom Annotation in JAVA, @interface keyword is used. The annotation contains :  1. Retention :  @Retention ( RetentionPolicy . RUNTIME ) It specifies that annotation should be available at runtime. 2. Target :  @Target ({ ElementType . METHOD }) It specifies that the annotation can only be applied to method. The target cane be modified to:   @Target ({ ElementType . TYPE }) for class level annotation @Target ({ ElementType . FIELD }) for field level annotation @Retention ( RetentionPolicy . RUNTIME ) @Target ({ ElementType . FIELD }) public @ interface CustomAnnotation { String value () default "default value" ; } value attribute is defined with @ CustomAnnotation annotation. If you want to use the attribute in annotation. A single attribute value. Example : public class Books {           @CustomAnnotation(value = "myBook")     public void updateBookDetail() {         ...
Post a Comment
Read more

Kafka And Zookeeper SetUp

 Kafka And Zookeeper SetUp zookeeper download Link : https://www.apache.org/dyn/closer.lua/zookeeper/zookeeper-3.8.3/apache-zookeeper-3.8.3-bin.tar.gz Configuration: zoo.conf # The number of milliseconds of each tick tickTime =2000 # The number of ticks that the initial # synchronization phase can take initLimit =10 # The number of ticks that can pass between # sending a request and getting an acknowledgement syncLimit =5 # the directory where the snapshot is stored. # do not use /tmp for storage, /tmp here is just # example sakes. dataDir =/tmp/zookeeper # the port at which the clients will connect clientPort =2181 4 char whitelist in command arguments 4lw.commands.whitelist =* Start ZooKeeper Server $ bin/zkServer.sh start Check zookeeper status dheeraj.kumar@Dheeraj-Kumar bin % echo stat | nc localhost 2181 stat is 4 character whitelisted argument  Check Kafka running status : echo dump | nc localhost 2181 | grep broker Responsibility of Leader in Zookeeper: 1. Distrib...
Post a Comment
Read more

Auto retries in REST API clients On Java On Ease

  Writing REST clients to consume API endpoints has become commonplace. While consuming REST endpoints, we sometimes end up in a situation where a downstream service throws some kind of transient error that goes away when the API call is retried. In such situations, we ask ourselves — “What if my API client was smart enough that knew how to retry a failed call?” Some of us go the extra mile to implement our own custom code that can retry API calls on error. But mind you, it is not only about knowing how to retry. The client also has to know when to retry and when not to. If the error is irrecoverable such as 400 — Bad Request, there is no point in retrying. It might also have to know how to back off and how to recover from the error. Implementing all this by hand, and then repeating it over and over again in every API client is cumbersome. It also adds a lot of boilerplate code and makes things even worse. But if you are a Spring/Spring Boot developer, you will be surprised to know...
Post a Comment
Read more