← 返回首页 ❓ 面试题库
📑 本篇章节导航 (共11章,点击直达)
一、Java 17-21核心新特性二、Virtual Threads深度实战三、Spring Boot 3.x核心新特性四、GraalVM Native Image五、Spring Security 6.x六、现代Java开发实践七、Spring Boot 3.x测试八、性能与监控九、实战场景题十、面试高频综合题面试速记口诀

Q93 Spring Boot 3.x与Java新特性深度实战

20K Java+AI 岗位高频考点 — Spring Boot 3.x是当前企业主流版本,配合Java 17/21新特性是面试重点。覆盖GraalVM Native Image、Virtual Threads、Records、Sealed Classes、Pattern Matching、Spring Boot 3.x新特性、Micrometer Observability等。

一、Java 17-21核心新特性

1. Java 17 LTS有哪些重要新特性?


// Sealed Class
public sealed interface Shape permits Circle, Rectangle, Triangle {}
public record Circle(double radius) implements Shape {}
public record Rectangle(double width, double height) implements Shape {}
public record Triangle(double a, double b, double c) implements Shape {}

// Pattern Matching for instanceof
if (obj instanceof String s && s.length() > 5) {
    System.out.println(s.toUpperCase());  // 直接使用s
}

2. Java 21 LTS有哪些重要新特性?


// Virtual Threads
try (var executor = Executors.newVirtualThreadPerTaskExecutor()) {
    IntStream.range(0, 100_000).forEach(i -> {
        executor.submit(() -> {
            Thread.sleep(Duration.ofSeconds(1));
            return i;
        });
    });
}

// Sequenced Collections
SequencedCollection<String> seq = new ArrayList<>(List.of("a", "b", "c"));
seq.getFirst();  // "a"
seq.getLast();   // "c"
seq.reversed();  // [c, b, a]

3. Record类的原理和使用场景?

Record是Java 16正式引入的不可变数据载体类,编译器自动生成:


public record UserDTO(Long id, String name, String email) {
    // 自定义紧凑构造器(验证)
    public UserDTO {
        if (name == null || name.isBlank()) {
            throw new IllegalArgumentException("name不能为空");
        }
    }
}

// 使用
UserDTO user = new UserDTO(1L, "张三", "zhangsan@qq.com");
user.name();  // "张三"(注意:不是getName())

场景:DTO、VO、Event对象、配置类、Map的Entry替代。

4. Sealed Classes(密封类)的应用场景?

限制继承层次,实现代数数据类型(ADT):


// 支付方式 - 密封接口
public sealed interface PaymentMethod permits WechatPay, Alipay, BankCard {}
public record WechatPay(String openId) implements PaymentMethod {}
public record Alipay(String userId) implements PaymentMethod {}
public record BankCard(String cardNo, String bank) implements PaymentMethod {}

// Pattern Matching + Sealed = 穷举检查
public String pay(PaymentMethod method) {
    return switch (method) {
        case WechatPay w -> "微信支付: " + w.openId();
        case Alipay a -> "支付宝: " + a.userId();
        case BankCard b -> "银行卡: " + b.cardNo();
        // 不需要default,编译器知道所有子类
    };
}

5. Pattern Matching for switch的用法?


// 类型匹配
static String format(Object obj) {
    return switch (obj) {
        case Integer i -> String.format("int %d", i);
        case Long l -> String.format("long %d", l);
        case Double d -> String.format("double %f", d);
        case String s -> String.format("String %s", s);
        case int[] arr -> "int数组, 长度=" + arr.length;
        case null -> "null";
        default -> obj.toString();
    };
}

// 带条件守卫(Guard Pattern)
static String categorize(Object obj) {
    return switch (obj) {
        case String s when s.length() > 10 -> "长字符串";
        case String s -> "短字符串";
        case Integer i when i > 0 -> "正整数";
        case Integer i -> "非正整数";
        default -> "其他";
    };
}

6. Text Blocks(文本块)的用法?


