REST-in-peace: New Declarative REST Client Library Generates Java API Clients from Interfaces

·3 views

A developer has released REST-in-peace (RIP), an open-source declarative REST client for Java designed to eliminate repetitive HTTP boilerplate. Developers describe an API as an annotated interface, and RIP produces a working implementation without manual HttpClient setup, JSON parsing, or status-code checks. The library generates code at compile time via an annotation processor, with a reflective proxy available as a fallback, and supports GraalVM native images without hand-written reflection configuration. Built-in resilience features such as retries with backoff, circuit breakers, bulkheads, idempotency keys, caching, and an interceptor chain are configured through annotations, with additional Spring Boot and reactive support.

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)

Study finds 60% of 175 AI tools changed their terms of service within 15 weeks

A developer re-read the terms of service for 175 AI tools on two separate occasions. The review found that about 60% of those terms had changed during a 15-week window. The findings were shared on Hacker News as a Show HN post linking to a guide on the subject. The source material provided does not detail the specific nature of the changes or the methodology used. The post drew limited attention, with three points and two comments at the time of posting.

0 comments Read more at Hacker News

ProgrammingDEV Community ·

ROC-AUC Can Mislead on Rare Events; Precision-Recall Metrics Reveal False Alarms

A tutorial explains that a classifier scoring a high ROC-AUC can still flood reviewers with irrelevant alerts when the target event is rare. Using a hypothetical wildfire social-media monitor, it notes that positives make up only about 1% of posts in the example. ROC-AUC measures how well positives are ranked above negatives, while precision and recall focus on the usefulness of flagged posts. The article argues that for imbalanced problems such as fraud, security, maintenance, and crisis monitoring, precision-recall evaluation can give a more meaningful picture of performance. It promises a reproducible Python demonstration comparing both metrics on the same classifier.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

Payments Firm Weighs Wiz-io Alternatives for Cloud Attack Surface Management

An organization in the payments industry is reassessing its choice of Wiz-io for cloud attack surface management, arguing that the tool was favored largely through personal engineering relationships rather than a rigorous evaluation. The piece contends that payment platforms need external attack surface coverage, real-time threat intelligence integration, and remediation that causes no downtime, since outages can quickly lead to financial losses and regulatory penalties. It proposes evaluating alternatives such as Palo Alto, Check Point, and CrowdStrike against criteria including continuous external asset mapping, correlation of threat data with internal vulnerabilities, and disruption-free patching methods. The author argues that inadequate tooling would leave misconfigured assets and exposed APIs open to attack and create maintenance windows that adversaries could exploit.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

Multi-Agent AI Systems Often Fail From Poor Coordination, Not Weak Agents

A DEV Community article argues that AI agents working together can perform worse than a single agent when they lack coordination, with duplicated searches, conflicting rewrites, and looping calls driving up costs. The author compares this to disorganized college group projects, where overlapping and contradictory edits undermine the final result. The proposed fix is not removing agents but adding simple handoff rules, such as requiring agents to claim tasks before starting and allowing only one agent to write each result. A minimal coordination contract in Python is offered as an example, using a dictionary to track task ownership without machine learning or vector databases. The author recommends rules that let agents disagree by creating new revision tasks rather than overwriting others' work.

0 comments Read more at DEV Community