Every post, summarised

Sep 17, 2026

• AWS

  How Equinix cut operational overhead with a shared services architecture on Amazon EKS

  Equinix replaced its self-managed Kubernetes environment on Amazon EKS to address operational sprawl caused by independently managed clusters and inconsistent infrastructure practices. The new shared services architecture assigns platform ownership to a cloud operations team while application teams focus on business services. It uses separate Workloads, Platform, and Network accounts: workloads run across two Availability Zones with ALB, Gateway API, Cilium, and Hubble, while shared data services, GitHub Runners, and platform services reside in the Platform account. The Network account provides cross-account and multi-Region connectivity through AWS Transit Gateway, Route 53 Resolver, and Direct Connect. Equinix reports 40% lower operational overhead, 4x higher deployment frequency, and adoption of a unified architecture across multiple business organizations.

• Databricks

  The Web Search Your Agent Inherited Isn't Good Enough

  An agent that keeps a company’s market view current must combine Databricks-hosted internal account records with external web signals such as funding rounds, leadership changes, product launches, and hiring surges. The initial implementation duplicates enrichment logic across Claude Code, Codex, and a direct model API, with inconsistent search results and no shared cost, governance, or audit trail. Omnigent consolidates the agent definition, model, tools, policies, limits, and model-call governance above those harnesses, while letting the engineer select a common search provider. Nimble’s Search API supplies live web data, while its Web Search Agents orchestrate multi-source retrieval and extraction, cross-check sources, return citations, and adapt to difficult sites and recurring retrieval paths. In Nimble’s testing, adding its search increased LLM benchmark accuracy from 46% to 71% and halved web search costs; the proposed Databricks setup then connects internal records and external context under one governance surface.

• Anthropic

  Introducing the Life Sciences Verification Program

  The Life Sciences Verification Program (LSVP) opens beta access to Mythos, Opus, and Sonnet models for verified life science teams whose work may be blocked by generally available Fable models. Applicants undergo review of research credentials, security standards, and ethical oversight, then may receive annual Standard Use grants or six-month, project-specific High-risk Use grants. Standard Use employs more permissive biology classifiers across research, clinical, manufacturing, and other workflows, while High-risk Use removes life-science safeguards for specifically vetted projects; cyber safeguards remain. The program shifts enforcement from request-level blocking to offline monitoring of behavioral patterns, requiring 30-day retention of flagged-activity data, compartmentalized from training and life sciences research teams. Access is available through API, Claude Science, Claude.ai, Claude Code, and Enterprise or Team plans, but not individual plans, third-party platforms, or BAA-enabled organizations during beta.

• Airbnb

  The guest journey, updated in real time: extending Airbnb’s sequence recommender with Chronon

  Airbnb’s guest sequence recommender previously refreshed Transformer-based embeddings in a daily batch, leaving activity from earlier the same day unavailable until the following run and creating up to nearly two days of staleness. To close this gap, Airbnb added Push Mode, which emits notifications when streaming feature values commit, and Near-real-time Model Transform, which invokes the deployed sequence encoder inside that streaming pipeline. Each page view or search is merged with the guest’s long-term and short-term sequence data, triggers inference, and writes a fresh embedding to the same low-latency store used by batch serving. The resulting system typically updates embeddings in under a minute, often within 10–30 seconds, improved offline NDCG by 1.67%, and increased uncancelled bookings by approximately one-third of a percent in online A/B tests.

• Notion

  A skills library for every agent

  The post introduces Notion’s skills library and Skills API, aimed at helping teams share organizational knowledge across AI agents and workflows. The library is designed for nontechnical and technical users, with collaborative editing, database organization, supporting files, permissions, suggested edits, version history, usage analytics, and controls over skill distribution. The API provides endpoints for loading skills in spec-compliant file formats, with examples including synchronization to GitHub, installation through Vercel’s Skills CLI, and uploads or edits through MCP tools. Notion says early customers and partners are already using the API across agents and tools, while an open-source starter kit supports Notion-to-GitHub synchronization. Vercel’s Skills CLI can install individual Notion skill pages or workspace plugins, using standards-compliant files without handling Notion-specific formats.