// 多行SQL
String sql = """
    SELECT u.id, u.name, o.total
    FROM users u
    JOIN orders o ON u.id = o.user_id
    WHERE o.created_at > '%s'
    """.formatted(LocalDate.now().minusDays(7));

// JSON模板
String json = """
    {
        "name": "%s",
        "age": %d
    }
    """.formatted(name, age);

// 正则表达式(不需要双重转义)
String regex = """
    (?<year>\\d{4})-(?<month>\\d{2})-(?<day>\\d{2})
    """;

二、Virtual Threads深度实战

7. Virtual Threads的核心原理?

Virtual Thread是JVM管理的轻量级线程,M:N调度:

创建方式:


// 方式一:直接创建
Thread.startVirtualThread(() -> doSomething());

// 方式二:工厂
Thread vt = Thread.ofVirtual().name("my-vt").start(() -> doSomething());

// 方式三:ExecutorService
try (var executor = Executors.newVirtualThreadPerTaskExecutor()) {
    executor.submit(() -> doSomething());
}

// 方式四:Spring Boot 3.2+
// application.yml: spring.threads.virtual.enabled: true

8. Virtual Thread的Pinning问题?

Pinning:Virtual Thread在执行synchronized块或native方法时无法从Carrier Thread上卸载,会"钉住"Carrier Thread。

影响:大量Pinning会导致Carrier Thread耗尽,吞吐量下降。

解决方案(JDK 21+):


// Before: synchronized会Pinning
synchronized (lock) {
    blockingIO();
}

// After: ReentrantLock不会Pinning
lock.lock();
try {
    blockingIO();
} finally {
    lock.unlock();
}

9. Virtual Thread vs WebFlux vs 协程?

维度Virtual ThreadWebFluxKotlin协程
编程模型同步阻塞(直觉)响应式(回调)挂起函数
学习成本极低高中
生态兼容完全兼容响应式库Kotlin生态
调试难度低(正常堆栈)高(回调地狱)中
适用场景通用、IO密集高并发流式Kotlin项目

选型建议:新项目优先Virtual Thread,旧WebFlux项目不急于迁移。

10. Spring Boot 3.2+如何启用Virtual Threads?


# application.yml
spring:
  threads:
    virtual:
      enabled: true  # Tomcat请求处理、@Async、调度器都使用虚拟线程

影响范围:

注意:ThreadLocal在Virtual Thread中慎用——百万级Virtual Thread = 百万份ThreadLocal副本。


三、Spring Boot 3.x核心新特性

11. Spring Boot 3.0的重要变更?

迁移关键点:


<!-- javax → jakarta -->
<!-- Before -->
<dependency>
    <groupId>javax.servlet</groupId>
    <artifactId>javax.servlet-api</artifactId>
</dependency>
<!-- After -->
<dependency>
    <groupId>jakarta.servlet</groupId>
    <artifactId>jakarta.servlet-api</artifactId>
</dependency>

12. Spring Boot 3.x的Observability(可观测性)?

Spring Boot 3.x集成了Micrometer Observation API,统一了Tracing和Metrics:


// 自动配置(无需额外代码)
management:
  tracing:
    sampling:
      probability: 1.0  # 采样率
  endpoints:
    web:
      exposure:
        include: health,info,prometheus

// 依赖
<dependency>
    <groupId>io.micrometer</groupId>
    <artifactId>micrometer-observation</artifactId>
</dependency>
<dependency>
    <groupId>io.micrometer</groupId>
    <artifactId>micrometer-tracing-bridge-brave</artifactId>
</dependency>
<dependency>
    <groupId>io.zipkin.reporter2</groupId>
    <artifactId>zipkin-reporter-brave</artifactId>
</dependency>

支持的Tracing后端:Zipkin、Jaeger、SkyWalking(通过Micrometer Bridge)。

13. Spring Boot 3.x的Properties改进?

Constructor Binding简化:


