<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Magento 2 on David Cajio | AWS, DevOps &amp; Platform Reliability</title><link>https://davidcajio.com/tags/magento-2/</link><description>Recent content in Magento 2 on David Cajio | AWS, DevOps &amp; Platform Reliability</description><generator>Hugo -- gohugo.io</generator><language>en-us</language><copyright>© 2026 David Cajio</copyright><lastBuildDate>Mon, 06 Jul 2026 08:00:00 -0400</lastBuildDate><atom:link href="https://davidcajio.com/tags/magento-2/index.xml" rel="self" type="application/rss+xml"/><item><title>Why Queues Belong Between Systems That Don’t Fail the Same Way</title><link>https://davidcajio.com/posts/why-queues-belong-between-systems-that-dont-fail-the-same-way/</link><pubDate>Mon, 06 Jul 2026 08:00:00 -0400</pubDate><guid>https://davidcajio.com/posts/why-queues-belong-between-systems-that-dont-fail-the-same-way/</guid><description>When SAP, Magento, WMS, and AfterShip all participate in the same order lifecycle, direct integrations become fragile fast. This post explains why AWS SQS FIFO queues belong between systems that fail differently, using real e-commerce flows like offline orders, order export, tracking updates, retries, bad data, dead-letter queues, and idempotent consumers.</description><media:content xmlns:media="http://search.yahoo.com/mrss/" url="https://davidcajio.com/posts/why-queues-belong-between-systems-that-dont-fail-the-same-way/feature.jpg"/></item><item><title>Practical Multi-Region E-Commerce Architecture on AWS (Without Overengineering It)</title><link>https://davidcajio.com/posts/aws-multi-region-ecommerce-architecture-practical-guide/</link><pubDate>Mon, 01 Jun 2026 13:46:15 -0400</pubDate><guid>https://davidcajio.com/posts/aws-multi-region-ecommerce-architecture-practical-guide/</guid><description>&lt;p&gt;When most people talk about multi-region architectures, they immediately jump to diagrams full of globally distributed databases, active-active replication, service meshes, and enough complexity to require a dedicated platform team.&lt;/p&gt;</description><media:content xmlns:media="http://search.yahoo.com/mrss/" url="https://davidcajio.com/posts/aws-multi-region-ecommerce-architecture-practical-guide/feature.jpg"/></item></channel></rss>