• AWS

  Building cloud-native PACS on AWS

  Multi-hospital networks face rising imaging volumes, siloed on-premises PACS, radiologist routing bottlenecks, and storage that must expand for 7 to 10 years of retention. The proposed pattern uses a hub-and-spoke hybrid architecture: local PACS instances preserve LAN-speed reading, while a centralized AWS archive provides cross-facility discovery, disaster recovery, and lifecycle-managed storage. Modalities send DICOM through C-STORE to local VNA servers, which normalize and compress objects; asynchronous replication sends images to Amazon S3, while Amazon Aurora PostgreSQL stores metadata and routing information. The AWS deployment spans two Availability Zones, places PACS services behind Network Load Balancers, and includes CloudFront and AWS WAF. Storage guidance distinguishes S3 Intelligent-Tiering, Glacier Instant Retrieval, and Glacier Deep Archive according to access frequency and retention needs.

• AWS

  How DHI Group accelerates generative AI workloads from idea to production using hackathons

  DHI Group needed to move generative AI efforts beyond proofs of concept because its traditional software development lifecycle took months, while it sought faster delivery, technical validation, and broader AI literacy. AWS and DHI used a four-phase Hackathon Acceleration Package—preparation, enablement, a three-day build event, and a path to production—with workshops on Amazon Bedrock AgentCore, AI-DLC, and Kiro. Twenty participants formed three teams and produced prototypes for employer analytics, intelligent candidate matching, and a unified ClearanceJobs–AgileATS marketplace; DHI leadership committed to advancing all three toward production. The winning marketplace uses an MCP server, Amazon Bedrock AgentCore, Lambda functions, session memory, and Claude 3.5 Haiku to let recruiters search candidates and enrich profiles through natural-language requests. The post concludes that time-boxed, cross-functional hackathons can compress ideation, architecture, prototyping, executive alignment, and production planning when production criteria and preparation are established upfront.

• Clickhouse

  Postgres week in the Netherlands: PGDay Lowlands & Percona Live 2026

  An account of three days in the Netherlands covers talks at PGDay Lowlands in Utrecht and Percona Live 2026 in Amsterdam, including a five-minute presentation on ClickHouse integrations and a PostgreSQL 19 monitoring session. pg_clickhouse uses a foreign data wrapper to expose ClickHouse tables as PostgreSQL foreign tables, allowing existing queries, ORMs, and dashboards to continue working while pushable work runs in ClickHouse; 15 of 22 TPC-H queries at scale factor 1 are fully pushed down. pg_stat_ch captures per-query execution events in a shared-memory ring buffer and sends batches to ClickHouse, dropping events rather than blocking PostgreSQL when ClickHouse is unavailable. The monitoring talk covered PostgreSQL 19 logging, WAL and I/O statistics, WAIT FOR, new system views, and multixact and wraparound changes. The post also reports talks on optimizer hints and plan stabilization, and says both conferences will return in 2027.

• Clickhouse

  September 2026 newsletter

  The September 2026 ClickHouse newsletter gathers product updates, community contributions, technical articles, and upcoming events. Its main release coverage describes ClickHouse 26.8, including custom HTTP handlers, dynamic query filtering, pipelined SQL through the |> operator, current-user query logging, a URL database engine, and Japanese and Chinese text-index tokenizers. Other featured developments include On-Demand Compute in private preview with a cost-based optimizer and distributed query execution, PromQL and a TimeSeries engine in private preview, AI Functions, and Postgres integrations such as WalShadow and Managed Postgres on Google Cloud. The issue also reports CostBench’s first end-to-end performance-per-dollar results, explains replication-queue diagnosis, notes 57 breaking changes since 26.3, and lists training, webinars, roadshows, and other events.

• Red Hat

  From hours to minutes: Optimizing Red Hat Developer Hub performance testing with immutable LDAP images

  Red Hat Developer Hub performance testing became slow and unreliable as runtime generation of large user and group catalogs stretched environment setup and introduced synchronization failures. Previously, the framework created entries through serialized Keycloak Admin REST API operations, then waited for paginated synchronization into the Developer Hub database; concurrency could not eliminate timeouts, rate limits, or incomplete catalogs. The replacement uses immutable, pre-built LDAP container images selected by an RBAC_POLICY-USER_COUNTu-GROUP_COUNTg convention, with slapadd loading seed data directly into offline LMDB files in a multi-stage build. LDAP starts with 10,000-plus indexed users, while Keycloak serves as an authentication gateway and Developer Hub waits for its initial catalog sync. Reported population time fell from 22-plus hours to 2 minutes 8 seconds for 10,000 users and 150,000 groups, while the immutable approach made tests deterministic, reduced flaky failures, stabilized baselines, and enabled larger reproducible scenarios.

