Spring Boot vs. Spring Framework: What’s the Difference?

By I Wayan Saryada in Spring Boot 0 Comment

Spring Boot and Spring Framework are closely related but serve distinct purposes in the world of Java development. Below is a comparison that highlights the key differences between the two:

1. Core Definition

  • Spring Framework:
    • A comprehensive framework that provides tools, libraries, and features to build a wide variety of Java applications. It includes modules such as Spring Core, Spring MVC, Spring Security, and more.
  • Spring Boot:
    • A framework built on top of the Spring Framework to simplify the development of Spring-based applications. It helps developers create standalone, production-ready applications with minimal configuration.

2. Configuration

  • Spring Framework:
    • Requires extensive XML configurations or Java-based configurations to set up an application.
    • Developers need to explicitly define and configure many components (e.g., beans, data sources, etc.).
  • Spring Boot:
    • Minimizes configuration by using auto-configuration and conventions over configurations.
    • Relies heavily on annotations like @SpringBootApplication, and dependencies are simplified via starters (e.g., spring-boot-starter-web, spring-boot-starter-data-jpa).
    • Enables a “just works” approach by setting up sensible defaults for most use cases.

3. Startup

  • Spring Framework:
    • Applications often rely on external application servers like Tomcat or Jetty for deployment. Configuration for deployment can be complex.
  • Spring Boot:
    • Provides an embedded application server (Tomcat, Jetty, or Undertow) so you can run the application directly—just like running a standalone Java program (using java -jar).
    • Simplifies startup and testing with its self-contained nature.

4. Dependencies

  • Spring Framework:
    • Developers need to manually manage dependencies for different project components and modules.
  • Spring Boot:
    • Uses Spring Boot starters, which are curated dependency descriptors that include the most commonly used libraries for specific types of applications.

5. Microservices

  • Spring Framework:
    • Not specifically designed for microservices but can be adapted with custom configurations.
  • Spring Boot:
    • Designed with microservices in mind. Provides embedded servers, REST API support, and tools like Spring Cloud to facilitate development and deployment of microservices.

6. Build and Deployment

  • Spring Framework:
    • Requires build tools to configure the application and deploy it on external application servers separately.
  • Spring Boot:
    • Generates standalone executable JAR or WAR files that include everything needed to run the application.

7. Learning Curve

  • Spring Framework:
    • Has a steeper learning curve because developers need to understand its modules and configure them manually.
  • Spring Boot:
    • Easier to get started with, thanks to its auto-configuration, starters, and reduced boilerplate code.

8. Use Cases

  • Spring Framework:
    • Suitable for complex, large-scale enterprise applications where fine-grained control over configurations, and application structures is needed.
  • Spring Boot:
    • Ideal for microservices architecture, cloud-native applications, rapid development, prototyping, and small to medium-sized applications.

9. Ecosystem

  • Both Spring Boot and Spring Framework are part of the broader Spring ecosystem. Spring Boot internally leverages the Spring Framework, so it doesn’t replace it but rather enhances it and makes it easier to use.

Example:

  • Spring Framework:
    Developers must explicitly set up dependencies, configure a dispatcher servlet, configure beans, and set up XML or Java-based configuration.
  • Spring Boot:
    A single annotation (@SpringBootApplication) bootstraps the application with default settings, embedded servers, and pre-configured components.

In Summary:

Think of Spring Boot as an opinionated way to work with the Spring Framework. If you need fine-grained control and customization, you’ll likely lean toward the Spring Framework. If you prefer convenience, rapid development, and minimal configuration, Spring Boot is the better choice.

How do I manage bean scopes in Spring Framework?

By I Wayan Saryada in Spring Core 0 Comment

In the Spring Framework, beans are defined with different scopes that govern their lifecycle and interaction with the container. The scope determines how many instances of a bean are created and how they are shared within an application.

Common Bean Scopes in Spring

Spring provides several bean scopes, and they are managed through the @Scope annotation or XML configuration. Below are the commonly used scopes:

