<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:dc="http://purl.org/dc/elements/1.1/" version="2.0">
  <channel>
    <title>InfoQ - Development - Articles</title>
    <link>https://www.infoq.com</link>
    <description>InfoQ Development Articles feed</description>
    <item>
      <title>Article: Scaling Java-Based Real-Time Systems: The Hidden Tradeoffs of Event-Driven Design</title>
      <link>https://www.infoq.com/articles/tradeoffs-event-driven-design/?utm_campaign=infoq_content&amp;utm_source=infoq&amp;utm_medium=feed&amp;utm_term=Development-articles</link>
      <description>&lt;img src="https://res.infoq.com/articles/tradeoffs-event-driven-design/en/headerimage/tradeoffs-event-driven-design-header-1782458803116.jpg"/&gt;&lt;p&gt;Event-driven architecture promises scalability, but in Java-based real-time systems the tradeoffs only surface in production. Drawing on a Java/Kafka contact center platform handling 80k BHCC across 10k agents, this article details where the design breaks down—state management, partition limits, deduplication, JVM tuning, cascading consumer failures—and the Redis-backed patterns that fixed each.&lt;/p&gt; &lt;i&gt;By Sagar Deepak Joshi&lt;/i&gt;</description>
      <category>Apache Kafka</category>
      <category>Java</category>
      <category>Spring Boot</category>
      <category>Redis</category>
      <category>Architecture &amp; Design</category>
      <category>Development</category>
      <category>article</category>
      <pubDate>Tue, 30 Jun 2026 09:00:00 GMT</pubDate>
      <guid>https://www.infoq.com/articles/tradeoffs-event-driven-design/?utm_campaign=infoq_content&amp;utm_source=infoq&amp;utm_medium=feed&amp;utm_term=Development-articles</guid>
      <dc:creator>Sagar Deepak Joshi</dc:creator>
      <dc:date>2026-06-30T09:00:00Z</dc:date>
      <dc:identifier>/articles/tradeoffs-event-driven-design/en</dc:identifier>
    </item>
    <item>
      <title>Article: Virtual panel: Security in the Machine Age: Expert Insights on AI Threat Evolution</title>
      <link>https://www.infoq.com/articles/security-ai-threat-evolution/?utm_campaign=infoq_content&amp;utm_source=infoq&amp;utm_medium=feed&amp;utm_term=Development-articles</link>
      <description>&lt;img src="https://res.infoq.com/articles/security-ai-threat-evolution/en/headerimage/security-ai-threat-evolution-header-1782202845102.jpg"/&gt;&lt;p&gt;This virtual panel brings together AI security experts to examine the evolution of AI-driven threats, from prompt injection and data poisoning to agent abuse and AI-powered social engineering. The discussion explores emerging attack patterns, incident response challenges, and the changes security teams must make as AI systems become more autonomous and integrated into critical workflows.&lt;/p&gt; &lt;i&gt;By Claudio Masolo, Elham Arshad, Sabri Allani, Vijay Dilwale, Igor Maljkovic&lt;/i&gt;</description>
      <category>Governance</category>
      <category>AI Security</category>
      <category>Adversarial Machine Learning</category>
      <category>Virtual Panel</category>
      <category>Architecture &amp; Design</category>
      <category>Development</category>
      <category>AI, ML &amp; Data Engineering</category>
      <category>article</category>
      <pubDate>Mon, 29 Jun 2026 11:00:00 GMT</pubDate>
      <guid>https://www.infoq.com/articles/security-ai-threat-evolution/?utm_campaign=infoq_content&amp;utm_source=infoq&amp;utm_medium=feed&amp;utm_term=Development-articles</guid>
      <dc:creator>Claudio Masolo, Elham Arshad, Sabri Allani, Vijay Dilwale, Igor Maljkovic</dc:creator>
      <dc:date>2026-06-29T11:00:00Z</dc:date>
      <dc:identifier>/articles/security-ai-threat-evolution/en</dc:identifier>
    </item>
    <item>
      <title>Article: Beyond CLEAN and MVP: Architecting an Offline-First Reactive Data Layer in Android</title>
      <link>https://www.infoq.com/articles/rdla-offline-first-reactive-android-data-layer/?utm_campaign=infoq_content&amp;utm_source=infoq&amp;utm_medium=feed&amp;utm_term=Development-articles</link>
      <description>&lt;img src="https://res.infoq.com/articles/rdla-offline-first-reactive-android-data-layer/en/headerimage/rdla-offline-first-reactive-android-data-layer-header-1781776366032.jpg"/&gt;&lt;p&gt;With the Reactive Data Layer Architecture (RDLA), you establish a clear boundary between public data APIs and private, framework-specific data-source implementations. Your presentation layer operates in a purely reactive manner, observing data changes rather than procedurally querying them. RDLA also simplifies testing by encouraging you to program to interfaces and use clean seeding patterns.&lt;/p&gt; &lt;i&gt;By Mervyn Anthony&lt;/i&gt;</description>
      <category>Mobile</category>
      <category>Asynchronous Architecture</category>
      <category>MVP</category>
      <category>Reactive Programming</category>
      <category>Clean Architecture</category>
      <category>Android</category>
      <category>Architecture &amp; Design</category>
      <category>Development</category>
      <category>article</category>
      <pubDate>Wed, 24 Jun 2026 09:00:00 GMT</pubDate>
      <guid>https://www.infoq.com/articles/rdla-offline-first-reactive-android-data-layer/?utm_campaign=infoq_content&amp;utm_source=infoq&amp;utm_medium=feed&amp;utm_term=Development-articles</guid>
      <dc:creator>Mervyn Anthony</dc:creator>
      <dc:date>2026-06-24T09:00:00Z</dc:date>
      <dc:identifier>/articles/rdla-offline-first-reactive-android-data-layer/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=Development-articles</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>AI Security</category>
      <category>Adversarial Machine Learning</category>
      <category>Architecture &amp; Design</category>
      <category>Development</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=Development-articles</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>
  </channel>
</rss>
