A Spring Boot 4.1 CRUD API starter in Java 21 that stores one resource, items, in PostgreSQL through Spring JDBC's JdbcClient and a HikariCP pool, built with the Maven wrapper. It is for Java developers who want controller, service and repository layers with Bean Validation, JSON errors, a database health check, Swagger UI at /docs and MockMvc tests.
by Light CloudCRUD APIs

Plain SQL through JdbcClient keeps every query visible in ItemRepository, while application.properties reads the DB_* variables straight into spring.datasource.url and caps HikariCP at 5 connections. Spring Boot runs schema.sql before the app takes traffic, so an unreachable database shows up at deploy time; because the script only creates a missing table, changing the shape of items later means one ALTER TABLE, or adding Flyway once you need real migrations. JSON goes through Jackson 3, the version Spring Boot 4 uses, which is why JsonConfig imports from tools.jackson, and responses use snake_case fields such as created_at. On Light Cloud the Maven project is built and run as a container on PORT with the database variables set, and every push to your copy redeploys.
Yes. This MIT-licensed GitHub template runs Spring Boot 4.1 on Java 21 with springdoc-openapi, so Swagger UI is at /docs as soon as it starts. Deploying it on a paid Light Cloud plan creates the PostgreSQL database and sets the DB_* variables.
Copy the item/ package, rename the record, controller, service and repository, and add its CREATE TABLE IF NOT EXISTS to schema.sql. Component scanning picks up the new controller, so there is nothing to register.
Each query is a few lines of SQL, which keeps the starter small and shows exactly what runs against the database. You can add Spring Data JPA later; the controller only talks to ItemService.
No. ItemControllerTest loads only the web layer with @WebMvcTest and mocks ItemService. That also means the SQL and the health check are not tested, so add an integration test against a real PostgreSQL when you need that cover.
Yes. Build the jar with ./mvnw package and start java -jar target/items-1.0.0.jar with PORT and the DB_* variables set, on any host with Java 21 that can reach PostgreSQL.
Start a Java REST API with Spring Boot, input validation and problem JSON errors
Start a Java REST API on Quarkus with live reload and settings from the environment
Start a C# CRUD API on PostgreSQL with ASP.NET Core minimal APIs, Npgsql and OpenAPI