<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>API Gateway on AI VOID</title><link>https://ai-blog.noorshomelab.dev/tags/api-gateway/</link><description>Recent content in API Gateway on AI VOID</description><generator>Hugo</generator><language>en</language><lastBuildDate>Fri, 15 May 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://ai-blog.noorshomelab.dev/tags/api-gateway/index.xml" rel="self" type="application/rss+xml"/><item><title>Scaling with Reverse Proxies and API Gateways</title><link>https://ai-blog.noorshomelab.dev/systems-engineering-2026/reverse-proxies-api-gateways/</link><pubDate>Fri, 15 May 2026 00:00:00 +0000</pubDate><guid>https://ai-blog.noorshomelab.dev/systems-engineering-2026/reverse-proxies-api-gateways/</guid><description>&lt;p&gt;Imagine your application starts small, a single server humming along, directly serving every user request. What happens when users multiply by thousands, or even millions? Direct access quickly becomes a bottleneck, a security risk, and a nightmare to manage. This is where reverse proxies and API gateways step in, transforming a fragile single point into a robust, scalable entry for your entire system.&lt;/p&gt;
&lt;p&gt;In this chapter, we&amp;rsquo;ll peel back the layers of how modern systems handle inbound traffic, learning the timeless engineering principles behind reverse proxies and API gateways. You&amp;rsquo;ll understand not just &lt;em&gt;what&lt;/em&gt; these components are, but &lt;em&gt;why&lt;/em&gt; they are indispensable for building scalable, resilient, and secure architectures, especially in the context of distributed systems and emerging AI agent workflows. We&amp;rsquo;ll explore their core functionalities, their evolution, and how to think about integrating them into your designs without falling into the trap of over-engineering.&lt;/p&gt;</description></item><item><title>The User&amp;#39;s Journey: A High-Level Request Flow</title><link>https://ai-blog.noorshomelab.dev/netflix-internals-guide-2026-03-19/user-request-flow/</link><pubDate>Thu, 19 Mar 2026 00:00:00 +0000</pubDate><guid>https://ai-blog.noorshomelab.dev/netflix-internals-guide-2026-03-19/user-request-flow/</guid><description>&lt;h2 id="introduction"&gt;Introduction&lt;/h2&gt;
&lt;p&gt;Welcome to the second chapter of our deep dive into &amp;ldquo;How Netflix Works Internally.&amp;rdquo; Building upon our foundational understanding of distributed systems, this chapter will guide you through the initial, crucial stages of a user&amp;rsquo;s interaction with the Netflix platform. From the moment a user clicks play or browses for content on their device, we&amp;rsquo;ll trace the journey of their request through the intricate web of Netflix&amp;rsquo;s architecture.&lt;/p&gt;
&lt;p&gt;Understanding this high-level request flow is paramount for several reasons: it illuminates the principles of scalable and resilient system design, showcases how diverse components collaborate, and sets the stage for grasping more specific architectural patterns in subsequent chapters. By the end of this chapter, you&amp;rsquo;ll have a practical mental model of how Netflix efficiently serves millions of users globally, minimizing latency and maximizing availability.&lt;/p&gt;</description></item><item><title>Authentication, Authorization, and Identity Management</title><link>https://ai-blog.noorshomelab.dev/netflix-internals-guide-2026-03-19/auth-authz-identity/</link><pubDate>Thu, 19 Mar 2026 00:00:00 +0000</pubDate><guid>https://ai-blog.noorshomelab.dev/netflix-internals-guide-2026-03-19/auth-authz-identity/</guid><description>&lt;h2 id="introduction"&gt;Introduction&lt;/h2&gt;
&lt;p&gt;In a platform like Netflix, managing who can access what content and perform which actions is paramount. This chapter dives into the critical mechanisms of &lt;strong&gt;Authentication (AuthN)&lt;/strong&gt;, &lt;strong&gt;Authorization (AuthZ)&lt;/strong&gt;, and &lt;strong&gt;Identity Management (IAM)&lt;/strong&gt;. These are the bedrock of security, ensuring that only legitimate users access the service and only have permission to do what they&amp;rsquo;re supposed to, whether it&amp;rsquo;s streaming a movie, updating their profile, or managing payment information.&lt;/p&gt;</description></item><item><title>15. Project: API Gateway and Backend Testing with Node.js/TypeScript</title><link>https://ai-blog.noorshomelab.dev/testcontainers-mastery-2026/15-project-api-gateway-nodejs/</link><pubDate>Sat, 14 Feb 2026 00:00:00 +0000</pubDate><guid>https://ai-blog.noorshomelab.dev/testcontainers-mastery-2026/15-project-api-gateway-nodejs/</guid><description>&lt;h2 id="introduction"&gt;Introduction&lt;/h2&gt;
&lt;p&gt;Welcome back, intrepid developer! In our journey through Testcontainers, we&amp;rsquo;ve explored its core concepts, set up basic tests with various services, and understood the magic it performs to give us clean, isolated environments. Now, it&amp;rsquo;s time to put all that knowledge into practice with a realistic, multi-service project.&lt;/p&gt;
&lt;p&gt;In this chapter, we&amp;rsquo;ll build a simplified API Gateway and a backend service, both written in Node.js with TypeScript. The backend service will interact with a PostgreSQL database for persistence and a Redis cache for speed. Our mission? To craft robust integration tests for this entire stack using Testcontainers. This setup closely mimics common microservices architectures, giving you invaluable experience in tackling real-world testing challenges. We&amp;rsquo;ll ensure our tests are fast, reliable, and truly reflective of how these services will behave in production.&lt;/p&gt;</description></item><item><title>Chapter 15: Project: Deploying a Kiro-Managed Microservice</title><link>https://ai-blog.noorshomelab.dev/aws-kiro-mastery/project-microservice-deployment/</link><pubDate>Sat, 24 Jan 2026 00:00:00 +0000</pubDate><guid>https://ai-blog.noorshomelab.dev/aws-kiro-mastery/project-microservice-deployment/</guid><description>&lt;h2 id="chapter-15-project-deploying-a-kiro-managed-microservice"&gt;Chapter 15: Project: Deploying a Kiro-Managed Microservice&lt;/h2&gt;
&lt;p&gt;Welcome back, intrepid developer! In our journey through AWS Kiro, we&amp;rsquo;ve explored its core features, agentic capabilities, and how it can assist in code generation and testing. Now, it&amp;rsquo;s time to bring all that knowledge together for a truly impactful project: deploying a fully functional, Kiro-managed serverless microservice to the cloud.&lt;/p&gt;
&lt;p&gt;This chapter will guide you through the exciting process of using Kiro not just to write code, but to orchestrate its deployment. We&amp;rsquo;ll focus on a common, modern architecture – a serverless microservice using AWS Lambda and API Gateway – and demonstrate how Kiro can streamline the entire CI/CD pipeline, from infrastructure as code (IaC) generation to actual cloud deployment. By the end, you&amp;rsquo;ll have a running microservice and a deeper understanding of Kiro&amp;rsquo;s power in end-to-end development workflows.&lt;/p&gt;</description></item><item><title>17. Project 3: Deploying a Microservices Architecture</title><link>https://ai-blog.noorshomelab.dev/void-cloud-mastery-2026/project-microservices-architecture/</link><pubDate>Sat, 14 Mar 2026 00:00:00 +0000</pubDate><guid>https://ai-blog.noorshomelab.dev/void-cloud-mastery-2026/project-microservices-architecture/</guid><description>&lt;h2 id="introduction"&gt;Introduction&lt;/h2&gt;
&lt;p&gt;Welcome back, intrepid cloud architect! In our previous projects, we&amp;rsquo;ve built full-stack applications and standalone API services, mastering the fundamentals of Void Cloud deployment and configuration. Now, it&amp;rsquo;s time to tackle a more advanced, yet incredibly powerful, architectural pattern: &lt;strong&gt;Microservices&lt;/strong&gt;.&lt;/p&gt;
&lt;p&gt;Microservices represent a shift from monolithic applications (where all functionality resides in a single, large codebase) to a collection of small, independent services. Each service focuses on a single business capability, can be developed, deployed, and scaled independently, and communicates with other services through well-defined APIs. This approach offers significant benefits in terms of scalability, resilience, and development agility, especially for large and complex applications.&lt;/p&gt;</description></item><item><title>Chapter 20: Advanced Detection and Prevention Strategies</title><link>https://ai-blog.noorshomelab.dev/web-security-ethical-hacking-2026/advanced-detection-prevention/</link><pubDate>Sun, 04 Jan 2026 00:00:00 +0000</pubDate><guid>https://ai-blog.noorshomelab.dev/web-security-ethical-hacking-2026/advanced-detection-prevention/</guid><description>&lt;h2 id="introduction-building-an-impenetrable-fortress"&gt;Introduction: Building an Impenetrable Fortress&lt;/h2&gt;
&lt;p&gt;Welcome back, future security master! In our previous chapters, we&amp;rsquo;ve donned our hacker hats and explored the thrilling world of deep exploitation techniques. We&amp;rsquo;ve uncovered vulnerabilities from basic XSS to complex business logic flaws and API abuses. Now, it&amp;rsquo;s time to switch gears. Knowing how attackers think is the ultimate superpower for building robust defenses.&lt;/p&gt;
&lt;p&gt;This chapter is your deep dive into the art and science of &lt;strong&gt;advanced detection and prevention strategies&lt;/strong&gt;. We&amp;rsquo;re moving beyond simple patching to architecting systems that are inherently secure, resilient, and capable of identifying threats before they cause damage. Think of it as building an impenetrable fortress with multiple layers of defense, watchful guards, and automated alarm systems.&lt;/p&gt;</description></item></channel></rss>