Spring Boot 4 Microservices & REST APIs · Lezione

Operazioni CRUD con REST

Implementi le operazioni Create, Read, Update e Delete per le entità tramite endpoint REST.

Operazioni CRUD con REST è una lezione Spring Boot 4 Microservices & REST APIs gratuita su CoddyKit. Questa è la lezione 5 di 6. Puoi leggere la lezione completa qui gratuitamente — poi esercitati direttamente nel browser con un editor di codice integrato e un tutor IA disponibile 24/7. Fa parte del percorso di apprendimento Spring Boot 4 Microservices & REST APIs, e i tuoi progressi si sincronizzano tra il web e l'app CoddyKit. Il corso Spring Boot 4 Microservices & REST APIs include 6 lezioni in totale.

Parti di questa lezione non sono ancora state tradotte e vengono mostrate in inglese.

CRUD Operations: The Basics

Welcome to implementing CRUD operations with Spring Boot! CRUD stands for Create, Read, Update, and Delete.

These are the four fundamental operations for persistent storage, allowing you to manage data in your application.

In REST APIs, each CRUD operation typically maps to a specific HTTP method.

Mapping CRUD to HTTP Methods

Understanding how CRUD maps to HTTP methods is key for RESTful design:

Create (C): Handled by POST requests.
Read (R): Handled by GET requests.
Update (U): Handled by PUT requests.
Delete (D): Handled by DELETE requests.

We'll use a simple Product entity and its ProductRepository from previous lessons.

Implementing Create (POST)

To create a new resource, we use the POST HTTP method. In Spring Boot, this is handled by the @PostMapping annotation.

The new product data is sent in the request body, which Spring automatically maps to our Product object using @RequestBody.

Create Product Example

Here's how you'd create an endpoint to add a new product. Run it, then try adding a product via a tool like Postman (e.g., POST to /api/products with JSON body {"name": "Laptop", "price": 1200.0}).

package com.coddykit.crud;

import jakarta.persistence.*;
import org.springframework.boot.SpringApplication;
import org.springframework.boot.autoconfigure.SpringBootApplication;
import org.springframework.data.jpa.repository.JpaRepository;
import org.springframework.stereotype.Repository;
import org.springframework.web.bind.annotation.*;
import org.springframework.beans.factory.annotation.Autowired;

@Entity
public class Product {
    @Id
    @GeneratedValue(strategy = GenerationType.IDENTITY)
    private Long id;
    private String name;
    private double price;
    public Product() {}
    public Product(String name, double price) {
        this.name = name;
        this.price = price;
    }
    public Long getId() { return id; }
    public void setId(Long id) { this.id = id; }
    public String getName() { return name; }
    public void setName(String name) { this.name = name; }
    public double getPrice() { return price; }
    public void setPrice(double price) { this.price = price; }
}

@Repository
interface ProductRepository extends JpaRepository<Product, Long> {}

@RestController
@RequestMapping("/api/products")
class ProductController {
    @Autowired
    private ProductRepository productRepository;

    @PostMapping
    public Product createProduct(@RequestBody Product product) {
        return productRepository.save(product);
    }
}

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

Implementing Read (GET)

Reading resources is done with the GET HTTP method. We'll create two types of read operations:

Get all products: Maps to @GetMapping.
Get a single product by ID: Maps to @GetMapping("/{id}") using a @PathVariable.

When fetching by ID, we use Optional to handle cases where the product might not exist.

Read Products Example

This code adds methods to fetch all products and a single product by its ID. Notice the use of ResponseEntity to return a 404 if a product isn't found.

package com.coddykit.crud;

import jakarta.persistence.*;
import org.springframework.boot.SpringApplication;
import org.springframework.boot.autoconfigure.SpringBootApplication;
import org.springframework.data.jpa.repository.JpaRepository;
import org.springframework.stereotype.Repository;
import org.springframework.web.bind.annotation.*;
import org.springframework.beans.factory.annotation.Autowired;
import org.springframework.http.ResponseEntity;
import java.util.List;
import java.util.Optional;

@Entity
public class Product {
    @Id
    @GeneratedValue(strategy = GenerationType.IDENTITY)
    private Long id;
    private String name;
    private double price;
    public Product() {}
    public Product(String name, double price) {
        this.name = name;
        this.price = price;
    }
    public Long getId() { return id; }
    public void setId(Long id) { this.id = id; }
    public String getName() { return name; }
    public void setName(String name) { this.name = name; }
    public double getPrice() { return price; }
    public void setPrice(double price) { this.price = price; }
}

@Repository
interface ProductRepository extends JpaRepository<Product, Long> {}

@RestController
@RequestMapping("/api/products")
class ProductController {
    @Autowired
    private ProductRepository productRepository;

    @GetMapping
    public List<Product> getAllProducts() {
        return productRepository.findAll();
    }

    @GetMapping("/{id}")
    public ResponseEntity<Product> getProductById(@PathVariable Long id) {
        Optional<Product> product = productRepository.findById(id);
        return product.map(ResponseEntity::ok)
                      .orElseGet(() -> ResponseEntity.notFound().build());
    }
}

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

Implementing Update (PUT)

To update an existing resource, we use the PUT HTTP method, annotated with @PutMapping.

The endpoint typically includes the resource's ID in the path (/{id}) to identify which item to update, and the updated data is sent in the @RequestBody.

Update Product Example

This method updates an existing product. It first checks if the product exists using the ID from the path. If found, it updates the fields from the request body and saves it.

package com.coddykit.crud;

import jakarta.persistence.*;
import org.springframework.boot.SpringApplication;
import org.springframework.boot.autoconfigure.SpringBootApplication;
import org.springframework.data.jpa.repository.JpaRepository;
import org.springframework.stereotype.Repository;
import org.springframework.web.bind.annotation.*;
import org.springframework.beans.factory.annotation.Autowired;
import org.springframework.http.ResponseEntity;
import java.util.Optional;

