Spring Boot 4.1 brings native gRPC support with new starters and property changes

·1 views

Spring Boot 4.1, released on 10 June 2026, integrates gRPC support directly into the framework, replacing the previously separate spring-grpc project starters. The new official starters are published under the org.springframework.boot group, covering server, client, and their respective test variants. The spring-grpc 1.1.0 project continues to supply the core programming model — including @GrpcService and GrpcChannelFactory — but is pulled in transitively, so developers no longer declare it explicitly in their builds. Several configuration properties were renamed during the migration, with notable changes including channel address keys, keepalive formatting, and server port now being a separate property. Boot 4.1's Gradle plugin also auto-configures protobuf compilation, eliminating the verbose protobuf{} blocks that earlier tutorials required.

Read the full story at DEV Community

This is an AI-generated summary. ShortSingh links to the original source for the complete article.

Discussion (0)

CTO Scrapped Months of Work After Demo Revealed Wrong Product Direction

A startup CTO in the United Kingdom shared a key lesson learned while building an edtech SaaS platform for researchers. After months of development, a product demo revealed that the solution built did not effectively address the users' problem, despite a solid technical foundation. The team decided to discard the existing codebase and start over, acknowledging that sunk time should not justify continuing with a flawed approach. The experience led the CTO to rethink the development process, emphasising the need to validate assumptions and ask critical questions before writing any code. The core takeaway is that understanding a problem does not automatically mean the proposed solution is the right one.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

Three Lines of Python Fixed a YouTube Pipeline That Contradicted Itself

On July 7, 2026, a developer's automated YouTube content pipeline produced a self-contradictory output in a single CI run, simultaneously recommending and prohibiting the same video archetype. The conflict arose because the ranking system's fallback logic could select a poorly-performing archetype when data was sparse, while the knowledge bank had independently flagged that same archetype as off-limits. Neither component checked the other's output before writing to committed files, leaving the script-writer routine with conflicting instructions. The fix involved adding a module-level frozenset of banned archetypes, filtering it out during fallback selection, and inserting a hard final guard that prevents any prohibited archetype from ever appearing in the directive file. The developer used a frozenset deliberately for O(1) membership testing and to signal that the entries are an unordered set of values, with the final guard serving as an explicit, readable statement of the system's core invariant.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

Developer builds 120-line JSON ledger to coordinate Claude and Codex AI pipeline sessions

A developer running a multi-session AI content pipeline faced a coordination challenge after three months: Claude and Codex operate in separate, non-overlapping GitHub Actions workflows, making real-time handoffs impossible. To solve this, they built a 120-line Node.js script that uses a JSON file committed directly to the repository as a persistent coordination ledger. Each task record tracks status, timestamps, and polling intervals, allowing Claude to check whether Codex has completed a review before proceeding to publish. The pull-based design avoids the need for external services, authentication tokens, or network dependencies, since the repo already serves as shared state. Over 114 article review handoffs, the system has operated without a single missed coordination.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

New library brings file-system routing and convention-based config to Fastify

A developer has released @syora/fastify v1.1.0, an open-source library that introduces Convention over Configuration to the Fastify Node.js framework. Instead of manually declaring routes, hooks, and plugins, the library infers them automatically from the project's directory structure. During startup, it scans the project, generates optimized manifests and TypeScript type definitions, so no filesystem scanning occurs at request time. The approach is inspired by frameworks like Nuxt and Next.js, while aiming to preserve Fastify's core performance and API. The author has published the project on GitHub and is actively seeking community feedback on real-world viability and potential improvements.

0 comments Read more at DEV Community