<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>GraphQL on AI VOID</title><link>https://ai-blog.noorshomelab.dev/tags/graphql/</link><description>Recent content in GraphQL on AI VOID</description><generator>Hugo</generator><language>en</language><lastBuildDate>Wed, 11 Feb 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://ai-blog.noorshomelab.dev/tags/graphql/index.xml" rel="self" type="application/rss+xml"/><item><title>Chapter 10: GraphQL Client Integration and Concerns</title><link>https://ai-blog.noorshomelab.dev/angular-production-guide-2026/graphql-client-integration/</link><pubDate>Wed, 11 Feb 2026 00:00:00 +0000</pubDate><guid>https://ai-blog.noorshomelab.dev/angular-production-guide-2026/graphql-client-integration/</guid><description>&lt;h2 id="chapter-10-graphql-client-integration-and-concerns"&gt;Chapter 10: GraphQL Client Integration and Concerns&lt;/h2&gt;
&lt;p&gt;Welcome to Chapter 10! So far, we&amp;rsquo;ve explored many powerful HTTP networking patterns, leveraging Angular&amp;rsquo;s &lt;code&gt;HttpClient&lt;/code&gt; and &lt;code&gt;HttpInterceptor&lt;/code&gt;s for traditional REST APIs. But what if your backend speaks a different language, a more flexible and efficient one called GraphQL? In this chapter, we&amp;rsquo;re going to dive deep into integrating a GraphQL client into your standalone Angular application.&lt;/p&gt;
&lt;p&gt;GraphQL offers a paradigm shift in how frontend applications fetch data. Instead of multiple REST endpoints, you interact with a single endpoint, requesting precisely the data you need. This chapter will equip you with the knowledge to harness GraphQL&amp;rsquo;s power, allowing your Angular apps to communicate efficiently with modern backends. We&amp;rsquo;ll focus on the popular Apollo Client, learning how to query data, perform mutations, manage client-side cache, and handle authorization, all within the standalone Angular ecosystem.&lt;/p&gt;</description></item><item><title>Chapter 11: Server-Side API Security: REST, GraphQL, and Beyond</title><link>https://ai-blog.noorshomelab.dev/web-security-hacker-dev-2026/api-security-best-practices/</link><pubDate>Sun, 04 Jan 2026 00:00:00 +0000</pubDate><guid>https://ai-blog.noorshomelab.dev/web-security-hacker-dev-2026/api-security-best-practices/</guid><description>&lt;h2 id="introduction-guarding-the-gates-to-your-data"&gt;Introduction: Guarding the Gates to Your Data&lt;/h2&gt;
&lt;p&gt;Welcome back, future security champions! In our previous chapters, we laid the groundwork for understanding how attackers think and how to secure the frontend of your applications. We discussed securing client-side data, preventing common browser-based attacks like XSS and CSRF, and the basics of authentication.&lt;/p&gt;
&lt;p&gt;Now, it&amp;rsquo;s time to shift our focus to the beating heart of most modern web applications: the server-side API. Whether you&amp;rsquo;re building a RESTful service, a GraphQL endpoint, or something else entirely, your API is the critical gateway to your application&amp;rsquo;s data, business logic, and sensitive operations. A single vulnerability here can expose your entire system, leading to data breaches, service disruptions, and severe reputational damage.&lt;/p&gt;</description></item></channel></rss>