// Before: @ConstructorBinding注解
// After: 当只有一个构造器时自动绑定
@ConfigurationProperties(prefix = "app")
public record AppProperties(
    String name,
    int port,
    List<String> servers,
    Duration timeout
) {}

新的属性文件格式:


# 支持List/Map更优雅的写法
app:
  name: my-app
  port: 8080
  servers:
    - server1:8080
    - server2:8080
  timeout: 30s  # Duration类型自动解析

14. Spring Boot 3.x的Docker镜像构建?

Buildpacks(推荐):


# 一行命令构建Docker镜像
./mvnw spring-boot:build-image
# 或
./gradlew bootBuildImage

分层镜像(Layered Jar):


# Dockerfile - 分层提取
FROM eclipse-temurin:21-jre as builder
WORKDIR /app
COPY target/*.jar app.jar
RUN java -Djarmode=layertools -jar app.jar extract

FROM eclipse-temurin:21-jre
WORKDIR /app
COPY --from=builder /app/dependencies/ ./
COPY --from=builder /app/spring-boot-loader/ ./
COPY --from=builder /app/snapshot-dependencies/ ./
COPY --from=builder /app/application/ ./
ENTRYPOINT ["java", "org.springframework.boot.loader.launch.JarLauncher"]

15. Spring Boot 3.2-3.4的重要新特性?

3.2:

3.3:

3.4:


// RestClient(3.2+)
RestClient restClient = RestClient.create();
String result = restClient.get()
    .uri("https://api.example.com/users/{id}", 1)
    .header("Authorization", "Bearer xxx")
    .retrieve()
    .body(String.class);

// JdbcClient(3.2+)
JdbcClient jdbcClient = JdbcClient.create(dataSource);
List<User> users = jdbcClient.sql("SELECT * FROM users WHERE age > :age")
    .param("age", 18)
    .query(User.class)
    .list();

四、GraalVM Native Image

16. GraalVM Native Image的原理?

Native Image通过AOT(Ahead-of-Time)编译将Java应用编译为本地可执行文件:

1. 分析阶段:静态分析应用的所有可达代码

2. 编译阶段:将字节码编译为机器码

3. 链接阶段:打包为可执行文件

优势:启动时间 < 100ms(vs JVM的数秒)、内存占用低(1/5-1/10)、无JVM预热。

限制:反射、动态代理、JNI需要显式配置;不支持运行时字节码生成。

17. Spring Boot 3.x的Native Image支持?


# 方式一:Buildpacks
./mvnw -Pnative native:compile
# 生成 target/my-app

# 方式二:GraalVM直接编译
native-image -jar target/my-app.jar

# 方式三:Docker构建
./mvnw -Pnative spring-boot:build-image
docker run --rm my-app:latest

Spring AOT处理:

18. Native Image的反射配置怎么做?


// 方式一:RuntimeHints(推荐)
@Component
public class MyRuntimeHints implements RuntimeHintsRegistrar {
    @Override
    public void registerHints(RuntimeHints hints, ClassLoader classLoader) {
        hints.reflection()
            .registerType(MyDto.class, MemberCategory.INVOKE_PUBLIC_METHODS)
            .registerConstructor(MyDto.class, MemberCategory.INVOKE_PUBLIC_CONSTRUCTORS);
        hints.resources()
            .registerPattern("templates/*")
            .registerPattern("static/*");
    }
}

// 方式二:@RegisterReflectionForBinding
@RegisterReflectionForBinding({UserDTO.class, OrderDTO.class})
@RestController
public class MyController { ... }

// 方式三:反射配置文件(reachability-metadata.json)

19. Native Image的适用场景和限制?

适用场景:

不适用:


五、Spring Security 6.x

20. Spring Security 6.x的重要变更?


// Before (Security 5)
@Configuration
public class SecurityConfig extends WebSecurityConfigurerAdapter {
    @Override
    protected void configure(HttpSecurity http) throws Exception {
        http.authorizeRequests()
            .antMatchers("/public/**").permitAll()
            .anyRequest().authenticated();
    }
}

// After (Security 6)
@Configuration
@EnableWebSecurity
public class SecurityConfig {
    @Bean
    SecurityFilterChain filterChain(HttpSecurity http) throws Exception {
        return http
            .authorizeHttpRequests(auth -> auth
                .requestMatchers("/public/**").permitAll()
                .requestMatchers("/admin/**").hasRole("ADMIN")
                .anyRequest().authenticated()
            )
            .oauth2ResourceServer(oauth2 -> oauth2.jwt(Customizer.withDefaults()))
            .sessionManagement(session -> session
                .sessionCreationPolicy(SessionCreationPolicy.STATELESS))
            .build();
    }
}

21. Spring Security 6的方法级安全怎么配置?


@Configuration
@EnableMethodSecurity  // 替代 @EnableGlobalMethodSecurity
public class MethodSecurityConfig { }

// 使用注解
@Service
public class OrderService {
    @PreAuthorize("hasRole('ADMIN') or #userId == authentication.principal.id")
    public Order getOrder(Long userId, Long orderId) { ... }

    @PostAuthorize("returnObject.userId == authentication.principal.id")
    public Order getMyOrder(Long orderId) { ... }

    @PreAuthorize("@orderSecurity.canModify(#orderId)")
    public void updateOrder(Long orderId, OrderDTO dto) { ... }
}

六、现代Java开发实践

22. Java 17+的异常处理改进?


// 多异常catch(已优化)
try {
    // ...
} catch (SQLException | IOException e) {
    log.error("数据库或IO异常", e);
}

// Try-with-resources + var
try (var conn = dataSource.getConnection();
     var stmt = conn.prepareStatement(sql);
     var rs = stmt.executeQuery()) {
    while (rs.next()) {
        // ...
    }
}

23. CompletableFuture的进阶用法?


// 组合多个异步任务
CompletableFuture<User> userFuture = CompletableFuture.supplyAsync(() -> userService.getById(userId));
CompletableFuture<List<Order>> ordersFuture = CompletableFuture.supplyAsync(() -> orderService.getByUserId(userId));
CompletableFuture<Credit> creditFuture = CompletableFuture.supplyAsync(() -> creditService.getByUserId(userId));

// 组合结果
CompletableFuture<UserProfile> profileFuture = userFuture
    .thenCombine(ordersFuture, (user, orders) -> new UserProfile(user, orders))
    .thenCombine(creditFuture, (profile, credit) -> {
        profile.setCredit(credit);
        return profile;
    });

// 超时处理
UserProfile profile = profileFuture
    .orTimeout(3, TimeUnit.SECONDS)
    .exceptionally(ex -> UserProfile.empty())
    .join();

24. Java新特性在业务代码中的实际应用?


// Records作为DTO
public record CreateOrderRequest(
    Long userId,
    List<OrderItem> items,
    @Nullable String couponCode
) {}

// Sealed Interface处理结果
public sealed interface OrderResult {
    record Success(Long orderId, BigDecimal total) implements OrderResult {}
    record Failed(String reason) implements OrderResult {}
    record Pending(Long orderId) implements OrderResult {}
}

// Pattern Matching处理
public String handleResult(OrderResult result) {
    return switch (result) {
        case Success s -> "订单创建成功: " + s.orderId();
        case Failed f -> "失败: " + f.reason();
        case Pending p -> "等待支付: " + p.orderId();
    };
}

// Text Block写SQL
String sql = """
    SELECT o.*, u.name
    FROM orders o
    JOIN users u ON o.user_id = u.id
    WHERE o.status = :status
      AND o.created_at > :since
    ORDER BY o.created_at DESC
    LIMIT :limit
    """;

25. Stream API的Java 17+增强?


// toList() 简化(Java 16+)
List<String> names = users.stream()
    .map(User::getName)
    .toList();  // 替代 .collect(Collectors.toList())

// Stream Gatherers(Java 24预览)
// 自定义中间操作

26. Java的时间API最佳实践?


// Duration/Period
Duration timeout = Duration.ofSeconds(30);
Period billingCycle = Period.ofMonths(1);

// Instant(时间戳)
Instant now = Instant.now();
Instant expireAt = now.plus(Duration.ofDays(7));

// 格式化
DateTimeFormatter fmt = DateTimeFormatter.ofPattern("yyyy-MM-dd HH:mm:ss");
LocalDateTime.parse("2024-01-01 12:00:00", fmt);

// 时区处理
ZonedDateTime tokyo = ZonedDateTime.now(ZoneId.of("Asia/Tokyo"));
ZonedDateTime beijing = tokyo.withZoneSameInstant(ZoneId.of("Asia/Shanghai"));

七、Spring Boot 3.x测试

27. Spring Boot 3.x的测试改进?


// 测试切片更精确
@WebMvcTest(UserController.class)
class UserControllerTest {
    @Autowired MockMvc mockMvc;
    @MockBean UserService userService;

    @Test
    void getUser() throws Exception {
        when(userService.getById(1L)).thenReturn(new UserDTO(1L, "张三"));
        mockMvc.perform(get("/api/users/1"))
            .andExpect(status().isOk())
            .andExpect(jsonPath("$.name").value("张三"));
    }
}

// Testcontainers集成
@SpringBootTest
@Testcontainers
class IntegrationTest {
    @Container
    static PostgreSQLContainer<?> postgres = new PostgreSQLContainer<>("postgres:16");

    @DynamicPropertySource
    static void configure(DynamicPropertyRegistry registry) {
        registry.add("spring.datasource.url", postgres::getJdbcUrl);
    }
}

28. 如何测试Virtual Thread应用?


@Test
void testVirtualThreadExecution() throws Exception {
    try (var executor = Executors.newVirtualThreadPerTaskExecutor()) {
        List<Future<String>> futures = IntStream.range(0, 1000)
            .mapToObj(i -> executor.submit(() -> {
                Thread.sleep(100);
                return Thread.currentThread().toString();
            }))
            .toList();

        long virtualCount = futures.stream()
            .map(Future::get)
            .filter(s -> s.contains("virtual"))
            .count();

        assertTrue(virtualCount > 900);  // 大部分应该是虚拟线程
    }
}

八、性能与监控

29. Spring Boot 3.x的Actuator增强?


management:
  endpoints:
    web:
      exposure:
        include: health,info,prometheus,metrics,env,beans
  endpoint:
    health:
      show-details: always
      probes:
        enabled: true  # K8s存活/就绪探针
  metrics:
    tags:
      application: ${spring.application.name}
    export:
      prometheus:
        enabled: true

K8s探针:


# K8s Deployment
livenessProbe:
  httpGet:
    path: /actuator/health/liveness
    port: 8080
readinessProbe:
  httpGet:
    path: /actuator/health/readiness
    port: 8080

30. Spring Boot 3.x的Structured Logging?


# application.yml
logging:
  format:
    console: structured  # 3.4+

输出格式(JSON):


{
  "timestamp": "2024-06-01T10:00:00.000Z",
  "level": "INFO",
  "thread": "http-nio-8080-exec-1",
  "logger": "com.example.UserService",
  "message": "User login",
  "context": {
    "userId": "12345",
    "traceId": "abc123"
  }
}

九、实战场景题

31. 如何从Spring Boot 2.x迁移到3.x?

迁移步骤:

1. 升级Java版本到17+

2. javax.* → jakarta.* 全局替换

3. Spring Security配置改为Lambda DSL

4. 废弃API替换(antMatchers→requestMatchers等)

5. 第三方库版本升级(确保兼容Jakarta)

6. 测试全量回归

工具辅助:


# OpenRewrite自动迁移
./mvnw rewrite:run \
  -Drewrite.activeRecipes=org.openrewrite.java.spring.boot3.UpgradeSpringBoot_3_3

32. 如何设计一个Spring Boot 3.x的微服务架构?


API Gateway (Spring Cloud Gateway)
    ↓
Service A (Spring Boot 3.x + Virtual Threads)
    ├── Spring Security 6 (JWT + OAuth2)
    ├── Spring Data JPA (Hibernate 6)
    ├── Spring Kafka
    └── Observability (Micrometer + Zipkin)

关键选型:

33. 如何优化Spring Boot应用的启动速度?

方案一:Lazy Initialization


spring:
  main:
    lazy-initialization: true  # 首次访问时才初始化Bean

方案二:GraalVM Native Image

启动时间从3秒降到50ms。

方案三:CDS(Class Data Sharing)


# Java 17+ + Spring Boot 3.3+
java -jar -XX:SharedArchiveFile=app.jsa my-app.jar

方案四:Spring Boot Layered + Docker缓存

利用Docker层缓存不变层。

34. 如何实现Spring Boot应用的优雅停机?


server:
  shutdown: graceful  # 优雅停机
spring:
  lifecycle:
    timeout-per-shutdown-phase: 30s  # 最大等待30秒

K8s配合:


# PreStop Hook等待流量排空
lifecycle:
  preStop:
    exec:
      command: ["sh", "-c", "sleep 10"]
terminationGracePeriodSeconds: 40  # > timeout-per-shutdown-phase

35. Spring Boot 3.x如何集成AI能力?


// Spring AI 2.0集成
@Configuration
public class AiConfig {
    @Bean
    ChatClient chatClient(ChatClient.Builder builder) {
        return builder
            .defaultSystem("你是Java技术专家助手")
            .defaultAdvisors(new MessageChatMemoryAdvisor(new InMemoryChatMemory()))
            .build();
    }
}

@RestController
@RequestMapping("/api/ai")
public class AiController {
    @Autowired ChatClient chatClient;

    @PostMapping("/chat")
    public Flux<String> chat(@RequestBody String message) {
        return chatClient.prompt()
            .user(message)
            .stream()
            .content();  // 流式输出
    }
}

十、面试高频综合题

36. Java 17/21迁移中最大的坑是什么?

1. javax→jakarta:第三方库不兼容(如老版MyBatis、Hibernate Validator)

2. 反射限制:某些框架的反射在Native Image中失效

3. Spring Security重构:配置方式完全变了

4. 依赖冲突:传递依赖可能还停留在javax

5. 字节码增强不兼容:Lombok、MapStruct等需要升级

37. Virtual Threads的生产注意事项?

1. 避免synchronized:用ReentrantLock替代

2. 慎用ThreadLocal:百万线程=百万副本

3. 监控Carrier Thread:jdk.VirtualThreadPinned事件

4. 连接池调整:Virtual Thread下连接池可能成为瓶颈

5. 不要pool Virtual Thread:Virtual Thread本身很轻,不需要池化

38. 如何选择Spring Boot的部署方式?

方式启动时间内存适用场景
JVM2-5s200-500MB通用、长期运行
Native Image50-100ms30-80MBServerless、CLI
CDS1-2s150-300MB传统部署优化
CRaC<100ms200-500MB快速恢复

39. Records vs Lombok @Value的选择?

Records优势:语言级支持、更简洁、Pattern Matching集成、Sealed Classes集成。

Lombok @Value优势:支持Builder、支持继承、更灵活的构造器。

建议:新项目用Records,需要Builder时用Lombok @Builder + Record。


// Record + Builder(Lombok)
@Builder
public record UserDTO(Long id, String name, String email) {}

// 使用
UserDTO user = UserDTO.builder().id(1L).name("张三").email("a@b.com").build();

40. Java 25/26有什么值得期待的特性?

41. Spring Boot 3.x的自动配置原理有什么变化?

Spring Boot 3.x使用AutoConfiguration.imports文件替代spring.factories:


# META-INF/spring/org.springframework.boot.autoconfigure.AutoConfiguration.imports
com.example.MyAutoConfiguration
com.example.AnotherAutoConfiguration

自动配置条件注解:


@AutoConfiguration
@ConditionalOnClass(DataSource.class)
@ConditionalOnMissingBean(DataSource.class)
@EnableConfigurationProperties(DataSourceProperties.class)
public class DataSourceAutoConfiguration {
    @Bean
    @ConditionalOnProperty("spring.datasource.url")
    public DataSource dataSource(DataSourceProperties props) {
        return DataSourceBuilder.create()
            .url(props.getUrl())
            .username(props.getUsername())
            .password(props.getPassword())
            .build();
    }
}

42. 如何设计Spring Boot 3.x的多环境配置?


# application.yml(公共配置)
spring:
  profiles:
    active: @profile.active@  # Maven占位符

---
# application-dev.yml
spring:
  datasource:
    url: jdbc:mysql://localhost:3306/dev
  threads:
    virtual:
      enabled: true

---
# application-prod.yml
spring:
  datasource:
    url: jdbc:mysql://${DB_HOST}:3306/${DB_NAME}
  threads:
    virtual:
      enabled: true

配置优先级(高→低):

1. 命令行参数 --server.port=8081

2. 环境变量 SERVER_PORT=8081

3. Profile特定配置

4. application.yml默认配置

43. Spring Boot 3.x的缓存抽象怎么用?


@Configuration
@EnableCaching
public class CacheConfig {
    @Bean
    RedisCacheManager cacheManager(RedisConnectionFactory factory) {
        RedisCacheConfiguration config = RedisCacheConfiguration.defaultCacheConfig()
            .entryTtl(Duration.ofMinutes(30))
            .serializeValuesWith(RedisSerializationContext.SerializationPair
                .fromSerializer(new GenericJackson2JsonRedisSerializer()));

        return RedisCacheManager.builder(factory)
            .cacheDefaults(config)
            .withInitialCacheConfigurations(Map.of(
                "users", config.entryTtl(Duration.ofHours(1)),
                "products", config.entryTtl(Duration.ofMinutes(10))
            ))
            .build();
    }
}

// 使用
@Service
public class UserService {
    @Cacheable(value = "users", key = "#id")
    public User getById(Long id) { return userRepository.findById(id); }

    @CachePut(value = "users", key = "#user.id")
    public User update(User user) { return userRepository.save(user); }

    @CacheEvict(value = "users", key = "#id")
    public void delete(Long id) { userRepository.deleteById(id); }
}

44. Spring Boot 3.x如何实现API版本控制?


// 方式一:URI路径版本
@RestController
@RequestMapping("/api/v1/users")
public class UserV1Controller { ... }

@RestController
@RequestMapping("/api/v2/users")
public class UserV2Controller { ... }

// 方式二:Header版本
@GetMapping(value = "/api/users", headers = "X-API-Version=1")
public UserV1 getUserV1() { ... }

// 方式三:Spring 6.2+ 内置API版本
@Configuration
public class ApiVersionConfig {
    @Bean
    ApiVersionConfigurer<RequestMappingHandlerMapping> apiVersionConfigurer() {
        return new ApiVersionConfigurer<>();
    }
}

45. Spring Boot 3.x的异常处理最佳实践?


@RestControllerAdvice
public class GlobalExceptionHandler {

    @ExceptionHandler(MethodArgumentNotValidException.class)
    @ResponseStatus(HttpStatus.BAD_REQUEST)
    public ProblemDetail handleValidation(MethodArgumentNotValidException ex) {
        ProblemDetail detail = ProblemDetail.forStatus(HttpStatus.BAD_REQUEST);
        detail.setTitle("参数验证失败");
        detail.setDetail(ex.getFieldErrors().stream()
            .map(e -> e.getField() + ": " + e.getDefaultMessage())
            .collect(Collectors.joining("; ")));
        return detail;
    }

    @ExceptionHandler(BusinessException.class)
    @ResponseStatus(HttpStatus.UNPROCESSABLE_ENTITY)
    public ProblemDetail handleBusiness(BusinessException ex) {
        return ProblemDetail.forStatusAndDetail(
            HttpStatus.UNPROCESSABLE_ENTITY, ex.getMessage());
    }
}

46. 如何实现Spring Boot应用的配置加密?


// 方式一:jasypt-spring-boot
// application.yml
// spring.datasource.password: ENC(加密后的密文)

// 方式二:Spring Cloud Config Server + Vault
// 方式三:环境变量注入(推荐生产环境)
spring:
  datasource:
    password: ${DB_PASSWORD}

47. Spring Boot 3.x的连接池最佳实践?


# HikariCP(默认)
spring:
  datasource:
    hikari:
      maximum-pool-size: 20        # CPU核数 * 2 + 磁盘数
      minimum-idle: 5
      connection-timeout: 30000    # 30秒获取连接超时
      idle-timeout: 600000         # 10分钟空闲超时
      max-lifetime: 1800000        # 30分钟最大生命周期
      connection-test-query: SELECT 1
      leak-detection-threshold: 60000  # 60秒连接泄漏检测

Virtual Thread下注意:maximum-pool-size可能需要增大,因为Virtual Thread数量远大于Platform Thread。

48. 如何实现Spring Boot应用的数据库多租户?


@Component
public class TenantInterceptor implements HandlerInterceptor {
    @Override
    public boolean preHandle(HttpServletRequest request, ...) {
        String tenant = request.getHeader("X-Tenant-ID");
        TenantContext.setTenant(tenant);
        return true;
    }

    @Override
    public void afterCompletion(...) {
        TenantContext.clear();
    }
}

// 基于Schema的多租户
public class SchemaMultiTenantConnectionProvider implements ConnectionProvider {
    @Override
    public Connection getConnection() {
        Connection conn = dataSource.getConnection();
        conn.setSchema("tenant_" + TenantContext.getTenant());
        return conn;
    }
}

49. Spring Boot 3.x的Scheduled Tasks增强?


@Configuration
@EnableScheduling
public class SchedulingConfig {
    @Bean
    TaskScheduler taskScheduler() {
        // 支持Virtual Thread
        return new SimpleAsyncTaskScheduler();  // Spring 6.1+
    }
}

@Component
public class ScheduledTasks {
    @Scheduled(fixedRate = 5000)           // 每5秒
    public void syncData() { ... }

    @Scheduled(cron = "0 0 2 * * ?")      // 每天凌晨2点
    public void dailyCleanup() { ... }

    @Scheduled(fixedDelay = 10000)         // 上次完成后10秒
    public void processQueue() { ... }
}

50. Spring Boot 3.x应用的健康检查设计?


// 自定义健康指标
@Component
public class RedisHealthIndicator extends AbstractHealthIndicator {
    @Autowired RedisTemplate<String, String> redisTemplate;

    @Override
    protected void doHealthCheck(Health.Builder builder) {
        try {
            String pong = redisTemplate.getConnectionFactory()
                .getConnection().ping();
            builder.up().withDetail("response", pong);
        } catch (Exception e) {
            builder.down().withException(e);
        }
    }
}

// 自定义就绪检查(K8s Readiness)
@Component
public class ReadinessHealthIndicator implements HealthIndicator {
    @Override
    public Health health() {
        // 检查所有外部依赖是否可用
        if (allDependenciesAvailable()) {
            return Health.up().build();
        }
        return Health.down().withDetail("reason", "依赖服务不可用").build();
    }
}

面试速记口诀

Java新特性三板斧:Records做数据载体、Sealed做类型约束、Pattern Matching做分支

>

Virtual Thread三注意:synchronized会Pinning、ThreadLocal会膨胀、不要池化虚拟线程

>

Boot 3.x三变革:Jakarta命名空间、Native Image支持、Observability统一

>

迁移三步走:Java 17 → javax→jakarta → Security配置重写