<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Vrithika Mendon on Medium]]></title>
        <description><![CDATA[Stories by Vrithika Mendon on Medium]]></description>
        <link>https://medium.com/@vmendonvrithika?source=rss-43137bc3269b------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*TlN1JaEPA6uv1hIovlDveg.jpeg</url>
            <title>Stories by Vrithika Mendon on Medium</title>
            <link>https://medium.com/@vmendonvrithika?source=rss-43137bc3269b------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Thu, 19 Nov 2026 20:22:11 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@vmendonvrithika/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Why AEM Edge Delivery Service Doesn’t Need a Publish Tier And Why That’s Brilliant]]></title>
            <link>https://medium.com/@vmendonvrithika/why-aem-edge-delivery-service-doesnt-need-a-publish-tier-and-why-that-s-brilliant-6b6b256d5166?source=rss-43137bc3269b------2</link>
            <guid isPermaLink="false">https://medium.com/p/6b6b256d5166</guid>
            <category><![CDATA[aem]]></category>
            <category><![CDATA[adobe-experience-manager]]></category>
            <category><![CDATA[website-performance]]></category>
            <category><![CDATA[edge-delivery-services]]></category>
            <category><![CDATA[adobe-experience-cloud]]></category>
            <dc:creator><![CDATA[Vrithika Mendon]]></dc:creator>
            <pubDate>Sun, 07 Sep 2025 17:22:42 GMT</pubDate>
            <atom:updated>2025-09-07T17:22:42.110Z</atom:updated>
            <content:encoded><![CDATA[<h3>What Was the Publish Tier, Anyway?</h3><p>In traditional AEM setups, content delivery followed a pretty standard path:</p><ol><li>Authors created content in the authoring environment.</li><li>That content was then “activated” to the publish tier.</li><li>The publish tier rendered the content for users.</li><li>A dispatcher served it through a CDN.</li></ol><p>This setup worked well for a long time. It gave teams control over what went live and when.</p><h3>How AEM EDS Delivers Without a Publish Tier</h3><p>So, if there’s no publish tier in AEM Edge Delivery Services (EDS), how does content actually get delivered?</p><p>AEM EDS is built around three core services (microservices architecture) called “buses” that handle different parts of the content delivery process:</p><ul><li>Content Bus: This is where structured content lives. Think of it as the organised storage for everything from page metadata to block data.</li><li>Code Bus: This holds the logic for how content is rendered in HTML templates, CSS styles, JavaScript behaviours. Developers commit this code to GitHub, and it’s used to transform raw content into web-ready pages.</li><li>Media Bus: This handles images, videos, and other media assets, optimising them for fast delivery.</li></ul><p>Together, these buses replace the traditional publish tier by handling everything that used to happen there just in a more distributed and scalable way.</p><h3>How Content Flows Without a Publish Tier</h3><p>Whether you’re writing in Word, Google Docs, or using AEM’s Universal Editor, let us understand how content flows through AEM Edge Delivery Services</p><p>It all starts with authoring.<br>You can create content in familiar tools like Word or Google Docs, or directly inside AEM using the Universal Editor. The key difference is where that content lives and how it gets transformed.</p><ul><li>For document-based authoring, your content is stored in a shared drive or synced to GitHub.</li><li>For Universal Editor, the content is saved in AEM’s internal repository.</li></ul><p>How is this content tied to code ?</p><p>A GitHub bot keeps an eye on changes. When you update a document or publish a page, it kicks off a process that transforms your content into static HTML, CSS, and JS, the stuff browsers actually need to display your page.</p><p>For Universal Editor content, there’s a config file called fstab.yaml that acts like a map. It tells the system which GitHub block (i.e., rendering logic) to use for each piece of content. This way, even though the content lives in AEM, it’s still rendered using the GitHub-hosted code.</p><h3>Coming to Why that’s Brilliant</h3><h3>It is Fast, Like Really Fast</h3><p>Since content is pre-rendered and cached at the edge (on CDN nodes like Fastly or Akamai), pages load in milliseconds. There’s no waiting for a publish server to do its thing. The closest edge server already has your content ready to go, so users get what they need, instantly.</p><h3>Simplicity</h3><p>With EDS, the delivery pipeline is clean and automated. Content updates flow through GitHub, get transformed, and are deployed without needing to monitor infrastructure or clear caches manually.</p><h3>Scalability</h3><p>Because content is served from edge nodes, the system scales automatically. You don’t need to provision extra servers or worry about backend performance. The CDN takes care of it, so your site stays fast and reliable even when things get busy.</p><h3>Secure by Default</h3><p>There’s no exposed backend server in the delivery path. Everything is served from secure, globally distributed edge nodes. That means fewer vulnerabilities and built-in protection like WAF and DDoS.</p><p>This brilliance empowers marketers to iterate faster, developers to build autonomously, and businesses to deliver high-performance experiences with minimal overhead.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6b6b256d5166" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Beyond Hosting: Why AEM Cloud Service Isn’t Just Managed Services in the Cloud]]></title>
            <link>https://medium.com/@vmendonvrithika/beyond-hosting-why-aem-cloud-service-isnt-just-managed-services-in-the-cloud-48684e02e41d?source=rss-43137bc3269b------2</link>
            <guid isPermaLink="false">https://medium.com/p/48684e02e41d</guid>
            <category><![CDATA[edge-delivery-services]]></category>
            <category><![CDATA[adobe]]></category>
            <category><![CDATA[adobe-experience-manager]]></category>
            <category><![CDATA[cloud-services]]></category>
            <category><![CDATA[content-management-system]]></category>
            <dc:creator><![CDATA[Vrithika Mendon]]></dc:creator>
            <pubDate>Sun, 17 Aug 2025 10:11:11 GMT</pubDate>
            <atom:updated>2025-08-17T10:11:11.005Z</atom:updated>
            <content:encoded><![CDATA[<p>Adobe Experience Manager (AEM) is one of the most powerful digital experience platforms in the market today. AEM enables brands to deliver personalised, content-rich experiences across web, mobile, and emerging channels.</p><p>But as organisations move to the cloud, a critical question arises:</p><p><strong><em>What does “AEM on the cloud” really mean?</em></strong></p><p>It’s a question I hear often. Many assume that AEM Managed Services (AMS) and AEM Cloud Service (AEMaaCS) are simply two flavours of the same cloud offering. <br>After all, both are hosted on Adobe’s infrastructure. <br>Yet, beneath the surface lies a fundamental <strong>architectural divide</strong>, <br>one that shapes how teams build, deploy, and innovate.</p><p>Here, we’ll go beyond hosting and explore why architecture and deployment models make all the difference.</p><h3>Cloud Hosted</h3><p>AEM MS is essentially a lift-and-shift of the traditional on-premise AEM setup. It runs on virtual machines (VMs), with dedicated environments for authoring, publishing, and dispatching. While Adobe manages the infrastructure, customers still handle deployments, upgrades, and patches manually. It’s cloud-hosted, but not cloud-native.</p><p>While it runs on Adobe’s cloud infrastructure, its design remains monolithic meaning all core services (authoring, publishing, dispatching) are tightly coupled and deployed as a single unit on virtual machines (VMs).</p><h4>VM-Based Monolithic Setup</h4><p>AEM MS environments are provisioned as dedicated VMs, each hosting a full stack of AEM services. These include:</p><ul><li>Author and Publish tiers running on separate VMs.</li><li>Dispatcher and Web servers manually configured.</li><li>Load balancers managing traffic across static environments</li></ul><h4>Manual Scaling and Patching</h4><p>Unlike AEM Cloud Service, AEM MS does not auto-scale. If traffic spikes, IT teams must manually add capacity. Similarly, patches and upgrades are scheduled and executed manually, often requiring downtime or maintenance windows.</p><h4>Mutable Infrastructure</h4><p>AEM MS is a mutable system, meaning infrastructure can be changed post-deployment. This contrasts with AEM Cloud Service’s immutable model, where environments are rebuilt and replaced rather than modified.</p><p>Mutable infrastructure allows quick fixes but lacks the consistency, reliability, and automation of cloud-native platforms.</p><h3><strong>Cloud Native</strong></h3><p>On the other hand, AEMaaCS is built from the ground up as a cloud-native platform. It uses microservices, containers, and auto-scaling to deliver a modern, agile experience. Updates are continuous, environments are immutable, and deployments are automated through Cloud Manager. There’s no SSH access or manual patching. It is a streamlined DevOps-driven delivery.</p><h4>Microservices Architecture</h4><p>AEMaaCS is a microservices-based architecture. Instead of bundling all services into a single unit, AEMaaCS breaks them down into independent, containerised components, each responsible for a specific function like authoring, publishing, asset processing, or workflow execution.</p><p>This modularity allows:</p><ul><li>Faster updates and isolated deployments.</li><li>If one service fails, others continue running.</li><li>Easier scaling and resource optimisation.</li></ul><h4>Auto-Scaling</h4><p>AEMaaCS is designed to scale automatically based on traffic and usage patterns. Whether you’re launching a campaign or handling a seasonal spike, the platform adjusts resources dynamically with no manual provisioning required.</p><p>And if something goes wrong? The system is self-healing. Containers restart automatically, and services recover without human intervention. This ensures high availability and performance, even under pressure.</p><h4>How Redundancy Works</h4><ul><li>Redundant containers are deployed across multiple zones or nodes.</li><li>A load balancer sits in front of these instances and routes traffic based on health checks and availability.</li><li>If an instance becomes unhealthy (e.g. crashes, slows down), the load balancer automatically reroutes traffic to healthy instances.</li><li>Meanwhile, the orchestration layer (like Kubernetes) replaces the failed container with a fresh one, this is the self-healing mechanism.</li></ul><h3>Immutable Infrastructure</h3><p>Unlike AEM MS, where you can SSH into servers and tweak configurations, AEMaaCS follows an immutable infrastructure model. You don’t modify live environments, you replace them.</p><p>Every deployment is a fresh container image, built and validated through Cloud Manager, Adobe’s CI/CD pipeline. This guarantees:</p><ul><li>Consistency across environments.</li><li>Reduced risk of configuration drift.</li><li>Simplified rollback and recovery.</li></ul><h3>So remember, both AEM MS and AEMaaCS are cloud-hosted, but only one is cloud-native.</h3><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=48684e02e41d" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Adobe GenStudio for Performance Marketing vs.]]></title>
            <link>https://medium.com/@vmendonvrithika/adobe-genstudio-for-performance-marketing-vs-dedfde475c9d?source=rss-43137bc3269b------2</link>
            <guid isPermaLink="false">https://medium.com/p/dedfde475c9d</guid>
            <category><![CDATA[performance-marketing]]></category>
            <category><![CDATA[content-marketing]]></category>
            <category><![CDATA[adobe]]></category>
            <dc:creator><![CDATA[Vrithika Mendon]]></dc:creator>
            <pubDate>Sun, 10 Aug 2025 17:37:08 GMT</pubDate>
            <atom:updated>2025-08-10T17:37:08.962Z</atom:updated>
            <content:encoded><![CDATA[<h3>Adobe GenStudio for Performance Marketing vs. Analytics: What Marketers Need to Know About the Difference</h3><h3><em>“If I already have Adobe Analytics, why do I need insights from GenStudio </em>for Performance Marketing<em>?”</em></h3><p>It’s a fair question and one that many marketers ask. <br>On the surface, both tools offer performance data. If you dig deeper, you’ll find they serve <strong>very different purposes</strong>, built for <strong>different teams</strong>, and optimized for <strong>different decisions.</strong></p><h3>Let’s start with the basics:</h3><ul><li><strong>Adobe Analytics</strong> is built to track <strong>user behavior</strong> across owned channels like websites and apps. It helps you understand how users navigate, where they drop off, and what actions they take.</li><li><strong>Adobe GenStudio for Performance Marketing</strong>, on the other hand, is designed to track <strong>creative performance</strong> across paid media platforms like Meta and Google CM360. It tells you which ad variant worked best, why it worked, and what to do next.</li></ul><h3>Here’s how the difference plays out in practice:</h3><ul><li><strong>Adobe Analytics might tell you</strong>:</li></ul><p>“Users from Mumbai spent 2.3 minutes on the landing page.”</p><ul><li><strong>Adobe GenStudio for Performance Marketing can tell you</strong>:</li></ul><p>“Which version of the Ad performed best on Instagram Reels for Gen Z in Bengaluru?”</p><h3><strong>How Detailed the Insights Are</strong></h3><p>GenStudio for Performance Marketing<strong> </strong>gives you <strong>creative level insights</strong> on how each image, headline, or a format performs across channels.</p><p>This means GenStudio for Performance Marketing can:</p><ul><li>Score creative variants based on performance</li><li>Identify which visual or copy elements drive engagement</li></ul><h3>Another key difference is <strong>how fast you get these insights</strong></h3><ul><li><strong>Adobe Analytics</strong> often requires custom dashboards and post-campaign analysis.</li><li><strong>GenStudio for Performance Marketing </strong>delivers <strong>near real-time feedback</strong> and <strong>AI-generated recommendations</strong> directly in the creative workflow.</li></ul><h3><strong>Where does the Data Come From</strong></h3><p>Adobe GenStudio for Performance Marketing connects directly to <strong>paid media platforms</strong> via authenticated APIs. It ingests:</p><ul><li>Campaign-level metrics (CTR, CPA, spend)</li><li>Creative-level performance (variant scoring, media attributes)</li><li>Attribute-level insights (copy tone, visual style, format effectiveness)</li></ul><h3><strong>Why Marketers Need Both</strong></h3><ul><li><strong>Adobe Analytics helps you understand what users do.</strong></li><li>Adobe GenStudio for Performance Marketing <strong>helps you influence what they do through better creative.</strong></li></ul><p>So the next time someone asks,</p><p>“If I already have Adobe Analytics, why do I need GenStudio for Performance Marketing?”<br> You’ll know the answer</p><p>Because knowing what happened isn’t enough. You need to know what worked and what to do next.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=dedfde475c9d" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[CDN or Something More? Demystifying Adobe Edge Delivery Services]]></title>
            <link>https://medium.com/@vmendonvrithika/cdn-or-something-more-demystifying-adobe-edge-delivery-services-a38b7f28f2f1?source=rss-43137bc3269b------2</link>
            <guid isPermaLink="false">https://medium.com/p/a38b7f28f2f1</guid>
            <category><![CDATA[adobe-experience-manager]]></category>
            <category><![CDATA[martech-stack]]></category>
            <category><![CDATA[content-management-system]]></category>
            <category><![CDATA[edge-delivery-services]]></category>
            <category><![CDATA[martech]]></category>
            <dc:creator><![CDATA[Vrithika Mendon]]></dc:creator>
            <pubDate>Fri, 01 Aug 2025 16:30:30 GMT</pubDate>
            <atom:updated>2025-08-01T16:30:30.161Z</atom:updated>
            <content:encoded><![CDATA[<p>Isn’t EDS just Adobe’s version of a CDN?</p><p>This question comes up so often and understandably so. On the surface, Adobe’s Edge Delivery Services (EDS) might <em>look</em> like just another content delivery network</p><p>It’s an easy mix-up to make after all, both Edge Delivery Services (EDS) and traditional CDNs operate at the edge, focus on performance, and rely heavily on caching to speed up content delivery. They both promise faster load times, better scalability, and improved user experiences. So on the surface, they seem interchangeable. But that’s where the similarities end !</p><h4><strong>What is a CDN, Really?</strong></h4><ul><li>Distributes static content (images, JS, CSS) across global edge servers.</li><li>Reduces latency by serving content from the nearest location.</li><li>Examples: Akamai, Cloudflare, Fastly.</li></ul><p>CDNs cache and serve, but don’t personalize or manage content.</p><h4><strong>What is AEM Edge Delivery Services (EDS)?</strong></h4><p>Think of EDS as a web delivery framework.</p><p>EDS focuses on the entire lifecycle of content delivery, from authoring and publishing to rendering and personalization.</p><p>Here’s what sets EDS apart:</p><p><strong>Authoring-first, Developer-light:</strong></p><ul><li>Both AEMaaCS and EDS allow marketers to create and manage content without needing developers. However, with EDS marketers can also update web pages using tools they already know, like Microsoft Word or Google Docs.</li></ul><p><strong>Edge-native Rendering:</strong></p><ul><li>Unlike CDNs that just cache and serve, EDS renders pages at the edge.<br>This means the content, layout, and design are all assembled instantly on a nearby server, so the page loads much faster.</li><li>This is possible using lightweight, pre built templates so users see it faster, it performs better on metrics like Core Web Vitals, and it looks great on any device.</li><li>Developers create these templates once, defining how different types of content (like headlines, images, buttons) should look and behave.</li><li>They’re lightweight because they’re stripped of unnecessary code.</li><li>They’re ready-to-go because they don’t need to be rebuilt every time they’re reused across pages and rendered quickly at the edge.</li></ul><p><strong>Built for AEM, but not limited to it:</strong></p><ul><li>EDS integrates deeply with Adobe Experience Manager (AEM), but it’s also flexible enough to work with headless CMSs, commerce platforms, and other sources of content.</li></ul><p><strong>Performance + Personalization:</strong></p><ul><li>EDS doesn’t just deliver content fast, it delivers the <em>right</em> content. It supports personalization and experimentation at the edge, so brands can tailor experiences without sacrificing speed.</li><li>Traditional personalization often happens after the page loads using JavaScript in the browser or server-side logic that can slow things down. EDS flips that model by doing it before the page even reaches the user.</li></ul><p>When someone visits a site, EDS can detect key signals like:</p><ul><li>Location (based on IP)</li><li>Device type (mobile, desktop)</li><li>Language preferences</li><li>Cookies or identifiers (e.g., returning visitor, logged-in user)</li></ul><p>These rules are defined in the codebase (typically in GitHub) and executed at the edge during page rendering.</p><p>Based on these signals, EDS uses lightweight logic at the edge to decide <em>which version</em> of the content to serve. This could mean:</p><ul><li>Showing a different banner to a user in Mumbai vs. one in Singapore</li><li>Displaying a personalized call-to-action for returning visitors</li></ul><p><strong>Modern DevOps Optional:</strong></p><ul><li>Developers can build, customize, and extend site functionality using GitHub workflows.</li></ul><p><strong>You may ask how ?</strong><br>Developers write and manage code (templates, logic, styling) in a GitHub repository just like they would for any modern web project.</p><p>When a developer commits a change (e.g., updates a template or adds a new feature), a GitHub Action is triggered. This action automatically builds the site and prepares it for deployment.</p><p>EDS takes the built output and deploys it directly to Adobe’s global edge network</p><p>The updated site is now live and optimized across all edge locations, ready to serve users with the latest content and functionality.</p><h3>When to use a Content Delivery Network</h3><ul><li>You already have a traditional CMS or static site and just want to speed up delivery of static assets (images, CSS, JS).</li><li>Your site doesn’t require frequent updates or real-time personalization.</li><li>You’re optimizing performance but not rethinking your authoring or delivery model.</li></ul><h3>When to Use AEM Edge Delivery Services (EDS)</h3><ul><li>You want ultra-fast, personalized experiences delivered directly from the edge.</li><li>Your marketing team needs to publish content quickly using tools like Word or Google Docs without waiting on developers.</li><li>You want to simplify DevOps with GitHub-based workflows and minimal infrastructure.</li><li>You’re aiming for better Core Web Vitals, SEO, and mobile performance.</li><li>You need to scale globally with personalization and experimentation built in.</li></ul><p><strong>EDS isn’t a replacement for a CDN</strong></p><p>EDS is Adobe’s answer to the need for speed, scale, and smarter delivery. It’s about crafting experiences that are fast, flexible, and future-ready !</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a38b7f28f2f1" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>