1. Singleton (Default Scope)

  • This is the default scope in Spring.
  • Ensures there is only one shared instance of the bean per Spring container.
  • Suitable for stateless beans.
  • Example:
@Component
public class MySingletonBean {
    // Default scope is singleton
}

Or explicitly:

@Component
@Scope("singleton")
public class MySingletonBean {
}

2. Prototype

  • A new instance of the bean is created every time it is requested.
  • Useful for stateful, non-shared objects.
  • Example:
@Component
@Scope("prototype")
public class MyPrototypeBean {
}

In XML:

<bean id="myBean" class="com.example.MyBean" scope="prototype" />

3. Request

  • A new bean instance is created for every HTTP request and is specific to the lifecycle of that request.
  • Used in web applications.
  • Example:
@Component
@Scope("request")
public class MyRequestScopedBean {
}

4. Session

  • A new bean instance is created for every HTTP session and remains valid for the session lifecycle.
  • Mainly used in web applications for session-specific data.
  • Example:
@Component
@Scope("session")
public class MySessionScopedBean {
}

5. Application

  • A new bean instance is shared across the entire ServletContext (application-wide).
  • Example:
@Component
@Scope("application")
public class MyApplicationScopedBean {
}

6. WebSocket

  • A new instance is created for the lifecycle of a WebSocket session.
  • Example:
@Component
@Scope("websocket")
public class MyWebSocketScopedBean {
}

Setting Bean Scope

  1. Using Annotations:
    • Leverage the @Scope annotation along with Spring’s @Component, @Service, @Controller, or @RestController.
    • Example:
    @Service
@Scope("prototype")
public class PrototypeService {
}
  2. Using XML Configuration:
    • Define the scope inside the XML bean configuration.
    • Example:
    <bean id="myBean" class="com.example.MyService" scope="prototype" />
  3. Programmatically:
    • Define the bean and its scope programmatically using Java-based configuration.
    • Example:
    @Configuration
public class AppConfig {
  @Bean
  @Scope("prototype")
  public MyService myService() {
      return new MyService();
  }
}

Custom Scopes

You can define custom scopes in Spring by implementing the Scope interface. This is typically used in special cases like tenant-based architectures.

How the Container Manages Scopes

In singleton scope, the container ensures that only one instance of the bean exists at a time. In prototype and other scopes, however, the container provides a fresh instance depending on the request but does not manage the full lifecycle, such as destroying the bean (in the case of prototype beans).
If you use scopes such as request, session, or websocket, Spring’s WebApplicationContext is responsible for managing the beans’ lifecycle.

Key Points:

  • Singleton Scope is the default scope in Spring.
  • For web applications, consider request, session, or application scopes for beans tied to web-specific functionalities.
  • For stateful beans, do not use Singleton scope unless thread safety is accounted for.
  • Custom Scope definitions can extend the functionality of bean management.

What Is Spring Boot? A Beginner’s Introduction to Rapid Java Development

By I Wayan Saryada in Spring Boot 0 Comment

Spring Boot is a framework designed to simplify and speed up the development of Java-based applications, especially for web and microservices. It’s built on top of the Spring Framework but offers additional features to reduce the complexity of configuration, making it ideal for developers who want to quickly get started with production-ready applications. Below is an introduction to Spring Boot for beginners:

Key Features of Spring Boot

  1. Auto-Configuration:
    • Spring Boot automatically configures your application based on the libraries and dependencies it detects on the classpath. For example, if you include a library for an in-memory database like H2, Spring Boot configures a data source for you automatically.
  2. Embedded Servers:
    • Spring Boot comes with embedded HTTP servers (like Tomcat, Jetty, or Undertow) so you can run your web applications without deploying them to an external server.
  3. Starter Dependencies:
    • To simplify dependency management, Spring Boot provides “starter” dependencies—a curated set of libraries for specific functionalities. For example, spring-boot-starter-web is used for building web applications.
  4. Production-Ready Features:
    • Out of the box, it includes several production-ready features like health checks, metrics, and application monitoring via the Spring Boot Actuator module.
  5. Convention over Configuration:
    • Spring Boot adheres to the “convention over configuration” philosophy, which minimizes the need for manual setup. It works with sensible defaults but allows for customization where required.
  6. Developer Tools:
    • Spring Boot DevTools enhances the development experience by enabling features like hot reloading, which speeds up development cycles.

