
  <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>Sun, 02 Aug 2026 00:00:00 GMT</lastBuildDate>
      <atom:link href="https://motionstechnologies.com/tags/gps/feed.xml" rel="self" type="application/rss+xml"/>
      
  <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>

    </channel>
  </rss>
