<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:dc="http://purl.org/dc/elements/1.1/" version="2.0">
  <channel>
    <title>InfoQ - Articles</title>
    <link>https://www.infoq.com</link>
    <description>InfoQ Articles feed</description>
    <item>
      <title>Article: Architecting Secure and Scalable Facial Verification Systems</title>
      <link>https://www.infoq.com/articles/secure-scalable-facial-verification/?utm_campaign=infoq_content&amp;utm_source=infoq&amp;utm_medium=feed&amp;utm_term=articles</link>
      <description>&lt;img src="https://res.infoq.com/articles/secure-scalable-facial-verification/en/headerimage/secure-scalable-facial-verification-header-1789468796366.jpg"/&gt;&lt;p&gt;When three thousand employees verify at once, synchronous API calls collapse. This article presents a four-layer architecture for high-volume face verification: client-side filtering that cut cloud costs 30%, decoupled detection and verification enabling 10x scaling, risk-based dynamic thresholds, and zero-trust privacy with consent gates and automated data purging for GDPR and HIPAA.&lt;/p&gt; &lt;i&gt;By Praveen Kumar Gopalakrishnan&lt;/i&gt;</description>
      <category>Cloud</category>
      <category>Security</category>
      <category>Architecture</category>
      <category>AI, ML &amp; Data Engineering</category>
      <category>DevOps</category>
      <category>Development</category>
      <category>Architecture &amp; Design</category>
      <category>article</category>
      <pubDate>Fri, 18 Sep 2026 09:00:00 GMT</pubDate>
      <guid>https://www.infoq.com/articles/secure-scalable-facial-verification/?utm_campaign=infoq_content&amp;utm_source=infoq&amp;utm_medium=feed&amp;utm_term=articles</guid>
      <dc:creator>Praveen Kumar Gopalakrishnan</dc:creator>
      <dc:date>2026-09-18T09:00:00Z</dc:date>
      <dc:identifier>/articles/secure-scalable-facial-verification/en</dc:identifier>
    </item>
    <item>
      <title>Article: Your Next DSL Author Is a Language Model</title>
      <link>https://www.infoq.com/articles/next-dsl-author-language-model/?utm_campaign=infoq_content&amp;utm_source=infoq&amp;utm_medium=feed&amp;utm_term=articles</link>
      <description>&lt;img src="https://res.infoq.com/articles/next-dsl-author-language-model/en/smallimage/Your-Next-DSL-Author-Is-a-Language-Model-thumb-1789048983233.jpg"/&gt;&lt;p&gt;In this article, the author introduces Typed Domain Grounding, an approach to reducing LLM hallucinations in domain-specific languages by embedding them in mainstream typed languages. Using kUML benchmarks and an infrastructure-as-code example, he explores how compiler validation and generate-compile-repair loops can make model-generated DSL output more reliable.&lt;/p&gt; &lt;i&gt;By Irakli Betchvaia&lt;/i&gt;</description>
      <category>Large language models</category>
      <category>Domain Specific Languages</category>
      <category>DSLs</category>
      <category>AI, ML &amp; Data Engineering</category>
      <category>Development</category>
      <category>article</category>
      <pubDate>Wed, 16 Sep 2026 11:00:00 GMT</pubDate>
      <guid>https://www.infoq.com/articles/next-dsl-author-language-model/?utm_campaign=infoq_content&amp;utm_source=infoq&amp;utm_medium=feed&amp;utm_term=articles</guid>
      <dc:creator>Irakli Betchvaia</dc:creator>
      <dc:date>2026-09-16T11:00:00Z</dc:date>
      <dc:identifier>/articles/next-dsl-author-language-model/en</dc:identifier>
    </item>
    <item>
      <title>Article: Implementing Durable Workflows on Postgres Without an External Orchestrator</title>
      <link>https://www.infoq.com/articles/durable-workflows-postgres/?utm_campaign=infoq_content&amp;utm_source=infoq&amp;utm_medium=feed&amp;utm_term=articles</link>
      <description>&lt;img src="https://res.infoq.com/articles/durable-workflows-postgres/en/headerimage/Implementing-Durable-Workflows-on-Postgres-Without-an-External-Orchestrator-header-1789129413946.jpg"/&gt;&lt;p&gt;Postgres can serve as the durable state store and coordination layer for workflows, eliminating the need for an external orchestrator. SKIP LOCKED enables concurrent work processing, primary-key checkpoints enforce idempotency, and leases support crash recovery. Workflow sleeps and human approvals can also be persisted as database state and survive restarts.&lt;/p&gt; &lt;i&gt;By Raman Varma&lt;/i&gt;</description>
      <category>Relational Databases</category>
      <category>Orchestration</category>
      <category>Postgres</category>
      <category>Queue</category>
      <category>Automation</category>
      <category>AI, ML &amp; Data Engineering</category>
      <category>Architecture &amp; Design</category>
      <category>article</category>
      <pubDate>Mon, 14 Sep 2026 11:00:00 GMT</pubDate>
      <guid>https://www.infoq.com/articles/durable-workflows-postgres/?utm_campaign=infoq_content&amp;utm_source=infoq&amp;utm_medium=feed&amp;utm_term=articles</guid>
      <dc:creator>Raman Varma</dc:creator>
      <dc:date>2026-09-14T11:00:00Z</dc:date>
      <dc:identifier>/articles/durable-workflows-postgres/en</dc:identifier>
    </item>
    <item>
      <title>Article: When Spec-Driven Development Pays off</title>
      <link>https://www.infoq.com/articles/when-spec-driven-development-pays-off/?utm_campaign=infoq_content&amp;utm_source=infoq&amp;utm_medium=feed&amp;utm_term=articles</link>
      <description>&lt;img src="https://res.infoq.com/articles/when-spec-driven-development-pays-off/en/smallimage/When-Spec-Driven-Development-Pays-Off-thumb-1788790605567.jpg"/&gt;&lt;p&gt;AI coding assistants have become a core part of software development. AI-generated code has shown productivity gains, but it's also contributing to security weaknesses and familiar bug patterns. In this article, author Nitin Garg highlights the bottleneck has moved from code generation to code verification, and how to detect &amp; mitigate it when the AI-generated behavior diverges from the intent.&lt;/p&gt; &lt;i&gt;By Nitin Garg&lt;/i&gt;</description>
      <category>AI Coding</category>
      <category>AI Assisted Coding</category>
      <category>Spec Driven Development</category>
      <category>Generative AI</category>
      <category>AI Development</category>
      <category>Artificial Intelligence</category>
      <category>AI, ML &amp; Data Engineering</category>
      <category>article</category>
      <pubDate>Thu, 10 Sep 2026 09:00:00 GMT</pubDate>
      <guid>https://www.infoq.com/articles/when-spec-driven-development-pays-off/?utm_campaign=infoq_content&amp;utm_source=infoq&amp;utm_medium=feed&amp;utm_term=articles</guid>
      <dc:creator>Nitin Garg</dc:creator>
      <dc:date>2026-09-10T09:00:00Z</dc:date>
      <dc:identifier>/articles/when-spec-driven-development-pays-off/en</dc:identifier>
    </item>
    <item>
      <title>Article: Implementing Chaos Engineering in Financial Payment Systems: Lessons from Enterprise ECS Deployments</title>
      <link>https://www.infoq.com/articles/chaos-engineering-ecs-payments/?utm_campaign=infoq_content&amp;utm_source=infoq&amp;utm_medium=feed&amp;utm_term=articles</link>
      <description>&lt;img src="https://res.infoq.com/articles/chaos-engineering-ecs-payments/en/headerimage/chaos-engineering-ecs-payments-header-1788254676411.jpg"/&gt;&lt;p&gt;Standard chaos engineering assumes experiments stop cleanly, blast radius is knowable in advance, and production is fair game. Payment systems violate all three. Salim Adedeji describes ECS-specific failure modes from enterprise deployments: a 60-second DNS TTL that produced 93-second failover, retry logic amplifying database load 2.4x, and AZ rebalancing loops that generic tooling misses.&lt;/p&gt; &lt;i&gt;By Salim Adedeji&lt;/i&gt;</description>
      <category>Containers</category>
      <category>Cloud</category>
      <category>Site Reliability Engineering</category>
      <category>Reliability</category>
      <category>Amazon Web Services</category>
      <category>Compliance</category>
      <category>Chaos Engineering</category>
      <category>Fault Tolerance</category>
      <category>Financial Applications</category>
      <category>DevOps</category>
      <category>Development</category>
      <category>Architecture &amp; Design</category>
      <category>article</category>
      <pubDate>Tue, 08 Sep 2026 09:00:00 GMT</pubDate>
      <guid>https://www.infoq.com/articles/chaos-engineering-ecs-payments/?utm_campaign=infoq_content&amp;utm_source=infoq&amp;utm_medium=feed&amp;utm_term=articles</guid>
      <dc:creator>Salim Adedeji</dc:creator>
      <dc:date>2026-09-08T09:00:00Z</dc:date>
      <dc:identifier>/articles/chaos-engineering-ecs-payments/en</dc:identifier>
    </item>
  </channel>
</rss>