Why Use Spring Boot?

  • Rapid Development:
    Its default configurations allow developers to create standalone applications quickly without needing to write boilerplate code.
  • Microservices-Friendly:
    Spring Boot is highly suitable for building microservices architectures, thanks to its lightweight setup and embedded server capabilities.
  • Seamless Integration:
    It integrates easily with other Spring projects (e.g., Spring Data, Spring Security, etc.) and third-party libraries.
  • Great Ecosystem:
    The expansive Spring ecosystem includes numerous supported tools and plugins.
  • Minimized XML Configuration:
    You no longer need to deal with verbose XML configurations that were common in traditional Spring Framework setups, as most configurations can now be done using annotations or property files.

How Spring Boot Works

When creating a Spring Boot application:

  1. Start with a Starter Project:
    Use Spring Initializr, a web-based tool, to generate a base project with the desired dependencies.
  2. Dependency Injection:
    Utilize Spring’s core dependency injection (IoC Container) to wire together application components.
  3. Annotations:
    Spring Boot provides a set of annotations like @SpringBootApplication, @RestController, and @Bean to simplify development.
  4. Application Properties:
    The application.properties (or application.yml) file is used to customize configurations.
  5. Single Entry Point:
    Applications built with Spring Boot typically have a main class annotated with @SpringBootApplication, which acts as an entry point for the application.

Hello World Example with Spring Boot

Here’s an example of a basic Spring Boot application:

// Main application class
package org.kodejava.spring;

import org.springframework.boot.SpringApplication;
import org.springframework.boot.autoconfigure.SpringBootApplication;

@SpringBootApplication
public class DemoApplication {
    public static void main(String[] args) {
        SpringApplication.run(DemoApplication.class, args);
    }
}

// Example REST Controller
package org.kodejava.spring;

import org.springframework.web.bind.annotation.GetMapping;
import org.springframework.web.bind.annotation.RestController;

@RestController
public class HelloWorldController {
    @GetMapping("/")
    public String helloWorld() {
        return "Hello, World!";
    }
}

To run this application:

  1. Run the DemoApplication class.
  2. Open a browser and navigate to `http://localhost:8080` to see “Hello, World!”

When to Use Spring Boot

  • You want to rapidly build standalone web or microservices.
  • You prefer convention over configuration.
  • You need ready-to-use tools for monitoring, metrics, and controlling your applications.
  • You want the simplicity of an embedded web server for quick deployment.

Conclusion

Spring Boot is a powerful framework that makes Java development faster, simpler, and more streamlined. Its rich ecosystem, ease of use, and production-ready features make it a great choice for developers at all levels, from beginners to experienced professionals.

Maven Dependencies

<dependencies>
    <dependency>
        <groupId>org.springframework.boot</groupId>
        <artifactId>spring-boot-starter-web</artifactId>
        <version>3.4.4</version>
    </dependency>
</dependencies>

How do I use constructor vs setter injection in Spring Framework?

By I Wayan Saryada in Spring Core 0 Comment

In the Spring Framework, dependency injection is a design pattern used to implement inversion of control (IoC). There are two main ways to inject dependencies into a Spring bean: constructor injection and setter injection. Below is an explanation of both, along with when and how to use them.

Constructor Injection

With constructor injection, dependencies are provided through the class constructor. This means that the required dependencies are injected while the bean is being instantiated.

Example:

package org.kodejava.spring;

import org.springframework.stereotype.Component;

@Component
public class ExampleService {