• Red Hat

  Catching poor LLM performance and accuracy before deployment

  Rapid changes in vLLM and the path from upstream releases to Red Hat AI Inference images can introduce performance and accuracy regressions that ordinary CI/CD tests miss. The midstream regression detector benchmarks upstream and release-candidate builds across hardware variants, using GuideLLM at multiple concurrency levels for performance and GSM8K for accuracy. It stores nightly upstream results, compares them with midstream benchmarks against threshold deltas, and feeds confirmed failures into fixes and rebuilds before release. To reduce false positives from limited samples, the workflow adds Wasserstein distance as a secondary check of whole request-response distributions rather than relying only on medians or means. The system also connects benchmark runs with prior JIRA regressions through a custom Claude skill that suggests possible fixes and assesses whether a flagged change is genuine.

• Red Hat

  Build a unified CI/CD control plane with Red Hat Developer Hub

  Red Hat Developer Hub brings OpenShift, Argo CD, Tekton, and Quay workflows into a unified developer portal, addressing context switching across separate consoles. The guide targets platform engineers and covers installing the Operator, creating GitHub and cluster credentials, configuring application and dynamic-plugin settings, defining RBAC policies, and deploying a Backstage custom resource. It uses a Kubernetes service-account token for access to pods, deployments, and pipeline runs, while Quay integration exposes image tags, vulnerabilities, and manifest details. After granting read access in monitored namespaces, the resulting portal can display pipeline runs, deployment health, image information, and Argo CD status in one view. The source says the setup is a proof-of-concept foundation, with a follow-up planned for software templates and developer self-service.

• Jetbrains

  Building a RAG Pipeline for Semantic Code Search: A Developer Diary and Field Notes

  JetBrains Context is presented as a production RAG pipeline for semantic code search, designed to give coding agents precise, citable evidence from repositories instead of relying on keyword tools such as grep. This first installment covers parsing, structure-aware chunking, and vectorization, with the goal of retrieving meaningful functions, symbols, or snippets rather than whole files or insignificant lines. Language parsers produce syntax nodes, and the algorithm retains the largest units that fit, splits oversized leaf nodes when necessary, groups small adjacent units, and keeps documentation, annotations, modifiers, and closing syntax with their constructs. JetBrains Context supports this approach for Kotlin, Java, Python, JavaScript, TypeScript, C#, PHP, Go, and Rust; other languages use line-based splitting. Vectors are generated with an open-weight model on company-operated GPUs, while indexed records store coordinates rather than source code, and the post reports that this setup outperformed hosted embedding APIs on internal code-retrieval benchmarks.

• Twilio

  How we AI-updated 1,138 Error-code Docs Pages

  Twilio used AI to update 1,138 error-code documentation pages over about 12 weeks, with a human reviewing every change. The team first scored roughly 2,692 pages with a deterministic script covering structure, content, and resources, then routed low-scoring pages to an LLM pipeline while sending borderline pages to human review. That pipeline used OpenAI's gpt-5.4 via the Responses API, generated full-file responses, sanitized them, converted them into git apply patches, linted results, and rejected any page whose code snippet fingerprint changed. Small-batch pull requests, tracking files, local-modification checks, and named reviewers limited duplicate work and kept approval in the workflow. Across about 27 pull requests from March to May 2026, the process marked 1,138 error codes complete, while the team acknowledged that human review was the quality bar and that future scaling would benefit from an automated evaluation harness and diff-based generation.

• Twilio

  Twilio’s 2026 Heightened Awareness Period: Ensuring Reliable Messaging for Peak Season

  Twilio has scheduled two 2026 Heightened Awareness Periods (HAPs) to manage messaging throughput during U.S. midterm election traffic and the Black Friday/Cyber Monday and holiday shopping surge. During these windows, high-volume short code and toll-free traffic shifts temporarily to Market Throughput, while 10DLC remains on Account-Based Throughput and RCS uses standard per-sender limits; contracted limits are honored. Most users need no action, but election senders should contact their account team by October 1, 2026, and holiday senders face deadlines for RCS approval, throughput review, A2P 10DLC requests, and supplementary orders. The election HAP runs November 2–4, 2026, while the holiday HAP runs November 19, 2026, through January 4, 2027; capacity is limited and allocated first come, first served.

