<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:dc="http://purl.org/dc/elements/1.1/" version="2.0">
  <channel>
    <title>InfoQ - Architecture &amp; Design</title>
    <link>https://www.infoq.com</link>
    <description>InfoQ Architecture &amp; Design feed</description>
    <item>
      <title>Presentation: Challenging Google Analytics: Building a Scalable, Cost-Effective User Tracking Service</title>
      <link>https://www.infoq.com/presentations/mobile-user-tracking-service/?utm_campaign=infoq_content&amp;utm_source=infoq&amp;utm_medium=feed&amp;utm_term=Architecture+%26+Design</link>
      <description>&lt;img src="https://res.infoq.com/presentations/mobile-user-tracking-service/en/mediumimage/alina-krasavina-medium-1781688348523.jpg"/&gt;&lt;p&gt;Alina Krasavina explains how Delivery Hero successfully deprecated Google Analytics and migrated to an internal user tracking platform. She discusses how a simplistic, highly scalable architecture allowed them to handle 10 times more load while capturing 97% of tracking data.&lt;/p&gt; &lt;i&gt;By Alina Krasavina&lt;/i&gt;</description>
      <category>Mobile</category>
      <category>Data Analytics</category>
      <category>Transcripts</category>
      <category>Cross Platform</category>
      <category>InfoQ Dev Summit Munich 2025</category>
      <category>Development</category>
      <category>Architecture &amp; Design</category>
      <category>presentation</category>
      <pubDate>Mon, 22 Jun 2026 15:07:00 GMT</pubDate>
      <guid>https://www.infoq.com/presentations/mobile-user-tracking-service/?utm_campaign=infoq_content&amp;utm_source=infoq&amp;utm_medium=feed&amp;utm_term=Architecture+%26+Design</guid>
      <dc:creator>Alina Krasavina</dc:creator>
      <dc:date>2026-06-22T15:07:00Z</dc:date>
      <dc:identifier>/presentations/mobile-user-tracking-service/en</dc:identifier>
    </item>
    <item>
      <title>Java News Roundup: Spring Tools, Helidon, Open Liberty, TomEE, JobRunr, Hibernate, Commonhaus</title>
      <link>https://www.infoq.com/news/2026/06/java-news-roundup-jun15-2026/?utm_campaign=infoq_content&amp;utm_source=infoq&amp;utm_medium=feed&amp;utm_term=Architecture+%26+Design</link>
      <description>&lt;img src="https://res.infoq.com/news/2026/06/java-news-roundup-jun15-2026/en/headerimage/java-news-roundup-image-1782133635464.jpg"/&gt;&lt;p&gt;This week's Java roundup for June 15th, 2026, features news highlighting: point releases of Spring Tools, Helidon, JobRunr and Gradle; the June 2026 edition of Open Liberty; the first milestone release of Apache TomEE 11.0; the first beta release of Hibernate ORM 8.0; Quarkus emergency maintenance releases to address CVE-2026-50559; and four open-source projects join the Commonhaus Foundation.&lt;/p&gt; &lt;i&gt;By Michael Redlich&lt;/i&gt;</description>
      <category>Gradle</category>
      <category>JDK 27</category>
      <category>Hibernate ORM</category>
      <category>JDK 28</category>
      <category>Open Liberty</category>
      <category>Apache TomEE</category>
      <category>Spring Framework</category>
      <category>Open JDK</category>
      <category>Helidon</category>
      <category>Commonhaus Foundation</category>
      <category>Quarkus</category>
      <category>Java</category>
      <category>JobRunr</category>
      <category>Development</category>
      <category>Architecture &amp; Design</category>
      <category>news</category>
      <pubDate>Mon, 22 Jun 2026 13:15:00 GMT</pubDate>
      <guid>https://www.infoq.com/news/2026/06/java-news-roundup-jun15-2026/?utm_campaign=infoq_content&amp;utm_source=infoq&amp;utm_medium=feed&amp;utm_term=Architecture+%26+Design</guid>
      <dc:creator>Michael Redlich</dc:creator>
      <dc:date>2026-06-22T13:15:00Z</dc:date>
      <dc:identifier>/news/2026/06/java-news-roundup-jun15-2026/en</dc:identifier>
    </item>
    <item>
      <title>Article: Understanding ML Model Poisoning: How It Happens and How to Detect It</title>
      <link>https://www.infoq.com/articles/understanding-ml-model-poisoning/?utm_campaign=infoq_content&amp;utm_source=infoq&amp;utm_medium=feed&amp;utm_term=Architecture+%26+Design</link>
      <description>&lt;img src="https://res.infoq.com/articles/understanding-ml-model-poisoning/en/headerimage/header-understanding-ml-model-poisoning-1781597719189.jpg"/&gt;&lt;p&gt;In this article, the author explores data poisoning as a threat to machine learning systems, covering techniques such as label flipping, backdoors, clean-label poisoning, and gradient manipulation. The article reviews real-world incidents, discusses the challenges of detecting poisoned data, and presents practical defenses, tools, and operational practices for securing ML training pipelines.&lt;/p&gt; &lt;i&gt;By Igor Maljkovic&lt;/i&gt;</description>
      <category>Adversarial Machine Learning</category>
      <category>AI Security</category>
      <category>Development</category>
      <category>Architecture &amp; Design</category>
      <category>AI, ML &amp; Data Engineering</category>
      <category>article</category>
      <pubDate>Mon, 22 Jun 2026 11:00:00 GMT</pubDate>
      <guid>https://www.infoq.com/articles/understanding-ml-model-poisoning/?utm_campaign=infoq_content&amp;utm_source=infoq&amp;utm_medium=feed&amp;utm_term=Architecture+%26+Design</guid>
      <dc:creator>Igor Maljkovic</dc:creator>
      <dc:date>2026-06-22T11:00:00Z</dc:date>
      <dc:identifier>/articles/understanding-ml-model-poisoning/en</dc:identifier>
    </item>
    <item>
      <title>AWS Graviton5 Reaches General Availability with 192 Cores and Formally Verified VM Isolation</title>
      <link>https://www.infoq.com/news/2026/06/aws-graviton5-ga/?utm_campaign=infoq_content&amp;utm_source=infoq&amp;utm_medium=feed&amp;utm_term=Architecture+%26+Design</link>
      <description>&lt;img src="https://res.infoq.com/news/2026/06/aws-graviton5-ga/en/headerimage/generatedHeaderImage-1781703289721.jpg"/&gt;&lt;p&gt;AWS made Graviton5-powered EC2 M9g and M9gd instances generally available with 192 ARM cores, formally verified VM isolation via the Nitro Isolation Engine, and DDR5-8800 memory. ClickHouse reported 36% better performance with zero code changes. Meta committed tens of millions of cores. On-demand pricing is 9% above Graviton4, translating to roughly 15% better price-performance.&lt;/p&gt; &lt;i&gt;By Steef-Jan Wiggers&lt;/i&gt;</description>
      <category>AI Architecture</category>
      <category>AWS</category>
      <category>IaaS</category>
      <category>Containers</category>
      <category>Cloud</category>
      <category>Cloud Architecture</category>
      <category>Development</category>
      <category>Architecture &amp; Design</category>
      <category>DevOps</category>
      <category>AI, ML &amp; Data Engineering</category>
      <category>news</category>
      <pubDate>Mon, 22 Jun 2026 10:05:00 GMT</pubDate>
      <guid>https://www.infoq.com/news/2026/06/aws-graviton5-ga/?utm_campaign=infoq_content&amp;utm_source=infoq&amp;utm_medium=feed&amp;utm_term=Architecture+%26+Design</guid>
      <dc:creator>Steef-Jan Wiggers</dc:creator>
      <dc:date>2026-06-22T10:05:00Z</dc:date>
      <dc:identifier>/news/2026/06/aws-graviton5-ga/en</dc:identifier>
    </item>
    <item>
      <title>Anthropic Reports Claude Now Handles 95% of Internal Analytics Queries</title>
      <link>https://www.infoq.com/news/2026/06/anthropic-claude-analytics/?utm_campaign=infoq_content&amp;utm_source=infoq&amp;utm_medium=feed&amp;utm_term=Architecture+%26+Design</link>
      <description>&lt;img src="https://res.infoq.com/news/2026/06/anthropic-claude-analytics/en/headerimage/generatedHeaderImage-1781542483302.jpg"/&gt;&lt;p&gt;Anthropic recently reported that Claude now handles around 95% of its internal analytics requests, letting employees query business data independently instead of relying on data teams. The company attributes this result less to advances in models and more to data governance, semantic definitions, and operational discipline.&lt;/p&gt; &lt;i&gt;By Renato Losio&lt;/i&gt;</description>
      <category>Business Analytics</category>
      <category>Claude</category>
      <category>Data Analytics</category>
      <category>Data Lake</category>
      <category>Anthropic</category>
      <category>Data Governance</category>
      <category>Architecture &amp; Design</category>
      <category>AI, ML &amp; Data Engineering</category>
      <category>news</category>
      <pubDate>Sun, 21 Jun 2026 16:47:00 GMT</pubDate>
      <guid>https://www.infoq.com/news/2026/06/anthropic-claude-analytics/?utm_campaign=infoq_content&amp;utm_source=infoq&amp;utm_medium=feed&amp;utm_term=Architecture+%26+Design</guid>
      <dc:creator>Renato Losio</dc:creator>
      <dc:date>2026-06-21T16:47:00Z</dc:date>
      <dc:identifier>/news/2026/06/anthropic-claude-analytics/en</dc:identifier>
    </item>
    <item>
      <title>Inside Atlassian’s Forge Billing Architecture for Distributed Usage Tracking at Scale</title>
      <link>https://www.infoq.com/news/2026/06/forge-billing-usage-platform/?utm_campaign=infoq_content&amp;utm_source=infoq&amp;utm_medium=feed&amp;utm_term=Architecture+%26+Design</link>
      <description>&lt;img src="https://res.infoq.com/news/2026/06/forge-billing-usage-platform/en/headerimage/generatedHeaderImage-1780198060365.jpg"/&gt;&lt;p&gt;Atlassian details the Forge billing platform built for usage-based pricing across its cloud ecosystem. It processes large-scale usage events with correct attribution, deduplication, and aggregation using a streaming pipeline, idempotent processing, and layered storage to enable accurate billing, near real-time visibility, and reliable reconciliation across distributed services.&lt;/p&gt; &lt;i&gt;By Leela Kumili&lt;/i&gt;</description>
      <category>Event Stream Processing</category>
      <category>Atlassian</category>
      <category>Jira</category>
      <category>Multi-tenancy</category>
      <category>Apache Kafka</category>
      <category>Event Driven Architecture</category>
      <category>Streaming</category>
      <category>Observability</category>
      <category>FinOps</category>
      <category>SaaS</category>
      <category>Distributed Systems</category>
      <category>Cloud Architecture</category>
      <category>Architecture &amp; Design</category>
      <category>Development</category>
      <category>news</category>
      <pubDate>Sat, 20 Jun 2026 14:21:00 GMT</pubDate>
      <guid>https://www.infoq.com/news/2026/06/forge-billing-usage-platform/?utm_campaign=infoq_content&amp;utm_source=infoq&amp;utm_medium=feed&amp;utm_term=Architecture+%26+Design</guid>
      <dc:creator>Leela Kumili</dc:creator>
      <dc:date>2026-06-20T14:21:00Z</dc:date>
      <dc:identifier>/news/2026/06/forge-billing-usage-platform/en</dc:identifier>
    </item>
    <item>
      <title>AWS Adds Multi-Region Replication to Amazon Cognito Identity Service</title>
      <link>https://www.infoq.com/news/2026/06/cognito-replication-aws/?utm_campaign=infoq_content&amp;utm_source=infoq&amp;utm_medium=feed&amp;utm_term=Architecture+%26+Design</link>
      <description>&lt;img src="https://res.infoq.com/news/2026/06/cognito-replication-aws/en/headerimage/generatedHeaderImage-1780821804660.jpg"/&gt;&lt;p&gt;AWS recently introduced Amazon Cognito multi-region replication, which automatically replicates user identities and user pool configurations from a primary region to a secondary one. This enables applications to continue authenticating users from a replica region during outages, without requiring custom replication and failover mechanisms.&lt;/p&gt; &lt;i&gt;By Renato Losio&lt;/i&gt;</description>
      <category>Authentication</category>
      <category>Cloud Security</category>
      <category>Identity Management</category>
      <category>AWS</category>
      <category>multi-region</category>
      <category>Availability</category>
      <category>Cloud</category>
      <category>Development</category>
      <category>Architecture &amp; Design</category>
      <category>news</category>
      <pubDate>Sat, 20 Jun 2026 07:40:00 GMT</pubDate>
      <guid>https://www.infoq.com/news/2026/06/cognito-replication-aws/?utm_campaign=infoq_content&amp;utm_source=infoq&amp;utm_medium=feed&amp;utm_term=Architecture+%26+Design</guid>
      <dc:creator>Renato Losio</dc:creator>
      <dc:date>2026-06-20T07:40:00Z</dc:date>
      <dc:identifier>/news/2026/06/cognito-replication-aws/en</dc:identifier>
    </item>
    <item>
      <title>Behind the Scenes:  Block 450 JVM Repositories into Monorepo to Reduce Dependency Drift</title>
      <link>https://www.infoq.com/news/2026/06/block-450-jvm-monorepo-migration/?utm_campaign=infoq_content&amp;utm_source=infoq&amp;utm_medium=feed&amp;utm_term=Architecture+%26+Design</link>
      <description>&lt;img src="https://www.infoq.com/styles/static/images/logo/logo_bigger.jpg"/&gt;&lt;p&gt;Block, Inc. describes migrating ~450 JVM repositories into a monorepo across Cash App and Square engineering to reduce dependency drift and coordination overhead. The system supports ~8,800 weekly builds with ~10 min p90 CI time. The approach improves cross-service changes, build visibility, and developer experience through dependency graph–based builds, selective CI, and custom IDE tooling.&lt;/p&gt; &lt;i&gt;By Leela Kumili&lt;/i&gt;</description>
      <category>IntelliJ IDEA</category>
      <category>JVM</category>
      <category>Platform Engineering</category>
      <category>Large Projects</category>
      <category>Continuous Integration</category>
      <category>plugins</category>
      <category>Java</category>
      <category>Distributed Systems</category>
      <category>Continuous Deployment</category>
      <category>Build systems</category>
      <category>IDE</category>
      <category>Architecture &amp; Design</category>
      <category>Development</category>
      <category>DevOps</category>
      <category>news</category>
      <pubDate>Fri, 19 Jun 2026 14:47:00 GMT</pubDate>
      <guid>https://www.infoq.com/news/2026/06/block-450-jvm-monorepo-migration/?utm_campaign=infoq_content&amp;utm_source=infoq&amp;utm_medium=feed&amp;utm_term=Architecture+%26+Design</guid>
      <dc:creator>Leela Kumili</dc:creator>
      <dc:date>2026-06-19T14:47:00Z</dc:date>
      <dc:identifier>/news/2026/06/block-450-jvm-monorepo-migration/en</dc:identifier>
    </item>
    <item>
      <title>Article: Designing Continuous Authorization for Sensitive Cloud Systems</title>
      <link>https://www.infoq.com/articles/continuous-authorization-cloud/?utm_campaign=infoq_content&amp;utm_source=infoq&amp;utm_medium=feed&amp;utm_term=Architecture+%26+Design</link>
      <description>&lt;img src="https://res.infoq.com/articles/continuous-authorization-cloud/en/headerimage/continuous-authorization-cloud-header-1781599988842.jpg"/&gt;&lt;p&gt;Most cloud systems make one authorization decision at login. Everything after runs on trust established at authentication time. For systems handling regulated data, that gap is where breaches happen. This article presents a continuous authorization architecture covering risk-tiered evaluation, behavioral baselines, privacy-preserving audit trails, and a phased and incremental rollout.&lt;/p&gt; &lt;i&gt;By Venkata Nedunoori&lt;/i&gt;</description>
      <category>Authorization</category>
      <category>Zero Trust</category>
      <category>Data Privacy</category>
      <category>Cloud Security</category>
      <category>Identity Management</category>
      <category>GDPR</category>
      <category>Cloud</category>
      <category>Compliance</category>
      <category>Architecture &amp; Design</category>
      <category>DevOps</category>
      <category>article</category>
      <pubDate>Fri, 19 Jun 2026 09:00:00 GMT</pubDate>
      <guid>https://www.infoq.com/articles/continuous-authorization-cloud/?utm_campaign=infoq_content&amp;utm_source=infoq&amp;utm_medium=feed&amp;utm_term=Architecture+%26+Design</guid>
      <dc:creator>Venkata Nedunoori</dc:creator>
      <dc:date>2026-06-19T09:00:00Z</dc:date>
      <dc:identifier>/articles/continuous-authorization-cloud/en</dc:identifier>
    </item>
    <item>
      <title>Azure Functions Ships Serverless Agents Runtime at Build 2026</title>
      <link>https://www.infoq.com/news/2026/06/azure-functions-serverless-agent/?utm_campaign=infoq_content&amp;utm_source=infoq&amp;utm_medium=feed&amp;utm_term=Architecture+%26+Design</link>
      <description>&lt;img src="https://res.infoq.com/news/2026/06/azure-functions-serverless-agent/en/headerimage/generatedHeaderImage-1781769901887.jpg"/&gt;&lt;p&gt;Azure Functions shipped a serverless agents runtime in public preview at Build 2026. Agents are defined in .agent.md markdown files with YAML triggers, MCP server access, 1,400+ connectors, and sandboxed execution. The Functions team confirmed to InfoQ that the runtime adds no cold start overhead and no billing premium beyond standard Flex Consumption.&lt;/p&gt; &lt;i&gt;By Steef-Jan Wiggers&lt;/i&gt;</description>
      <category>Agents</category>
      <category>AI Architecture</category>
      <category>Microsoft Azure</category>
      <category>Cloud</category>
      <category>FaaS</category>
      <category>Azure Functions</category>
      <category>Development</category>
      <category>Architecture &amp; Design</category>
      <category>DevOps</category>
      <category>AI, ML &amp; Data Engineering</category>
      <category>news</category>
      <pubDate>Fri, 19 Jun 2026 08:57:00 GMT</pubDate>
      <guid>https://www.infoq.com/news/2026/06/azure-functions-serverless-agent/?utm_campaign=infoq_content&amp;utm_source=infoq&amp;utm_medium=feed&amp;utm_term=Architecture+%26+Design</guid>
      <dc:creator>Steef-Jan Wiggers</dc:creator>
      <dc:date>2026-06-19T08:57:00Z</dc:date>
      <dc:identifier>/news/2026/06/azure-functions-serverless-agent/en</dc:identifier>
    </item>
    <item>
      <title>From Camera to Cloud: Netflix’s Scalable Media Processing Pipeline</title>
      <link>https://www.infoq.com/news/2026/06/netflix-camera-file-processing/?utm_campaign=infoq_content&amp;utm_source=infoq&amp;utm_medium=feed&amp;utm_term=Architecture+%26+Design</link>
      <description>&lt;img src="https://res.infoq.com/news/2026/06/netflix-camera-file-processing/en/headerimage/generatedHeaderImage-1780195416361.jpg"/&gt;&lt;p&gt;Netflix has detailed a cloud-based system for scaling camera file processing across global film and TV workflows. The pipeline handles ingest, validation, metadata extraction, and media transformation at scale using FilmLight API and distributed compute. It standardizes workflows across editorial, VFX, and color pipelines, improving consistency and reducing manual handling across productions.&lt;/p&gt; &lt;i&gt;By Leela Kumili&lt;/i&gt;</description>
      <category>Netflix</category>
      <category>Orchestration</category>
      <category>Batch Processing</category>
      <category>Pipeline as Code</category>
      <category>Streaming Video</category>
      <category>Media</category>
      <category>Automation in the Cloud and Management at Scale</category>
      <category>Video Codec</category>
      <category>Scaling</category>
      <category>Cloud</category>
      <category>Architecture &amp; Design</category>
      <category>Culture &amp; Methods</category>
      <category>Development</category>
      <category>news</category>
      <pubDate>Thu, 18 Jun 2026 14:36:00 GMT</pubDate>
      <guid>https://www.infoq.com/news/2026/06/netflix-camera-file-processing/?utm_campaign=infoq_content&amp;utm_source=infoq&amp;utm_medium=feed&amp;utm_term=Architecture+%26+Design</guid>
      <dc:creator>Leela Kumili</dc:creator>
      <dc:date>2026-06-18T14:36:00Z</dc:date>
      <dc:identifier>/news/2026/06/netflix-camera-file-processing/en</dc:identifier>
    </item>
    <item>
      <title>Presentation: Write-Ahead Intent Log: a Foundation for Efficient CDC at Scale</title>
      <link>https://www.infoq.com/presentations/write-ahead-intent-log/?utm_campaign=infoq_content&amp;utm_source=infoq&amp;utm_medium=feed&amp;utm_term=Architecture+%26+Design</link>
      <description>&lt;img src="https://res.infoq.com/presentations/write-ahead-intent-log/en/mediumimage/vinay-chella-akshat-goel-medium-1781177310280.jpg"/&gt;&lt;p&gt;Vinay Chella and Akshat Goel discuss the challenges of running traditional CDC across heterogeneous databases during peak order traffic. They explain how Debezium hit limits under high load and share how they built Write-Ahead Intent Log (WAIL) - a custom architecture that utilizes a dumb producer proxy and a smart consumer pattern to cleanly separate the intent from the state payload.&lt;/p&gt; &lt;i&gt;By Vinay Chella, Akshat Goel&lt;/i&gt;</description>
      <category>Platform Engineering</category>
      <category>Transcripts</category>
      <category>QCon San Francisco 2025</category>
      <category>Data Access</category>
      <category>Architecture &amp; Design</category>
      <category>AI, ML &amp; Data Engineering</category>
      <category>presentation</category>
      <pubDate>Thu, 18 Jun 2026 13:13:00 GMT</pubDate>
      <guid>https://www.infoq.com/presentations/write-ahead-intent-log/?utm_campaign=infoq_content&amp;utm_source=infoq&amp;utm_medium=feed&amp;utm_term=Architecture+%26+Design</guid>
      <dc:creator>Vinay Chella, Akshat Goel</dc:creator>
      <dc:date>2026-06-18T13:13:00Z</dc:date>
      <dc:identifier>/presentations/write-ahead-intent-log/en</dc:identifier>
    </item>
    <item>
      <title>How Lightweight ADRs and Architectural Advice Forums Can Support Architectural Decisions</title>
      <link>https://www.infoq.com/news/2026/06/architectural-decisions/?utm_campaign=infoq_content&amp;utm_source=infoq&amp;utm_medium=feed&amp;utm_term=Architecture+%26+Design</link>
      <description>&lt;img src="https://res.infoq.com/news/2026/06/architectural-decisions/en/headerimage/generatedHeaderImage-1781423516304.jpg"/&gt;&lt;p&gt;How we decide is at the core of architecture, and the architecture advice process is a way to decentralize architectural decisions. It needs to be supported by Architecture Decision Records because of the speed at which technology and systems move, and can be complemented by a weekly architecture advice forum.&lt;/p&gt; &lt;i&gt;By Ben Linders&lt;/i&gt;</description>
      <category>GOTO Conference</category>
      <category>Feedback</category>
      <category>Patterns and Practices</category>
      <category>Architecture</category>
      <category>Architecture Decision Records</category>
      <category>Collaboration</category>
      <category>Culture &amp; Methods</category>
      <category>Architecture &amp; Design</category>
      <category>news</category>
      <pubDate>Thu, 18 Jun 2026 11:35:00 GMT</pubDate>
      <guid>https://www.infoq.com/news/2026/06/architectural-decisions/?utm_campaign=infoq_content&amp;utm_source=infoq&amp;utm_medium=feed&amp;utm_term=Architecture+%26+Design</guid>
      <dc:creator>Ben Linders</dc:creator>
      <dc:date>2026-06-18T11:35:00Z</dc:date>
      <dc:identifier>/news/2026/06/architectural-decisions/en</dc:identifier>
    </item>
    <item>
      <title>VS Code 1.123 Adds Two-Hour Extension Update Delay to Limit Supply Chain Attacks</title>
      <link>https://www.infoq.com/news/2026/06/vscode-extension-update-delay/?utm_campaign=infoq_content&amp;utm_source=infoq&amp;utm_medium=feed&amp;utm_term=Architecture+%26+Design</link>
      <description>&lt;img src="https://www.infoq.com/styles/static/images/logo/logo_bigger.jpg"/&gt;&lt;p&gt;VS Code 1.123 adds a two-hour delay before auto-updating extensions to newly published versions, creating a revocation window against supply chain attacks. The delay does not apply to trusted publishers like Microsoft, GitHub, and OpenAI. Similar cooldown mechanisms have now spread across pip, RubyGems, npm, pnpm, Yarn, and Bun.&lt;/p&gt; &lt;i&gt;By Steef-Jan Wiggers&lt;/i&gt;</description>
      <category>Visual Studio Code</category>
      <category>Application Security</category>
      <category>Software Supply Chain</category>
      <category>Development</category>
      <category>Architecture &amp; Design</category>
      <category>DevOps</category>
      <category>news</category>
      <pubDate>Thu, 18 Jun 2026 10:15:00 GMT</pubDate>
      <guid>https://www.infoq.com/news/2026/06/vscode-extension-update-delay/?utm_campaign=infoq_content&amp;utm_source=infoq&amp;utm_medium=feed&amp;utm_term=Architecture+%26+Design</guid>
      <dc:creator>Steef-Jan Wiggers</dc:creator>
      <dc:date>2026-06-18T10:15:00Z</dc:date>
      <dc:identifier>/news/2026/06/vscode-extension-update-delay/en</dc:identifier>
    </item>
    <item>
      <title>AI Agent Identity and Permission Challenges: How Uber and Auth0 Are Rethinking Access Control</title>
      <link>https://www.infoq.com/news/2026/06/ai-agent-identity-uber-auth0/?utm_campaign=infoq_content&amp;utm_source=infoq&amp;utm_medium=feed&amp;utm_term=Architecture+%26+Design</link>
      <description>&lt;img src="https://res.infoq.com/news/2026/06/ai-agent-identity-uber-auth0/en/headerimage/Auth0-Header-1781600533444.jpeg"/&gt;&lt;p&gt;Uber recently described an internal architecture for propagating identity across multi-agent AI workflows. The design aims to perserve user context, agent provenance, and scoped access as agents delegate work and call internal tools. The case study aligns with Auth0’s view that AI agents need permissions based on delegated authority, scoped credentials, and explicit human approval boundaries.&lt;/p&gt; &lt;i&gt;By Eran Stiller&lt;/i&gt;</description>
      <category>Model Context Protocol (MCP)</category>
      <category>Agents</category>
      <category>Agent2Agent</category>
      <category>OAuth</category>
      <category>Zero Trust</category>
      <category>Identity Management</category>
      <category>Architecture</category>
      <category>AI Security</category>
      <category>Architecture &amp; Design</category>
      <category>Development</category>
      <category>news</category>
      <pubDate>Wed, 17 Jun 2026 12:15:00 GMT</pubDate>
      <guid>https://www.infoq.com/news/2026/06/ai-agent-identity-uber-auth0/?utm_campaign=infoq_content&amp;utm_source=infoq&amp;utm_medium=feed&amp;utm_term=Architecture+%26+Design</guid>
      <dc:creator>Eran Stiller</dc:creator>
      <dc:date>2026-06-17T12:15:00Z</dc:date>
      <dc:identifier>/news/2026/06/ai-agent-identity-uber-auth0/en</dc:identifier>
    </item>
  </channel>
</rss>
