0Pricing
Spring Boot 4 Complete Guide · Lección

Flujos de reader, processor y writer orientados a chunks

Conecte los componentes ItemReader, ItemProcessor e ItemWriter para procesar chunks de forma escalable.

Flujos de reader, processor y writer orientados a chunks es una lección gratuita de Spring Boot 4 Complete Guide en CoddyKit. Esta es la lección 2 de 4. Puedes leer la lección completa abajo gratuitamente — luego la practicas en el navegador con un editor de código integrado y un tutor de IA 24/7. Forma parte de la ruta de aprendizaje de Spring Boot 4 Complete Guide, y tu progreso se sincroniza en la web y la app de CoddyKit. El curso de Spring Boot 4 Complete Guide incluye 4 lecciones en total.

Partes de esta lección aún no han sido traducidas y se muestran en inglés.

Why Chunk-Oriented Processing?

Spring Batch reads, processes, and writes data in chunks instead of one record at a time. A chunk is a configurable number of items (the commit-interval) handled inside a single transaction.

  • Read N items one by one with an ItemReader.
  • Process each item with an ItemProcessor.
  • Write the whole batch of N at once with an ItemWriter.

Writing in bulk and committing per chunk is what makes batch jobs scale to millions of rows without exhausting memory.

The Three Core Interfaces

Every chunk step is built from three single-method interfaces. Knowing their contracts is the foundation of the whole pattern.

  • ItemReader<I> → I read() returns the next item, or null when the input is exhausted.
  • ItemProcessor<I, O> → O process(I item) transforms an input into an output; returning null filters the item out.
  • ItemWriter<O> → void write(Chunk<? extends O> chunk) persists the accumulated chunk.
public interface ItemReader<I> {
    I read() throws Exception; // null = end of input
}

public interface ItemProcessor<I, O> {
    O process(I item) throws Exception; // null = filter
}

public interface ItemWriter<O> {
    void write(Chunk<? extends O> chunk) throws Exception;
}

Defining a Domain Type

A chunk step flows typed data from reader to processor to writer. Let's model a simple input and output. The reader emits raw Customer records and the writer stores normalized ones.

Using a Java record keeps these immutable value types concise. This snippet is plain Java with no framework, so it runs standalone.

public class DomainDemo {
    record Customer(String name, String email) {}

    public static void main(String[] args) {
        Customer c = new Customer("  Ada ", "ADA@MAIL.COM");
        Customer normalized = new Customer(
                c.name().trim(),
                c.email().toLowerCase());
        System.out.println(normalized);
    }
}

Building the ItemReader

For database input, JdbcCursorItemReader streams rows one at a time so memory stays flat. You give it a DataSource, a SQL query, and a RowMapper to turn each row into a domain object.

Spring Batch calls read() repeatedly until it returns null, advancing the cursor each time.

@Bean
public JdbcCursorItemReader<Customer> reader(DataSource dataSource) {
    return new JdbcCursorItemReaderBuilder<Customer>()
            .name("customerReader")
            .dataSource(dataSource)
            .sql("SELECT name, email FROM customers WHERE active = true")
            .rowMapper((rs, rowNum) ->
                    new Customer(rs.getString("name"), rs.getString("email")))
            .build();
}

Building the ItemProcessor

The processor is where business logic lives: validation, enrichment, transformation, or filtering. Its input and output types may differ.

  • Return a transformed object to pass it downstream.
  • Return null to skip the item entirely — it never reaches the writer.

Keep processors stateless and idempotent so they behave correctly when chunks are retried.

@Bean
public ItemProcessor<Customer, Customer> processor() {
    return customer -> {
        if (customer.email() == null || !customer.email().contains("@")) {
            return null; // filter invalid records out of the chunk
        }
        return new Customer(
                customer.name().trim(),
                customer.email().toLowerCase());
    };
}

Building the ItemWriter

The writer receives the whole processed chunk at once via a Chunk<O>. Writing in bulk — one batched INSERT per chunk instead of one per row — is the key performance win.

JdbcBatchItemWriter uses a parameterized SQL statement and a bean-property parameter source to map fields automatically.

@Bean
public JdbcBatchItemWriter<Customer> writer(DataSource dataSource) {
    return new JdbcBatchItemWriterBuilder<Customer>()
            .dataSource(dataSource)
            .sql("INSERT INTO customers_clean (name, email) VALUES (:name, :email)")
            .beanMapped()
            .build();
}

Wiring the Chunk Step

A Step ties the three components together. The generic types <Customer, Customer> declare the input and output of the chunk, and the integer is the commit-interval.

With a chunk size of 100, Spring Batch reads 100 items, processes each, then writes all survivors in one transaction before committing.

@Bean
public Step chunkStep(JobRepository jobRepository,
                      PlatformTransactionManager txManager,
                      ItemReader<Customer> reader,
                      ItemProcessor<Customer, Customer> processor,
                      ItemWriter<Customer> writer) {
    return new StepBuilder("chunkStep", jobRepository)
            .<Customer, Customer>chunk(100, txManager)
            .reader(reader)
            .processor(processor)
            .writer(writer)
            .build();
}

