<rss version="2.0">
  <channel>
    <title>r-aem on superterran.net</title>
    <link>https://superterran.net/categories/r-aem/</link>
    <description></description>
    
    <language>en</language>
    
    <lastBuildDate>Thu, 08 May 2025 11:49:22 -0400</lastBuildDate>
    
    <item>
      <title></title>
      <link>https://superterran.net/2025/05/08/aem-is-dying-a-slow.html</link>
      <pubDate>Thu, 08 May 2025 11:49:22 -0400</pubDate>
      
      <guid>http://superterran.micro.blog/2025/05/08/aem-is-dying-a-slow.html</guid>
      <description>&lt;p&gt;AEM 6.5 is dying a slow but inevitable death, AEM as a Cloud Service will be around for many years to come but is not where Adobe is putting emphasis. Adobe sees the future of AEM as Edge Delivery Services (see &lt;a href=&#34;https://aem.live/&#34;&gt;aem.live&lt;/a&gt;) and Universal Editor (&lt;a href=&#34;https://experienceleague.adobe.com/en/docs/experience-manager-cloud-service/content/implementing/developing/universal-editor/page-editor-universal-editor&#34;&gt;experienceleague.adobe.com/en/docs/e&amp;hellip;&lt;/a&gt; which actually shows that Adobe is trying to reach parity with AEM Classic). They believe that customizations should migrate to Adobe Developer App Builder.&lt;/p&gt;
&lt;p&gt;I&amp;rsquo;ll say from an integrators perspective, the new world Adobe is pushing toward is a lot better in many respects, but AEM 6.5 and AEMaaCS deployments are inherently more fully baked and support a lot of enterprise use-cases that the new wave of technologies won&amp;rsquo;t for quite some time.&lt;/p&gt;
&lt;p&gt;I suspect, like with Adobe Commerce SaaS, that Adobe will eventually try and position the new technologies as the future of the platform and encourage everyone to adopt it wholesale, but like with AC SaaS, they truth is that it won&amp;rsquo;t be ready for five years for some use-cases, and enterprises who want/need tighter control will never switch, so the older offerings will probably never fully go away.&lt;/p&gt;
&lt;p&gt;&lt;a href=&#34;https://www.reddit.com/r/aem/comments/1khpzdn/comment/mr9hm5i/&#34;&gt;www.reddit.com/r/aem/com&amp;hellip;&lt;/a&gt;&lt;/p&gt;
</description>
    </item>
    
    <item>
      <title></title>
      <link>https://superterran.net/2025/01/07/its-worth-learning-because-it.html</link>
      <pubDate>Tue, 07 Jan 2025 15:31:43 -0400</pubDate>
      
      <guid>http://superterran.micro.blog/2025/01/07/its-worth-learning-because-it.html</guid>
      <description>&lt;p&gt;It&amp;rsquo;s worth learning because it will be in the market for the next decade, but Adobe believes Edge Delivery Services is the future of AEM and has actively started building that out and migrating customers to it. EDS with Universal Editor still expects AEM for content persistence so expertise is important in the foreseeable future even as they sunset it.&lt;/p&gt;
&lt;p&gt;The virtue of learning AEM is that it, in essence, is an Ingres to more modern headless development by way of SPAs, Universal Editor, and even EDS which is analogous to gitflow-driven static site generation while still giving you enough pain and frustration to teach you about traditional monolith development.&lt;/p&gt;
&lt;p&gt;There are probably easier paths, but I will say that agencies and businesses do not perceive the death of AEM as near, enterprises are still using it pretty heavily, and SKUs like AEM Guides which is internally facing will likely not go away anytime soon.&lt;/p&gt;
&lt;p&gt;&lt;a href=&#34;https://www.reddit.com/r/aem/comments/1hvxrue/comment/m5x7qno/&#34;&gt;www.reddit.com/r/aem/com&amp;hellip;&lt;/a&gt;&lt;/p&gt;
</description>
    </item>
    
  </channel>
</rss>