    private final Dependency dependency;

    // Constructor Injection
    public ExampleService(Dependency dependency) {
        this.dependency = dependency;
    }

    public void performAction() {
        dependency.doSomething();
    }
}

Benefits of Constructor Injection:

  1. Immutability:
    • Dependencies must be provided at the time of object creation, making the object immutable after construction.
    • This makes the object safer and helps reduce bugs.
  2. Mandatory dependencies:
    • Forces the consumer of the class to supply all required dependencies, avoiding the risk of . NullPointerException
  3. Better for testing:
    • Enables better support for testing because the dependencies can be easily mocked or injected during object creation.
  4. Cleaner design:
    • Encourages proper design by clearly stating required dependencies upfront.

Drawbacks:

  • Not as flexible when you need to inject optional dependencies, since constructors get unwieldy with too many parameters.

Setter Injection

With setter injection, the dependencies are provided via public setter methods after the bean is instantiated.

Example:

package org.kodejava.spring;

import org.springframework.beans.factory.annotation.Autowired;
import org.springframework.stereotype.Component;

@Component
public class ExampleService {

   private Dependency dependency;

   // Setter Injection
   @Autowired
   public void setDependency(Dependency dependency) {
      this.dependency = dependency;
   }

   public void performAction() {
      if (dependency != null) {
         dependency.doSomething();
      } else {
         throw new IllegalStateException("Dependency not initialized");
      }
   }
}

Benefits of Setter Injection:

  1. Optional dependencies:
    • Suitable for when some dependencies are optional, as they can be assigned (or remain unassigned) after the bean instance is created.
  2. Flexibility:
    • Allows updating/replacing dependencies later if needed (though this may lead to issues with immutability).
  3. Better for backward compatibility:
    • Useful for older codebases where constructors may already exist, and introducing a large constructor could break existing code.

Drawbacks:

  • Dependencies can be set or modified at any time, leaving the object in an inconsistent or unpredictable state.
  • There is no guarantee that mandatory dependencies are set, which increases the risk of runtime errors if they are missing.

When to Use Constructor Injection vs Setter Injection?

Factor Constructor Injection Setter Injection
Mandatory dependencies Use when a dependency is essential for the bean to function properly. Not ideal for mandatory dependencies since they can be forgotten or missed.
Optional dependencies Use if you can design your code with multiple constructors for optional behaviors (slightly more complex). Better for optional dependencies, since the setters are invoked as needed.
Immutability Guarantees immutability after bean instantiation. Object remains mutable.
Object complexity Becomes harder to manage when there are too many dependencies. Useful when the bean has several dependencies and not all need to be injected.
Testing Easier to test with mocks or stubs because all dependencies are set when constructing the object. Slightly more verbose for tests as setters might need to be initialized.

Using @Autowired in Spring

Spring automates injection using the @Autowired annotation, which works with both constructor and setter injection.

Constructor Injection with @Autowired:

package org.kodejava.spring;

import org.springframework.beans.factory.annotation.Autowired;
import org.springframework.stereotype.Component;

@Component
public class ExampleService {

    private final Dependency dependency;

    @Autowired // Optional in Spring (constructor with 1 argument is auto-detected)
    public ExampleService(Dependency dependency) {
        this.dependency = dependency;
    }
}

Setter Injection with @Autowired:

import org.springframework.beans.factory.annotation.Autowired;
import org.springframework.stereotype.Component;

@Component
public class ExampleService {

    private Dependency dependency;

    @Autowired
    public void setDependency(Dependency dependency) {
        this.dependency = dependency;
    }
}

Best Practices

  1. Generally, default to constructor injection, because:
    • It ensures all required dependencies are injected at creation time.
    • It aligns with good object-oriented practices (e.g., immutability, better encapsulation).
  2. Use setter injection sparingly, mostly for:
    • Optional dependencies.
    • Situations where backward compatibility is a concern.
  3. Avoid mixing setter and constructor injection for the same dependency, as it can lead to confusion.
  4. For constructor injection with a large number of dependencies, consider refactoring (e.g., using a helper class to encapsulate related dependencies).