• Boxcompute

  Full Linux VMs for your agents

  BoxCompute VM Sandboxes are now the default runtime for every account, giving agents a full Linux virtual machine rather than a shared-kernel gVisor container. Each disposable VM boots its own kernel and provides root access, outbound internet with public IPv4 and DNS, and a unified approximately 10 GiB filesystem covering / and /workspace, while preserving the existing create, execute, file-transfer, and delete API. The CLI or HTTP API can create a VM, and users can opt out with vmSandbox: false or disable networking with blockNetwork: true. VMs remain billable until explicitly deleted and currently use a fixed profile of 0.5 CPU, 1 GiB memory, and a minimal Ubuntu image. The beta does not include inbound ports, SSH, custom images, or volumes.

• Google

  Why client SDK generation belongs in the open

  Google describes partnering with Speakeasy to open-source the OpenAPI code-generation suite used for new SDKs for its Interactions, Agents, and Webhooks APIs. The change follows the May 2026 shutdown of a proprietary SDK-generation provider, which exposed platform risk while Google was preparing the Interactions API for general availability; migration prioritized avoiding breaking changes and preserving type definitions, strict error hierarchies, and streaming behavior. The AGPLv3 suite generates statically typed libraries for Python, TypeScript, Go, Java, C#, PHP, and Ruby, plus standalone agent-native CLI binaries and documentation MCP servers built from OpenAPI specifications and Markdown. Google says a deterministic generator paired with Antigravity AI agents now supports its pipeline across six targets, including three released SDKs, with roughly one engineer maintaining it, while generated code can remain under a chosen license such as MIT or Apache 2.0.

• Auth0

  Preventing Destructive Actions with Step-up Authentication

  The Agentic Arcade’s admin panel adds an admin-only “reset all scores” action to prevent a long-lived or stolen admin session from wiping every player’s history. It combines the arcade-admin role with step-up MFA, requiring a recognized MFA signal and auth_time or iat within five minutes. A shared helper checks amr, acr, or a tenant claim; buildMfaStepUpUrl uses acr_values and can add max_age=0, while mfa.challengeWithPopup() opens MFA before the reset request. A beforeSessionSaved hook preserves claims filtered by the Auth0 Next.js SDK, and the API enforces session, role, and freshness gates before clearing scores; cancelled or blocked popups stop the request.

• Apple

  REVERSAL-BENCH: A Reversibility Axis and Reset Oracle for Measuring the Reset-Free RL Cliff

  REVERSAL-BENCH addresses the challenge of evaluating reset-free reinforcement learning when environments contain irreversible transitions. It controls reversibility with continuous parameter ρ ∈ [0, 1] and supplies a reset oracle, a ground-truth mechanism for verifying state recoverability across eight manipulation settings and five physics engines. Evaluations spanning standard actor-critic, safe reinforcement learning, and specialized reset-free methods find a sharp reversibility cliff: reset-free agents become absorbed into irrecoverable states as ρ increases, while episodic agents maintain steady learning. Geometrically identical reversible counterparts indicate the breakdown is caused by irreversibility rather than obstacle complexity, and the effect persists under learned policies in full physics simulations. The released suite includes a multi-simulator dataset with recoverability labels and a reset oracle; a safety shield predicts recoverability accurately, but active recovery mainly works when agents can steer away from traps.

• Databricks

  A multi agent approach audience intelligence

  Advertisers often lose strategic intent when campaign briefs become data queries, while planners and data teams also miss insights hidden across large customer datasets. An AI-powered audience generation solution on the Databricks Data + AI Platform addresses this gap by combining Genie, custom tool-calling agents, Agent Bricks, Unity Catalog, and a Databricks App. Planners describe audiences in natural language; Genie produces governed SQL segments, an Affinity Agent calculates statistically validated lift against the full population, and a Supervisor Agent routes or chains these capabilities. The resulting workflow saves audiences in Unity Catalog for auditability and downstream activation, and is described as compressing planning and iteration cycles from days or weeks to minutes while enabling faster response to market shifts and pacing issues.