SShortSingh.
TopTechnologyAI & MLStartupsProgrammingScienceBusinessFinanceCrypto & Web3World
Back to feed
Programming

How to Evolve REST and GraphQL APIs Without Breaking Existing Clients

0
·1 views

Every deployed API acts as a contract with its consumers, meaning changes to fields, endpoints, or response shapes can break clients that cannot be force-updated. REST APIs support four versioning strategies — URI path, query parameter, custom header, and content negotiation — each with distinct tradeoffs for public versus internal use. Not all changes require a version bump; adding new optional fields or endpoints is safe, while removing fields or changing types demands a new version. When breaking changes are unavoidable, both old and new versions should run simultaneously until usage data confirms the older version is no longer in use. GraphQL takes a different approach by rejecting versioning altogether, favoring schema evolution techniques to maintain backward compatibility as systems grow.

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)

Log in to join the discussion and vote.

Log in

Related stories

0
ProgrammingDEV Community ·

Developer builds AI event planning coordinator agent using TypeScript and HazelJS

A developer has published a tutorial on DEV Community detailing how to build an AI-powered Event Planning Coordinator Agent using TypeScript and the HazelJS framework. The system uses a multi-agent architecture where specialized agents handle distinct tasks such as venue search, guest coordination, logistics planning, and budget management. A RAG-powered pipeline with semantic search allows the VenueSearchAgent to retrieve relevant venues from a knowledge base based on criteria like capacity, type, and price. The GuestCoordinatorAgent manages guest lists, RSVP tracking, and communication scheduling, while a supervisor agent called EventManagerAgent orchestrates the overall workflow. The project aims to simplify the complexity of event planning by distributing responsibilities across focused, intelligent agents.

0 comments Read more at DEV Community
0
ProgrammingDEV Community ·

Developer Builds AI-Powered Home Maintenance Scheduler Using TypeScript and HazelJS

A developer has published a tutorial on DEV Community detailing how to build a Home Maintenance Scheduler Agent using TypeScript and the HazelJS framework. The system uses a multi-agent architecture, where six specialized agents handle tasks such as intake, scheduling, provider search, and reminder coordination, all overseen by a central orchestrator. A key feature is Retrieval-Augmented Generation (RAG), which allows the agent to semantically search a knowledge base of maintenance tasks categorized by frequency, difficulty, cost, and seasonal requirements. The goal is to help homeowners manage recurring maintenance needs — such as HVAC servicing and gutter cleaning — by automating scheduling and provider matching. The project demonstrates how AI agent frameworks can be applied to practical, everyday household management challenges.

0 comments Read more at DEV Community
0
ProgrammingDEV Community ·

Why Emails Pass SPF and DKIM But Still Fail DMARC: Alignment Explained

Emails can pass both SPF and DKIM authentication checks and still fail DMARC due to a concept called alignment, which requires that at least one authenticated domain matches the visible From address. SPF authenticates the Return-Path envelope sender, while DKIM authenticates the domain in its d= tag — neither of which necessarily matches the From header recipients see. DMARC, defined under RFC 7489, mandates that at least one of these authenticated domains aligns with the From domain before a message is considered compliant. Common failure scenarios include email service providers signing messages under their own domain rather than the sender's, and email forwarding that breaks SPF checks and corrupts DKIM signatures. The fix typically involves configuring a custom Return-Path or an aligned DKIM signature through the sending platform so that at least one mechanism aligns with the sender's actual domain.

0 comments Read more at DEV Community
0
ProgrammingDEV Community ·

EDR Tools Restrict Linux Distro Choice, Creating Tension Between Security and Dev Productivity

Endpoint Detection and Response (EDR) tools like Acronis support only a limited set of Linux distributions — such as Ubuntu, Debian, and RHEL-family — leaving developers who prefer other distros unable to comply with IT security policies. These tools rely on kernel-level hooks and system calls that vary across distributions, making broad compatibility technically demanding and resource-intensive for vendors. IT teams enforcing EDR compliance aim for a uniform security posture, but this standardization can reduce developer flexibility, productivity, and morale. Developers blocked from preferred distros often resort to workarounds like virtualization or dual-booting, which can introduce security blind spots and monitoring gaps. Experts note that vendor lock-in, slow EDR update cycles, and regulatory requirements like GDPR and HIPAA further complicate efforts to balance security compliance with developer autonomy.

0 comments Read more at DEV Community