Maven Dependencies

<dependency>
    <groupId>org.springframework</groupId>
    <artifactId>spring-context</artifactId>
    <version>6.2.6</version>
</dependency>

Maven Central

How do I define application context using ClassPathXmlApplicationContext and AnnotationConfigApplicationContext?

By I Wayan Saryada in Spring Core 0 Comment

To define an application context in Spring using ClassPathXmlApplicationContext or AnnotationConfigApplicationContext, you establish the context for your Spring-managed beans using XML configuration in the former, and Java-based annotations in the latter. Here’s how each can be used:

1. Using ClassPathXmlApplicationContext

This approach loads the application context configuration from an XML file.

Example:

package org.kodejava.spring;

import org.kodejava.spring.MyBean;
import org.springframework.context.ApplicationContext;
import org.springframework.context.support.ClassPathXmlApplicationContext;

public class XmlAppContextExample {
    public static void main(String[] args) {
        // Load application context from XML configuration file
        ApplicationContext context = new ClassPathXmlApplicationContext("applicationContext.xml");

        // Retrieve a bean from the context
        MyBean myBean = context.getBean(MyBean.class);
        System.out.println(myBean.sayHello());
    }
}

Key Points:

  • The XML file (applicationContext.xml) must be placed in the classpath.
  • Define your beans and their dependencies inside the XML file.

Example applicationContext.xml:

<beans xmlns="http://www.springframework.org/schema/beans"
       xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
       xsi:schemaLocation="http://www.springframework.org/schema/beans
           https://www.springframework.org/schema/beans/spring-beans.xsd">

    <!-- Define a simple bean -->
    <bean id="myBean" class="org.kodejava.spring.MyBean"/>
</beans>

2. Using AnnotationConfigApplicationContext

This approach leverages Java-based configuration and annotations to define the context and beans.

Example:

package org.kodejava.spring;

import org.springframework.context.ApplicationContext;
import org.springframework.context.annotation.AnnotationConfigApplicationContext;

public class AnnotationAppContextExample {
    public static void main(String[] args) {
        // Load application context from a Java configuration class
        ApplicationContext context = new AnnotationConfigApplicationContext(AppConfig.class);

        // Retrieve a bean from the context
        MyBean myBean = context.getBean(MyBean.class);
        System.out.println(myBean.sayHello());
    }
}

Java Configuration Class:

package org.kodejava.spring;

import org.springframework.context.annotation.Bean;
import org.springframework.context.annotation.ComponentScan;
import org.springframework.context.annotation.Configuration;

@Configuration
@ComponentScan(basePackages = "org.kodejava.spring") // Automatically detect beans in this package
public class AppConfig {

    // Optionally define beans manually if needed
    @Bean
    public MyBean myBean() {
        return new MyBean();
    }
}

Example Component Class:

package org.kodejava.spring;

import org.springframework.stereotype.Component;

@Component
public class MyBean {
    public String sayHello() {
        return "Hello from MyBean!";
    }
}

Summary of Each Approach:

Feature ClassPathXmlApplicationContext AnnotationConfigApplicationContext
Configuration Style XML-based Java-based annotations
Setup Effort Requires maintaining XML files separately Use annotations and Java configuration classes
Readability Can become verbose as the application grows Clean and concise, readable for Java developers
Dependency Injection Declared in XML Defined via @Component, @Bean, @Autowired, etc.
Preferred Use Case Legacy or existing applications Modern, annotation-based Spring applications

For modern Spring applications, AnnotationConfigApplicationContext (annotation-based configuration) is the recommended approach due to its ease of use, better readability, and alignment with modern Spring best practices.

Maven Dependencies

<dependency>
    <groupId>org.springframework</groupId>
    <artifactId>spring-context</artifactId>
    <version>6.2.6</version>
</dependency>

Maven Central