# REST Published articles for REST. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## Mintlify rebuilds automations around pre-built templates for common use cases DevFeed: [Mintlify rebuilds automations around pre-built templates for common use cases]() Original publisher: [Read original article]() Author: Patrick Foster Published: 2026-09-15T00:00:00Z Content type: article Language: en Sources: [Mintlify Blog]() Topics: [Automation](), [Documentation](), [changelog](), [Pull Request](), [Markdown](), [YAML]() Tags: [announcements](), [automation](), [changelog](), [docs](), [documentation](), [execution](), [markdown](), [prompt](), [quality](), [rest]() ### AI overview Mintlify rebuilt its automations around pre-built templates for common use cases, including syncing content with code changes, generating changelogs, and improving documentation from user feedback and support signals. Custom prompts remain available for specialized tasks. ### Source excerpt We redesigned automations for quicker setup with pre-built automations optimized for common use cases. Choose the right automations for your project and you're set. No context engineering required. ## APIs & Service Communication: The Essential Guide DevFeed: [APIs & Service Communication: The Essential Guide]() Original publisher: [Read original article]() Author: Nikki Siapno Published: 2026-09-08T13:03:41Z Content type: tutorial Language: en Sources: [Level Up Coding System Design Newsletter]() Topics: [API](), [Microservice](), [GraphQL](), [gRPC](), [Kafka](), [WebSocket]() Tags: [api](), [apis](), [graphql](), [http](), [kafka](), [rest]() ### AI overview A tutorial comparing communication patterns for distributed systems. It explains how request-response APIs, event streams, and bidirectional connections affect responsiveness, service coupling, failure propagation, operational complexity, reliability, and scalability, then introduces REST and GraphQL with their main strengths, tradeoffs, and use cases. ### Source excerpt REST, gRPC, Kafka, WebSockets, Pub/Sub, and more. How do they all fit together? ## Client-Side SDK Generation with VMware Cloud Foundation OpenAPI Specs DevFeed: [Client-Side SDK Generation with VMware Cloud Foundation OpenAPI Specs]() Original publisher: [Read original article]() Author: vmwareblogs Published: 2026-09-07T09:38:44Z Content type: tutorial Language: en Sources: [VMware Blogs]() Topics: [OpenAPI Specification](), [SDKs](), [.NET](), [C#](), [developer tooling](), [Java](), [Python](), [PowerShell]() Tags: [apis](), [cli](), [cloud](), [cloud-infrastructure](), [csharp](), [developer](), [developer-tooling](), [docker](), [home-page](), [java](), [net](), [openapi](), [powershell](), [programming](), [programming-language](), [python](), [rest](), [rest-api](), [sdk](), [specifications](), [vcf-9-0](), [vcf-9-1](), [vcf-sdk]() ### AI overview This guide explains how to generate a strongly typed .NET C# client SDK from VMware Cloud Foundation and vSphere OpenAPI specifications. It covers OpenAPI Generator, installation options, large specification handling, API-surface scoping, and the REST and JSON-RPC interfaces targeted by the example. ### Source excerpt Starting with VMware Cloud Foundation (VCF) 9.0, VMware officially publishes OpenAPI specifications for VCF APIs. This is a major milestone for developers, enabling you to consume VCF APIs using your programming language of choice. VMware provides first-class developer tooling such as VCF PowerCLI for PowerShell users and the VCF SDK offering Java and Python bindings. ... Continued The post Client-Side SDK Generation with VMware Cloud Foundation OpenAPI Specs appeared first on VMware Blogs. ## 【kube-apiserver】storage.Interface 与 etcd3：codec、prefix 与 CRUD 路径 DevFeed: [【kube-apiserver】storage.Interface 与 etcd3：codec、prefix 与 CRUD 路径]() Original publisher: [Read original article]() Author: Liao Tonglang Published: 2026-08-28T00:00:00Z Content type: tutorial Language: zh Sources: [土法炼钢 - 系统与基础设施]() Topics: [Kubernetes](), [API](), [Encryption](), [Raft]() Tags: [api](), [apiserver](), [codec](), [crud](), [distributed](), [encryption](), [encryption-at-rest](), [etcd3](), [guaranteed-update](), [kubernetes](), [optimistic-concurrency](), [raft](), [rest](), [storage](), [v1-30-3]() ### AI overview This tutorial explains how kube-apiserver's storage.Interface integrates with the etcd3 backend in Kubernetes v1.30.3. It covers key prefixes, codec serialization, value transformation and encryption-at-rest boundaries, optimistic concurrency through GuaranteedUpdate and transactions, and the mapping from etcd3 watch streams to apiserver events. ### Source excerpt 拆解 kube-apiserver 的 storage.Interface 契约与 etcd3 实现：codec 序列化、pathPrefix/resourcePrefix、value.Transformer 加密边界、GuaranteedUpdate 乐观并发，以及 Watch 到 etcd3 的完整路径。版本锚定 Kubernetes v1.30.3 / etcd v3.5.33。 ## 【kube-apiserver】Watch 路径（服务端）：长连接、410 Gone 与 timeout DevFeed: [【kube-apiserver】Watch 路径（服务端）：长连接、410 Gone 与 timeout]() Original publisher: [Read original article]() Author: Liao Tonglang Published: 2026-08-28T00:00:00Z Content type: article Language: zh Sources: [土法炼钢 - 系统与基础设施]() Topics: [Kubernetes](), [HTTP](), [kubectl]() Tags: [410-gone](), [apiserver](), [bookmark](), [cacher](), [distributed](), [etcd](), [etcd3](), [informer](), [kubernetes](), [resourceversion](), [rest](), [timeout](), [v1-30-3](), [watch]() ### AI overview This article explains the Kubernetes v1.30.3 apiserver Watch path, from the REST handler through cacher and etcd3 watchers. It distinguishes 410 Gone caused by cacher ring-buffer eviction from errors propagated from etcd compaction, and covers resourceVersion semantics, timeouts, bookmarks, connection lifecycle, and the boundary with client-go Informer. ### Source excerpt 钉 Kubernetes v1.30.3 服务端 Watch 路径：从 REST handler 到 cacher/etcd3 watcher 的建立过程、resourceVersion=0 与具体 RV 的语义差异、410 Gone 与 etcd ErrCompacted 的映射、bookmark 推送与连接生命周期，以及与 client-go Informer 的边界。 ## 【kube-apiserver】进程与请求路径：generic apiserver、HandlerChain 与 REST 路由 DevFeed: [【kube-apiserver】进程与请求路径：generic apiserver、HandlerChain 与 REST 路由]() Original publisher: [Read original article]() Author: Liao Tonglang Published: 2026-08-28T00:00:00Z Content type: tutorial Language: zh Sources: [土法炼钢 - 系统与基础设施]() Topics: [Kubernetes](), [API]() Tags: [admission](), [apf](), [apiserver](), [audit](), [authn](), [authz](), [distributed](), [generic-apiserver](), [gvr](), [handlerchain](), [kubernetes](), [request-path](), [rest](), [v1-30-3]() ### AI overview This tutorial explains the Kubernetes v1.30.3 kube-apiserver process model, the generic apiserver framework, HandlerChain ordering, GVR routing, and the points where requests can be rejected before reaching storage. It also distinguishes failures caused by APF, authentication and authorization, admission, and storage. ### Source excerpt 拆解 kube-apiserver 进程模型与 generic apiserver 框架；钉 HandlerChain 各插槽顺序与失败落点；说明 GVR 路由机制与请求在到达 storage 前可能被拦截的位置。版本锚定 Kubernetes v1.30.3。 ## How we shipped a production API out of one Slack thread DevFeed: [How we shipped a production API out of one Slack thread]() Original publisher: [Read original article]() Author: WorkOS Published: 2026-08-27T14:09:14Z Content type: article Language: en Sources: [WorkOS Blog]() Topics: [API](), [Slack](), [CRUD]() Tags: [agents](), [api](), [merge](), [production](), [pull-requests](), [rest](), [security](), [slack]() ### AI overview WorkOS describes how its IT Contact API was shipped from a single Slack thread. Humans made product and design decisions and gated the merge, while agents handled tickets, pull requests, review responses, and merges. The discussion shaped the API from an initial RPC proposal toward REST and resolved security, deletion, and duplicate-creation questions. ### Source excerpt The WorkOS IT Contact API went live on August 18 out of a single Slack thread. Humans made the decisions and gated the merge; agents did everything else. ## How Fuzz Testing for APIs Is Evolving DevFeed: [How Fuzz Testing for APIs Is Evolving]() Original publisher: [Read original article]() Author: J Simpson Published: 2026-08-21T07:00:00Z Content type: article Language: en Sources: [Nordic APIs]() Topics: [Testing](), [API](), [Large Language Model](), [Security](), [HTTP]() Tags: [api-security](), [api-testing](), [api-vulnerabilities](), [apis](), [artificial-intelligence](), [blog](), [http](), [llm](), [llms](), [open-source](), [openapi-specification](), [rest](), [security](), [testing](), [validation]() ### AI overview The article examines how API fuzz testing is evolving through the use of LLMs, OpenAPI Overlay, and automated security testing. It highlights the importance of generating suitable test data so HTTP requests can pass input validation and reach deeper security checks. ### Source excerpt Ahead of Nordic APIs Summit 2026, we check in with speaker Andrea Arcuri on how fuzz testing for APIs is evolving. "You cannot really check security properties if all your HTTP calls fail with a 4xx because your techniques can't generate the right test data to pass the first layer of input validation," answers Andrea ... ## \[CVE\] \[URGENT\] Squid v19.2.6 and Tentacle v20.2.4 released DevFeed: [\[CVE\] \[URGENT\] Squid v19.2.6 and Tentacle v20.2.4 released]() Original publisher: [Read original article]() Author: Patrick Donnelly Published: 2026-08-19T00:00:00Z Content type: release Language: en Sources: [Ceph Blog]() Topics: [releases](), [Authentication](), [Linux](), [client](), [monitor]() Tags: [authentication](), [blog-post](), [cve](), [cves](), [en-article](), [en-blog-post](), [errors](), [linux](), [process](), [release](), [releases](), [rest](), [rgw](), [squid](), [tentacle](), [upgrade]() ### AI overview The Ceph project released Tentacle 20.2.4 and Squid 19.2.6 as hotfixes addressing four CVEs. The article urgently recommends upgrading and explains changes to CephX key types, daemon-key rotation, authentication controls, recovery procedures, and multisite RGW request signing. ### Source excerpt The Ceph project has released Tentacle 20.2.4 and Squid 19.2.6 hotfixes for four CVEs across several components. This is the sixth backport release in the Squid series. This is the fourth backport release in the Tentacle series. We strongly recommend that all Ceph operators upgrade to one of these releases as soon as possible. Release Date ¶ August 19, 2026 Critical Upgrade Steps ¶ The fix for CVE-2025-30156 introduces a new CephX key type, aes256k. This is the first time Ceph has introduced a new key type for CephX credentials. Therefore, a new procedure exists for upgrading and rotating Ceph daemon keys as part of this CVE. Before upgrading a Ceph cluster, the operator should familiarize themselves with the procedure to upgrade CephX keys. These steps are for package-based deployments of Ceph. In other sections, the document also includes new information about key rotation procedures, monitor authentication controls, and emergency recovery procedures. Deployments using cephadm will automate the process except for client keys. You may notice that Cephadm spends more time than normal on the upgrade after updating all daemon images. This is due to a new process rotating the OSD and MDS keys. Please be patient. There are plans to improve this in the future. Deployments using Rook will also automate rotation of some client keys with some exclusions. Look to the Rook project's announcement for more details. Client and kernel upgrades are recommended to support aes256k. Note that upstream Linux kernel client support began in kernel 7.0 and has been backported to CentOS Stream 9 and 10. Check with your distribution vendor for backported key support before rotating client keys used by the kernel. As part of upgrading a Ceph cluster, six new health warnings and errors will be generated. This is normal. As part of the process to upgrade/rotate entity keys, you will address the warnings and errors as you go. These are documented beginning here. The CephX documentation has bee ## Choosing an HTTP Status for AI Agent Authorization Through Transparent Proxies DevFeed: [Choosing an HTTP Status for AI Agent Authorization Through Transparent Proxies]() Original publisher: [Read original article]() Author: WorkOS Published: 2026-08-11T00:00:00Z Content type: tutorial Language: en Sources: [WorkOS Blog]() Topics: [API](), [AI Agent](), [HTTP](), [Authentication]() Tags: [agents](), [ai-agent](), [api](), [authentication](), [http](), [rest]() ### AI overview This article explains how a transparent proxy for AI agents should respond when a user has not connected a third-party API. It examines why 401 and 403 conflict with existing authentication and provider-response meanings, and discusses the proposed response shape and the x402 standard. ### Source excerpt Your agent calls a third-party API for a user who never connected it. What to send back, why 401 and 403 are both already taken, and what the x402 standard means for the answer. ## How to build an employee self-service portal in Webflow Cloud with Auth0, D1, and the CMS Data API DevFeed: [How to build an employee self-service portal in Webflow Cloud with Auth0, D1, and the CMS Data API]() Original publisher: [Read original article]() Author: Ismail Ajagbe Published: 2026-08-08T00:00:00Z Content type: tutorial Language: en Sources: [Webflow Blog]() Topics: [webflow](), [Auth0](), [Authentication](), [Cloudflare](), [Content Management System](), [Drizzle](), [Next.js](), [SQLite](), [web applications](), [API](), [hosting](), [JSON Web Tokens]() Tags: [authentication](), [cloudflare](), [code](), [drizzle](), [guides](), [hosting](), [how-to](), [next-js](), [rest](), [sqlite](), [webflow]() ### AI overview A guide to building an employee self-service portal in Webflow Cloud with Next.js, Auth0 authentication, Cloudflare D1 backed by Drizzle ORM, SQLite, and Webflow CMS announcements. ### Source excerpt Learn how to build an employee self-service portal in Webflow Cloud with Next.js, Auth0, SQLite, and Webflow CMSs. ## Vercel Container Registry repositories can now be made public DevFeed: [Vercel Container Registry repositories can now be made public]() Original publisher: [Read original article]() Author: Luke Phillips-Sheard Published: 2026-08-07T17:00:00Z Content type: release Language: en Sources: [Vercel News]() Topics: [Vercel](), [Command-line interface](), [REST API]() Tags: [api](), [cli](), [container-registry](), [documentation](), [images](), [registry](), [rest](), [rest-api](), [sandbox](), [update](), [vercel]() ### AI overview Vercel Container Registry repositories can now be made public. Public repositories allow any Vercel team to pull and use their images while retaining read-only access; repositories remain private by default. ### Source excerpt Vercel Container Registry now lets you make a repository public, so anyone with a Vercel account can pull and use its images. Sharing already granted read access to up to 100 teams, and making a repository public opens that access to every Vercel team rather than a named set. Public access is read-only, so anyone can pull and use the images but cannot push, delete, or otherwise change the repository. Repositories stay private by default. Make a repository public from the project dashboard under Images -> repository -> Settings -> Public Access, where confirming requires typing the repository name. You can also set visibility from the Vercel CLI: Public images work like shared images in Vercel Sandbox, which accepts a team-scoped image reference in Sandbox.create(): Update your repository visibility from the dashboard, the CLI, or the REST API, and see the Vercel Container Registry documentation to learn more. Read more ## REST API Authentication Methods Clearly Explained DevFeed: [REST API Authentication Methods Clearly Explained]() Original publisher: [Read original article]() Author: Nikki Siapno Published: 2026-08-05T18:25:08Z Content type: tutorial Language: en Sources: [Level Up Coding System Design Newsletter]() Topics: [Authentication](), [REST API](), [API keys](), [Authorization](), [Security]() Tags: [api](), [api-keys](), [authentication](), [authorization](), [jwt](), [private-key](), [rest](), [security]() ### AI overview This tutorial explains REST API authentication methods, including API keys, bearer tokens, JWTs, HMAC secrets, and mutual TLS. It distinguishes authentication from authorization and discusses operational concerns such as credential rotation, revocation, auditing, rate limiting, and responding to leaked credentials. ### Source excerpt 8 API authentication methods every developer should know. ## Incus/LXC: contenedores de sistema en Linux DevFeed: [Incus/LXC: contenedores de sistema en Linux]() Original publisher: [Read original article]() Author: Antonio Pérez Published: 2026-08-03T00:00:00Z Content type: tutorial Language: es Sources: [tengoping.com]() Topics: [Containers](), [Linux](), [Command-line interface](), [API](), [Proxmox](), [Docker](), [qemu](), [podman]() Tags: [api](), [cli](), [containers](), [docker](), [linux](), [lxc](), [proxmox](), [qemu](), [rest](), [ssh](), [storage]() ### AI overview This Spanish-language tutorial explains Incus as a Linux Containers system-container and lightweight hypervisor manager built on LXC. It describes its origins as a community fork of LXD, compares system containers with application containers and virtual machines, and outlines how Incus differs from Proxmox, Docker, and Podman. ### Source excerpt Incus gestiona contenedores de sistema con LXC: instalación, incus launch, storage pools y redes, y cuándo elegirlo frente a Docker o una VM. ## Learning Path: FastAPI: Python API Development With Light Speed DevFeed: [Learning Path: FastAPI: Python API Development With Light Speed]() Original publisher: [Read original article]() Author: Real Python Published: 2026-07-22T12:00:00Z Content type: tutorial Language: en Sources: [Real Python]() Topics: [FastAPI](), [Python](), [API](), [REST API](), [Pydantic](), [Web Development](), [CRUD]() Tags: [api](), [api-documentation](), [database](), [development](), [python](), [rest](), [tutorial](), [validation](), [web-development]() ### AI overview This learning path teaches Python developers how to build REST APIs and complete web applications with FastAPI. It covers automatic validation, serialization, interactive documentation, Pydantic data models, CRUD operations, Jinja2-rendered web pages, and a URL shortener project. ### Source excerpt Learn FastAPI from the ground up. Build REST APIs, serve web pages with Jinja2 templates, and create a complete URL shortener project in Python. ## Scale Faster with Managed Weaviate: Now in Public Preview on DigitalOcean DevFeed: [Scale Faster with Managed Weaviate: Now in Public Preview on DigitalOcean]() Original publisher: [Read original article]() Author: Waverly Swinton Published: 2026-07-09T19:08:52Z Content type: release Language: en Sources: [DigitalOcean]() Topics: [Digital Ocean](), [Cloud](), [Databases](), [Retrieval Augmented Generation (RAG)](), [autoscaling](), [Self-hosted](), [GraphQL](), [gRPC]() Tags: [autoscaling](), [configuration](), [database](), [databases](), [digitalocean](), [graphql](), [high-availability](), [hosting](), [infrastructure](), [preview](), [product-updates](), [real-time](), [rest](), [retrieval](), [run](), [security](), [storage](), [upgrades](), [workflows]() ### AI overview DigitalOcean has placed Managed Weaviate into public preview. The service provides fully managed Weaviate clusters with automated backups, security patching, version upgrades, high availability, and storage autoscaling, with pricing starting at $20 per month. ### Source excerpt Production Weaviate in minutes, managed by DigitalOcean. Starting at $20/month. Vector databases have become a core piece of the AI application stack. Whether you're building retrieval-augmented generation (RAG), semantic search, agentic workflows and memory, or similarity-based recommendations, you need a vector store that's reliable, fast, and doesn't require a dedicated ops engineer to keep running. Weaviate has become a critical part of that stack -- its open-source AI-native vector database powers semantic search, RAG, and agentic workflows for thousands of companies. Self-hosting Weaviate is doable but it comes at a cost. You're on the hook for backups, version upgrades, security patches, high availability configuration, and storage scaling. That's real time and real engineering capacity that isn't going toward your product. Managed alternatives from larger cloud vendors exist, but they often come with per-query fees, per-dimension surcharges, and pricing models that are difficult to predict as usage grows. Today, we're announcing that Managed Weaviate is now in public preview on DigitalOcean, offering an easy way for you to run Weaviate in production, at a price that makes sense from day one. The easiest way to run Weaviate in production Managed Weaviate on DigitalOcean handles the operational work so you don't have to. Provision a fully managed Weaviate cluster directly from the DigitalOcean control panel. From there, automated backups, security patching, version upgrades, high availability, and storage autoscaling are handled for you. Full Weaviate client compatibility via GraphQL, REST, and gRPC on port 443 means your existing code works without modification. This means you get Weaviate's full capabilities -- semantic and hybrid search, RAG pipelines, and support for agent-driven workflows -- without spending engineering time on the infrastructure beneath them. Predictable pricing, starting at $20/month We built Managed Weaviate with flat, predictable monthly ## Vercel Services: Run full stack on Vercel DevFeed: [Vercel Services: Run full stack on Vercel]() Original publisher: [Read original article]() Author: Joe Haddad Published: 2026-06-30T04:00:00Z Content type: release Language: en Sources: [Vercel News]() Topics: [Vercel](), [Deployment](), [FastAPI](), [Next.js](), [Developer experience](), [Routing (disambiguation)](), [JavaScript](), [Network Configuration](), [Python]() Tags: [cli](), [configuration](), [deployment](), [developer-experience](), [infrastructure](), [next-js](), [rest](), [routing](), [vercel]() ### AI overview Vercel Services is introduced in public beta as a way to run multiple frameworks in one Vercel Project. It supports coordinated deployments and previews, internal service communication, shared routing, service bindings, centralized logs, and local multi-service development for full-stack applications. ### Source excerpt To a user, an app with a Next.js frontend and a FastAPI backend feels like one product, and the same should be true for the engineers who build it. Instead, the two pieces are often deployed across different clouds with different development and deployment workflows. Today we're introducing Vercel Services in public beta, which lets you run multiple frameworks in one Vercel Project. This unlocks: Atomic deployments: Your frontend, backend, and other services stay in sync and deploy or roll back together Shared preview deployments: See how any change affects all your services Internal service communication: Services can talk to each other without routing through the public Internet Vercel handles the rest: routing, builds, deployments, and auto-scaling in production. The developer experience you already know from Vercel now covers your entire application. Compose applications with Vercel Services Declare your services under the services key in vercel.json keeping the routing configuration explicit: Services can be mounted to a shared routing table without the need for a reverse proxy or CORS. The services configuration is recognized at multiple levels of the Vercel platform: The Deployments panel shows a visualization of services graph The Logs UI allows filtering by individual service The vercel dev CLI automatically runs all services giving you a production-like environment locally Service bindings Services can talk to other services internally, without routing through the public Internet. Here's an example how the new bindings configuration key enables that: Now the JavaScript frontend code can talk to the Python service internally via the URL stored in the BACKEND_INTERNAL_URL environment variable: Service-to-service traffic stays on the Vercel network rather than egressing to the public internet. Many independent services can become one application connected by the same wiring, rather than separate deployments that you stitch together across hosts. Framework-def ## Introduction to Backend Development in 2026 DevFeed: [Introduction to Backend Development in 2026]() Original publisher: [Read original article]() Author: snehaa Published: 2026-06-09T07:28:26Z Content type: tutorial Language: en Sources: [Backend Archives | Talent500 blog]() Topics: [backend-development](), [Back end](), [Databases](), [Development](), [servers](), [App](), [Framework](), [JavaScript](), [Node.js](), [PHP](), [Python](), [Ruby]() Tags: [2026](), [apis](), [applications](), [authentication](), [backend](), [backend-development](), [backend-frameworks](), [databases](), [developer](), [developers](), [development](), [go](), [javascript](), [net](), [newsletters](), [node-js](), [php](), [programming](), [python](), [rest](), [ruby](), [server-side-development](), [technology](), [web-development]() ### AI overview An introductory guide to backend development, explaining how server-side code powers websites and applications through application logic, APIs, databases, authentication, and integrations with other services. ### Source excerpt Backend development sits behind every modern website and application, powering the logic, data, and infrastructure that users never see but [...] The post Introduction to Backend Development in 2026 appeared first on Talent500 blog. ## Trigger Deployments on Git Tags DevFeed: [Trigger Deployments on Git Tags]() Original publisher: [Read original article]() Author: Michael Fallihee Published: 2026-06-05T00:00:00Z Content type: release Language: en Sources: [Pulumi]() Topics: [Deployment](), [Git](), [releases](), [ci](), [REST API](), [GitHub]() Tags: [announcements](), [azure](), [bitbucket](), [deployment](), [devops](), [features](), [git](), [git-tags](), [github](), [gitlab](), [product](), [pulumi-cloud](), [rest](), [rest-api](), [version-control]() ### AI overview Pulumi Deployments can now trigger stack deployments when matching Git tags are pushed. Teams can enable tag-based triggers, configure glob filters, and use the tag name in deployment commands or Pulumi programs. The feature works with GitHub, GitLab, Bitbucket, Azure DevOps, and Custom VCS integrations. ### Source excerpt A git tag is how many teams mark a release as ready. Pulumi Deployments can now act on that signal directly: configure a tag-based trigger, push a version tag like v1.2.0, and Pulumi automatically runs pulumi up for your stack. No extra pipeline glue, no manual click -- your release tag is the deployment. Why tags? Push to Deploy has long let you preview changes on a pull request and update a stack when commits merge to a branch. That branch-based model is a great fit for continuous delivery to shared development and QA environments, where every merge should flow straight through. But promotion to production is often deliberate, not continuous. You merge throughout the day, then decide -- separately -- that a particular commit is the release. The conventional way to record that decision is a git tag: v1.2.0, 2026.06.0, release-2026-06-04. Tagging is already part of most teams' release rituals. Tag-based triggers connect that ritual to your infrastructure. Instead of wiring up a separate CI job to call the Pulumi Deployments REST API on a tag event, you configure the trigger once in your stack's deployment settings and let Pulumi handle the rest. How it works Tag triggers are controlled by two settings on your stack's deployment configuration: Run updates for pushed tags -- a toggle that enables running pulumi up when a matching tag is pushed. Tag filters -- a list of glob patterns that decide which tag names qualify. Tag filters use the same model as the path filters you may already know, except the patterns match against the tag name rather than changed file paths. A few examples: v* -- deploy on any tag beginning with v, such as v1.0.0 and v2.3.1. v* plus !*-rc* -- deploy on release tags but skip release candidates like v1.2.0-rc1. 2026.* -- deploy on calendar-versioned releases such as 2026.06.0. Filters prefixed with ! are exclusions, and an exclusion always wins over an include. With no filters configured and the toggle on, every tag push deploys. Deleting a tag never ## How to Design APIs DevFeed: [How to Design APIs]() Original publisher: [Read original article]() Author: Saurabh Dashora Published: 2026-06-02T06:41:25Z Content type: tutorial Language: en Sources: [System Design Codex]() Topics: [API](), [Architecture & Design](), [interface](), [CRUD](), [GraphQL](), [gRPC](), [HTTP](), [JSON](), [XML]() Tags: [api](), [apis](), [crud](), [graphql](), [how-to](), [http](), [interface](), [json](), [rest](), [rpc]() ### AI overview A tutorial on API design covering interface contracts, resource and endpoint naming, request and response formats, API paradigms, and modeling relationships between entities. ### Source excerpt Key considerations to keep in mind ## OpenAPI, ORM, SVG and Lottie DevFeed: [OpenAPI, ORM, SVG and Lottie]() Original publisher: [Read original article]() Author: Shai Almog Published: 2026-06-01T00:00:00Z Content type: release Language: en Sources: [CodeName One]() Topics: [OpenAPI Specification](), [Code generation](), [SQLite](), [Object-relational mapping](), [JSON](), [XML](), [SVG](), [ASP.NET Core](), [FastAPI](), [Nest]() Tags: [build](), [fastapi](), [http](), [java](), [json](), [lottie](), [maven-plugin](), [net](), [openapi](), [orm](), [rest](), [spring](), [svg](), [xml]() ### AI overview A Codename One release follow-up describes a shared build-time code generation pipeline for OpenAPI client generation, a SQLite ORM, JSON and XML mappers, SVG and Lottie transcoders, and a declarative router. The pipeline emits typed Java from annotations or declarative source files without reflection. ### Source excerpt An OpenAPI client generator, a JPA-shaped SQLite ORM, JAXB-shaped JSON / XML mappers, build-time SVG / Lottie transcoders, and a declarative router with deep links. All on the same build-time codegen pipeline. ## REST vs GraphQL vs gRPC DevFeed: [REST vs GraphQL vs gRPC]() Original publisher: [Read original article]() Author: Nikki Siapno Published: 2026-05-28T10:32:52Z Content type: comparison Language: en Sources: [Level Up Coding System Design Newsletter]() Topics: [API](), [GraphQL](), [gRPC](), [HTTP](), [JSON]() Tags: [apis](), [graphql](), [http](), [json](), [rest]() ### AI overview A comparison of REST, GraphQL, and gRPC explains how each API style organizes communication and the tradeoffs each makes between flexibility, simplicity, efficiency, and control. ### Source excerpt The tradeoffs behind resource-driven, query-driven, and method-driven APIs. ## Building a REST API With Express Framework and MongoDB DevFeed: [Building a REST API With Express Framework and MongoDB]() Original publisher: [Read original article]() Author: Nic Raboy Published: 2026-05-08T12:00:00Z Content type: tutorial Language: en Sources: [Nic Raboy]() Topics: [Express](), [MongoDB](), [REST API](), [Tutorial](), [Node.js](), [JavaScript](), [Cross-origin resource sharing (CORS)](), [.env](), [JSON]() Tags: [api](), [code](), [cors](), [database](), [development](), [express](), [javascript](), [json](), [mongodb](), [node-js](), [nosql](), [rest](), [rest-api](), [tutorial]() ### AI overview A tutorial on building a REST API with Express Framework, MongoDB, and Node.js. It explains how JSON flows between clients, application logic, and MongoDB, then covers prerequisites, dependencies, CORS, environment configuration, and project structure. ### Source excerpt Almost every modern web application will need a REST API for the frontend to communicate with, and in almost every scenario, that frontend is going to expect to work with JSON data. As a result, the b... The post Building a REST API With Express Framework and MongoDB appeared first on Hevo. ## Realtime or Pipelines? How to choose the right tool DevFeed: [Realtime or Pipelines? How to choose the right tool]() Original publisher: [Read original article]() Author: Eduardo Gurgel; Riccardo Busetti Published: 2026-05-05T07:00:00Z Content type: article Language: en Sources: [Supabase Blog]() Topics: [Supabase](), [PostgreSQL](), [Replication](), [WebSocket]() Tags: [postgres](), [postgresql](), [real-time](), [replication](), [rest](), [ui]() ### AI overview This article compares Supabase Realtime and Supabase Pipelines, explaining that both use logical replication to read Postgres changes but serve different purposes. Realtime delivers live updates and communication features to application clients, while Pipelines moves data to analytical destinations. ### Source excerpt Both Realtime and Pipelines read changes from your Postgres database using logical replication. But they solve very different problems. Here is how to pick the right one. [Next page]()