Assembling the Job

A Job is an ordered set of steps. For a single chunk step, the job simply starts with it. Spring Boot auto-detects the Job bean and runs it on startup.

The JobRepository records execution metadata — status, read/write counts, and the last committed position — enabling restartability.

@Bean
public Job importCustomersJob(JobRepository jobRepository, Step chunkStep) {
    return new JobBuilder("importCustomersJob", jobRepository)
            .start(chunkStep)
            .build();
}

Choosing the Chunk Size

The commit-interval is a tuning lever, not a magic number.

  • Too small (e.g. 1): one transaction per row — high commit overhead, slow.
  • Too large (e.g. 100,000): bigger transactions, more memory and rollback cost if a chunk fails.
  • Typical sweet spot: 100–1000, tuned by measuring throughput against your database and row size.

Remember: a failed item rolls back the entire chunk, so larger chunks mean more work redone on failure.

Fault Tolerance: Skip and Retry

Real input is messy. Wrap the step with .faultTolerant() to keep processing despite isolated failures.

  • .skip(...) — tolerate up to skipLimit bad items instead of failing the job.
  • .retry(...) — re-attempt transient errors (e.g. deadlocks) up to retryLimit before giving up.

On a skip or retry, Spring Batch re-scans the chunk item by item, isolating the offending record.

@Bean
public Step faultTolerantStep(JobRepository jobRepository,
                              PlatformTransactionManager txManager,
                              ItemReader<Customer> reader,
                              ItemProcessor<Customer, Customer> processor,
                              ItemWriter<Customer> writer) {
    return new StepBuilder("ftStep", jobRepository)
            .<Customer, Customer>chunk(100, txManager)
            .reader(reader)
            .processor(processor)
            .writer(writer)
            .faultTolerant()
            .skip(FlatFileParseException.class)
            .skipLimit(20)
            .retry(DeadlockLoserDataAccessException.class)
            .retryLimit(3)
            .build();
}

The Chunk Lifecycle in Order

Putting it together, each chunk follows the same loop inside one transaction:

  • 1. Read: call read() repeatedly until chunk-size items are buffered (or null ends input).
  • 2. Process: call process() on each item; nulls are filtered out.
  • 3. Write: pass the surviving items as one Chunk to write().
  • 4. Commit: commit the transaction and record progress in the JobRepository.

Then the loop repeats for the next chunk until the reader is exhausted.

Quick Check

Test your understanding of the chunk pipeline.

Recap

You wired a complete chunk-oriented flow in Spring Batch:

  • ItemReader streams input one item at a time, returning null at the end.
  • ItemProcessor transforms or filters items; null drops an item.
  • ItemWriter persists the whole chunk in bulk for performance.
  • The Step binds them with a chunk(size, txManager) commit-interval, and the Job orchestrates the steps.
  • Tune chunk size for throughput, and add .faultTolerant() with skip/retry for resilient pipelines.

This read-process-write loop, committed per chunk, is the backbone of scalable batch processing.

Preguntas frecuentes

¿La lección «Flujos de reader, processor y writer orientados a chunks» es gratis?

Sí — el texto completo de «Flujos de reader, processor y writer orientados a chunks» es gratis para leer aquí en la web. Para practicarla de forma interactiva (editor de código integrado y tutor de IA 24/7) y desbloquear el resto del curso de Spring Boot 4 Complete Guide, actualiza a CoddyKit PRO. El curso de Spring Boot 4 Complete Guide incluye 4 lecciones en total.

¿Qué aprenderé en «Flujos de reader, processor y writer orientados a chunks»?

Conecte los componentes ItemReader, ItemProcessor e ItemWriter para procesar chunks de forma escalable. Practicas Spring Boot 4 Complete Guide con código real que ejecutas directamente en el navegador, y un tutor de IA 24/7 responde tus preguntas mientras trabajas en la lección.

¿Necesito experiencia previa para empezar Spring Boot 4 Complete Guide?

No se requiere experiencia previa. Spring Boot 4 Complete Guide en CoddyKit está estructurado para principiantes hasta estudiantes avanzados, así que puedes empezar aquí o desde el inicio y avanzar a tu ritmo. Esta es la lección 2 de 4.

¿Cuánto tiempo toma la lección «Flujos de reader, processor y writer orientados a chunks»?

La mayoría de las lecciones de CoddyKit toman alrededor de 5–10 minutos. Cada una es compacta e interactiva, así que avanzas constantemente y retomas exactamente por donde dejaste en la web y la app.

¿Puedo escribir y ejecutar código en esta lección de Spring Boot 4 Complete Guide?

Sí. Cada lección de Spring Boot 4 Complete Guide incluye un editor de código integrado, así que escribes y ejecutas código real directamente en tu navegador y obtienes retroalimentación instantánea de IA — sin configuración local necesaria.

Todas las lecciones de este curso

  1. Jobs, steps y el modelo JobRepository
  2. Flujos de reader, processor y writer orientados a chunks
  3. Tolerancia a fallos y políticas de skip y retry
  4. Particionamiento y ejecución paralela de steps
← Volver a Spring Boot 4 Complete Guide