@Entity
public class Product {
    @Id
    @GeneratedValue(strategy = GenerationType.IDENTITY)
    private Long id;
    private String name;
    private double price;
    public Product() {}
    public Product(String name, double price) {
        this.name = name;
        this.price = price;
    }
    public Long getId() { return id; }
    public void setId(Long id) { this.id = id; }
    public String getName() { return name; }
    public void setName(String name) { this.name = name; }
    public double getPrice() { return price; }
    public void setPrice(double price) { this.price = price; }
}

@Repository
interface ProductRepository extends JpaRepository<Product, Long> {}

@RestController
@RequestMapping("/api/products")
class ProductController {
    @Autowired
    private ProductRepository productRepository;

    @PutMapping("/{id}")
    public ResponseEntity<Product> updateProduct(
        @PathVariable Long id, @RequestBody Product productDetails) {
        Optional<Product> product = productRepository.findById(id);
        if (product.isPresent()) {
            Product existingProduct = product.get();
            existingProduct.setName(productDetails.getName());
            existingProduct.setPrice(productDetails.getPrice());
            return ResponseEntity.ok(productRepository.save(existingProduct));
        } else {
            return ResponseEntity.notFound().build();
        }
    }
}

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

Implementing Delete (DELETE)

To remove a resource, we use the DELETE HTTP method, annotated with @DeleteMapping.

Similar to update, the ID of the resource to delete is passed as a @PathVariable. After deletion, it's common to return a 204 No Content status.

Delete Product Example

This method deletes a product by ID. It finds the product and, if present, deletes it. Returning ResponseEntity.noContent().build() is a good practice for successful deletions.

package com.coddykit.crud;

import jakarta.persistence.*;
import org.springframework.boot.SpringApplication;
import org.springframework.boot.autoconfigure.SpringBootApplication;
import org.springframework.data.jpa.repository.JpaRepository;
import org.springframework.stereotype.Repository;
import org.springframework.web.bind.annotation.*;
import org.springframework.beans.factory.annotation.Autowired;
import org.springframework.http.ResponseEntity;
import java.util.Optional;

@Entity
public class Product {
    @Id
    @GeneratedValue(strategy = GenerationType.IDENTITY)
    private Long id;
    private String name;
    private double price;
    public Product() {}
    public Product(String name, double price) {
        this.name = name;
        this.price = price;
    }
    public Long getId() { return id; }
    public void setId(Long id) { this.id = id; }
    public String getName() { return name; }
    public void setName(String name) { this.name = name; }
    public double getPrice() { return price; }
    public void setPrice(double price) { this.price = price; }
}

@Repository
interface ProductRepository extends JpaRepository<Product, Long> {}

@RestController
@RequestMapping("/api/products")
class ProductController {
    @Autowired
    private ProductRepository productRepository;

    @DeleteMapping("/{id}")
    public ResponseEntity<Void> deleteProduct(@PathVariable Long id) {
        Optional<Product> product = productRepository.findById(id);
        if (product.isPresent()) {
            productRepository.delete(product.get());
            return ResponseEntity.noContent().build();
        } else {
            return ResponseEntity.notFound().build();
        }
    }
}

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

Quick Check: HTTP Methods

Which HTTP method is typically used to update an existing resource in a REST API, and which one is for creating a new resource?

Recap: CRUD with REST

You've successfully learned how to implement all four CRUD operations using Spring Boot REST controllers!

Create: Use @PostMapping.
Read: Use @GetMapping (for all or by ID).
Update: Use @PutMapping.
Delete: Use @DeleteMapping.

These are the building blocks for almost any data-driven API. Next, we'll explore validation and error handling!

Domande Frequenti

La lezione «Operazioni CRUD con REST» è gratuita?

Sì — il testo completo di «Operazioni CRUD con REST» è gratuito qui sul web. Per esercitarvi in modo interattivo (un editor di codice integrato e un tutor IA 24/7) e sbloccare il resto del corso Spring Boot 4 Microservices & REST APIs, passa a CoddyKit PRO. Il corso Spring Boot 4 Microservices & REST APIs include 6 lezioni in totale.

Cosa imparerò in «Operazioni CRUD con REST»?

Implementi le operazioni Create, Read, Update e Delete per le entità tramite endpoint REST. Eserciti Spring Boot 4 Microservices & REST APIs con codice pratico che esegui direttamente nel browser, e un tutor IA 24/7 risponde alle tue domande mentre lavori sulla lezione.

Ho bisogno di esperienza per iniziare Spring Boot 4 Microservices & REST APIs?

Non è richiesta alcuna esperienza precedente. Spring Boot 4 Microservices & REST APIs su CoddyKit è strutturato per principianti e studenti avanzati, quindi puoi iniziare da qui o dall'inizio e procedere al tuo ritmo. Questa è la lezione 5 di 6.

Quanto tempo richiede la lezione «Operazioni CRUD con REST»?

La maggior parte delle lezioni CoddyKit richiede circa 5–10 minuti. Ogni lezione è breve e interattiva, quindi fai progressi costanti e riprendi esattamente da dove hai lasciato su web e app.

Posso scrivere ed eseguire codice in questa lezione Spring Boot 4 Microservices & REST APIs?

Sì. Ogni lezione Spring Boot 4 Microservices & REST APIs include un editor di codice integrato, quindi scrivi ed esegui codice reale direttamente nel tuo browser e ricevi feedback istantaneo dall'IA — nessuna configurazione locale necessaria.

Tutte le lezioni di questo corso

← Torna a Spring Boot 4 Microservices & REST APIs