<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Microservices on AI VOID</title><link>https://ai-blog.noorshomelab.dev/categories/microservices/</link><description>Recent content in Microservices on AI VOID</description><generator>Hugo</generator><language>en</language><lastBuildDate>Sat, 14 Feb 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://ai-blog.noorshomelab.dev/categories/microservices/index.xml" rel="self" type="application/rss+xml"/><item><title>6. Message Brokers and Service Interactions: Kafka and Web Services</title><link>https://ai-blog.noorshomelab.dev/testcontainers-mastery-2026/06-message-brokers-kafka-web-services/</link><pubDate>Sat, 14 Feb 2026 00:00:00 +0000</pubDate><guid>https://ai-blog.noorshomelab.dev/testcontainers-mastery-2026/06-message-brokers-kafka-web-services/</guid><description>&lt;h2 id="introduction"&gt;Introduction&lt;/h2&gt;
&lt;p&gt;Welcome back, intrepid tester! In the previous chapters, you mastered the art of using Testcontainers to bring real databases into your tests. That was a huge step up from in-memory fakes, but what about the broader landscape of modern applications? Many microservices don&amp;rsquo;t just talk to databases; they communicate through message brokers, call other APIs, and integrate with external services.&lt;/p&gt;
&lt;p&gt;This chapter is your passport to confidently testing those complex interactions. We&amp;rsquo;re going to tackle two crucial areas:&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>GRPC with Node.js &amp;amp; Next.js: A Beginner&amp;#39;s Guide to High-Performance Microservices</title><link>https://ai-blog.noorshomelab.dev/guides/grpc-nodejs-nextjs-guide/</link><pubDate>Thu, 21 Aug 2025 00:00:00 +0000</pubDate><guid>https://ai-blog.noorshomelab.dev/guides/grpc-nodejs-nextjs-guide/</guid><description>&lt;h1 id="grpc-with-nodejs--nextjs-a-beginners-guide-to-high-performance-microservices"&gt;gRPC with Node.js &amp;amp; Next.js: A Beginner&amp;rsquo;s Guide to High-Performance Microservices&lt;/h1&gt;
&lt;p&gt;Welcome to this comprehensive guide on gRPC, specifically tailored for beginners looking to implement it with Node.js and Next.js. In today&amp;rsquo;s interconnected world, efficient communication between services is paramount. gRPC, a modern RPC framework developed by Google, offers a robust solution for building high-performance, language-agnostic microservices. This document will walk you through the fundamentals, core concepts, and practical applications of gRPC, empowering you to build scalable and efficient systems.&lt;/p&gt;</description></item></channel></rss>