
  <rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
    <channel>
      <title>Motions Technologies Canada</title>
      <link>https://motionstechnologies.com/blog</link>
      <description>A blog created by Motions Technologies</description>
      <language>en-us</language>
      <managingEditor>jawad.arif@motionstechnologies.com (Motions Technologies)</managingEditor>
      <webMaster>jawad.arif@motionstechnologies.com (Motions Technologies)</webMaster>
      <lastBuildDate>Mon, 10 Aug 2026 00:00:00 GMT</lastBuildDate>
      <atom:link href="https://motionstechnologies.com/tags/kafka/feed.xml" rel="self" type="application/rss+xml"/>
      
  <item>
    <guid>https://motionstechnologies.com/blog/building-modern-marketplace-platforms</guid>
    <title>Building Modern Marketplace Platforms End-to-End: Frontend, Backend, Security, Retries, and Cloud Deployment</title>
    <link>https://motionstechnologies.com/blog/building-modern-marketplace-platforms</link>
    <description>A deep dive into how we design and ship platforms like UmaMeats—Next.js and mobile clients, Spring Boot microservices on ECS, DynamoDB, Redis GEO, Kafka with DLTs and outbox, Stripe payments and identity, CORS and auth hardening, and cost-aware deployment.</description>
    <pubDate>Mon, 10 Aug 2026 00:00:00 GMT</pubDate>
    <author>jawad.arif@motionstechnologies.com (Motions Technologies)</author>
    <category>Software Architecture</category><category>Microservices</category><category>Security</category><category>AWS</category><category>ECS</category><category>Next.js</category><category>Kafka</category><category>DynamoDB</category><category>Retry</category><category>DevOps</category>
  </item>

  <item>
    <guid>https://motionstechnologies.com/blog/delivery-orchestration-platform</guid>
    <title>Building a Delivery Orchestration Layer: Dispatch, GPS, and Ops</title>
    <link>https://motionstechnologies.com/blog/delivery-orchestration-platform</link>
    <description>Patterns for a delivery orchestration API: Redis GEO for driver presence, event-driven assignment, soft offers, and ops visibility—without overbuilding day one.</description>
    <pubDate>Sun, 02 Aug 2026 00:00:00 GMT</pubDate>
    <author>jawad.arif@motionstechnologies.com (Motions Technologies)</author>
    <category>Delivery</category><category>Redis</category><category>Kafka</category><category>Spring Boot</category><category>Architecture</category><category>GPS</category>
  </item>

  <item>
    <guid>https://motionstechnologies.com/blog/kafka-504-incident-postmortem</guid>
    <title>The 60-Second Coincidence: Anatomy of a 504 That Was Never the Broker&#39;s Fault</title>
    <link>https://motionstechnologies.com/blog/kafka-504-incident-postmortem</link>
    <description>A courier taps accept, waits, and gets HTTP 504. Isolating producer vs consumer vs broker, why 60 seconds is a fingerprint, and the DynamoDB putItem pattern that can wipe credentials on a hot path.</description>
    <pubDate>Thu, 13 Aug 2026 00:00:00 GMT</pubDate>
    <author>jawad.arif@motionstechnologies.com (Motions Technologies)</author>
    <category>Kafka</category><category>Incident Response</category><category>Spring Boot</category><category>AWS</category><category>ECS</category><category>DynamoDB</category><category>Observability</category>
  </item>

  <item>
    <guid>https://motionstechnologies.com/blog/kafka-production-hardening</guid>
    <title>Production Kafka for Order and Payment Events: Hardening What Actually Breaks</title>
    <link>https://motionstechnologies.com/blog/kafka-production-hardening</link>
    <description>Silent swallows, missing DLQs, dual-write gaps, and no idempotency: how we hardened Kafka producers and consumers for a real order/payment pipeline.</description>
    <pubDate>Tue, 04 Aug 2026 00:00:00 GMT</pubDate>
    <author>jawad.arif@motionstechnologies.com (Motions Technologies)</author>
    <category>Kafka</category><category>Spring Boot</category><category>Event-Driven</category><category>Observability</category><category>Microservices</category>
  </item>

    </channel>
  </rss>
