DEV Community: Rafael Corrêa Gomes

Why Brands Join (and Leave) Shopify?

Rafael Corrêa Gomes — Tue, 12 Aug 2025 21:05:32 +0000

Over the last 16 years working with e-commerce, I have been involved in hundreds of conversations with brands that were evaluating Shopify. I have seen it from both sides. I have helped merchants successfully launch on Shopify, and I have also worked with those who decided to leave it for another platform. This article is not based on theory. These points come directly from my work with global brands and my experience leading projects in North America, Europe, and Latin America.

The reasons why brands join and leave Shopify are very different, but both are deeply connected to business realities, not just technical features.

Why Brands Join Shopify

One of the main drivers is the reduction in total cost of ownership and technical debt. For many brands, the savings are visible almost from day one. The infrastructure, hosting, and core platform maintenance are part of the package, which means the business can focus on growth rather than servers, patches, and complex deployments.

Another strong reason is autonomy. Shopify’s app ecosystem is massive, with more than ten thousand apps ready to install and use. In many cases, a merchant can add new capabilities without engaging a development team or writing a single line of code. That is powerful when time to market matters.

The third point I consistently hear from merchants is about innovation. Shopify delivers new features regularly and often integrates the latest market advances directly into the platform. This ranges from AI-driven features to SEO best practices and updated compliance tools. For a brand that wants to stay competitive without building everything from scratch, this is a significant advantage.

Why Brands Leave Shopify

On the other side, some brands decide to leave. In many cases, the trigger is the platform’s variable fees. For businesses with very low product margins, the costs of Shopify Plus or the additional fees when not using Shopify Payments can noticeably impact profitability.

Another scenario is when the project requires too many customizations. Shopify can handle complex needs, but at a certain point, the level of custom work increases the total cost of ownership. It also creates operational complexity, and sometimes merchants start questioning whether the initial promise of simplicity still holds.

Finally, there is the matter of platform policies and roadmap. Shopify is a SaaS product with its own rules and priorities. Certain restricted items and features are prohibited due to policy, while strategic decisions depend entirely on Shopify’s roadmap. For some brands, that level of dependency feels too limiting, especially when they want complete control of their infrastructure and features.

My Take on the Market

In my experience, brands do not leave Shopify because it fails them. They leave because their business model evolves in a direction where the trade-offs of staying no longer make sense. Sometimes it is a margin problem. Sometimes it is a complexity problem. Sometimes it is a control problem.

At the same time, I have seen many brands that could have stayed on Shopify if they had approached the platform with a clearer understanding of its strengths and boundaries. The key is to align business goals with platform capabilities from the beginning. When that alignment exists, Shopify can scale impressively. When it does not, the conversation about replatforming often starts sooner than expected.

As someone who works daily with Shopify, Adobe Commerce, and other platforms, my advice is to look beyond features and focus on the long-term cost, agility, and control you will need. These are the real decision points that determine whether a brand thrives on Shopify or eventually decides to move on.

The strategy evolves when the platform changes

Rafael Corrêa Gomes — Sat, 05 Jul 2025 22:29:17 +0000

Looking back, I’ve seen many merchants and partners go through the journey from Magento 1 to Magento 2 (Adobe Commerce), including myself. Now, we’re entering the next evolution, Adobe Commerce as a Cloud Service (ACCS).

Each wave of change brought something new, but also taught us something valuable. And while it’s tempting to compare these transitions as just “technical upgrades,” the reality is that each one reshapes how we think and build ecommerce solutions.

The Migration Journey (M1 to M2)

When Magento 2 launched, it came with real improvements, better performance, modern APIs, stronger security, a new SLA for support, and security compliance from Adobe. However, it wasn’t an overnight switch, mainly because we could leverage the upgrade opportunity to revisit some implementation points and reduce costs, while also improving speed and efficiency.

So at that time, we redesigned stores with the new accessibility compliance in mind. Revisited the architecture diagram. Clean up the data to migrate. And for sure, we evaluated the customizations requested over the years, to make sure we maintain the most valuable ones, and drop the ones with lower ROI.

The good news? The core tech stack remained familiar. PHP, MySQL, and XML still formed the foundation, and that helped developers keep going while adapting over time.

That's when I started to create open-source tools to help developers code on Magento 2, 10 years ago, tools aiming VSCode, Docker, Translation, Magento 2 UI, Deploy, Terminal, Atom. Tools that had more than 500k downloads and hundreds of contributions.

Some merchants got help from agencies. Others figured things out on their own. But almost everyone went through a phase of evaluating and learning the value of migrating to Magento 2 as they scaled.

A Different Kind of Transition (Going to Saas)

Now, as we move to Adobe Commerce SaaS, where merchants are aiming to use AI, improve how autonomous their teams are, and aim for a lower TCO, maintaining the customizations that really matter, with high ROI, so the change is different.

"It’s not just about code. It’s about strategy."

Instead of rebuilding everything, the most successful brands during this migration will:

Minimize migrating customizations with lower ROI
Redesign only what truly matters for Saas architecture
Rethink data models to be lean and efficient
Use native SaaS services like App Builder, API Mesh, and Edge Delivery
Build progressively, starting with landing pages and key funnels before tackling checkout or custom logic
Use my new AI open-source tool, Adobe Commerce Dev MCP 😉

Here you can see a diagram I've created to show the 10 main steps during the migration.

10 steps to migrate your Adobe Commerce Cloud to ACCS
Adobe Commerce Saas migration process
The biggest shift? You don’t have to do all the heavy lifting alone. ACCS is designed to remove complexity from your e-commerce platform. Therefore, it's essential to ensure that you don't introduce extra complexity into your customization layer (App Builders and middleware).

And while the tooling and APIs are important, what really matters is a mindset shift for key decision makers, from on-premises to Saas architecture.

This Time, Strategy Beats Manual Work

Going to ACCS (Adobe Commerce as a Cloud Service) is not about copying your existing architecture line by line. It’s about deciding what should evolve and where Saas can carry the weight for you, to better leverage the migration benefits.

You can gradually phase your migration, optimize where it matters most, and benefit from:

Lower total cost of ownership
Faster go-to-market timelines
Future-proof services backed by Adobe

To visualize the changes, here you have a simplified diagram showing the main areas we need to think about.

Changes when migrating to Adobe Commerce as a Cloud Service
Migration to ACCS
They help break down the process into manageable phases, while reinforcing the message Adobe shares:

you don’t need to rush — you need to be intentional

If you’re starting to plan your move to ACCS, my advice is simple, long story short:

✅ Focus on business outcomes

✅ Let go of unnecessary complexity

✅ Work with a straightforward migration strategy, not just a task list

This is not just an upgrade. It’s your chance to start using the latest technologies to optimize your work and reduce costs.

Happy to chat if you’re on this journey!

Why I Built an Adobe Commerce Dev MCP Server and How It Can Help You Code Faster

Rafael Corrêa Gomes — Tue, 03 Jun 2025 18:29:35 +0000

As someone leading both Adobe Commerce and Shopify practices at Valtech, I spend a good portion of my personal time experimenting with new tools, writing proof of concepts, and exploring how emerging technologies work. One pattern I’ve observed is how platforms like Shopify and CommerceTools have been paving the way with Model Context Protocol (MCP) servers—unlocking smoother AI-assisted development with tools like Cursor and Claude.

Yet, for Adobe Commerce developers, a clear gap existed.

There was no open-source MCP server tailored to the Adobe Commerce GraphQL APIs—no way to validate, autocomplete, or generate code in real time using AI based on the latest schema definitions.

That’s what motivated me to build the Adobe Commerce Dev MCP Server.

What Is It?

It’s an open-source MCP Server built specifically for Adobe Commerce. It helps devs code faster and smarter by enabling AI-powered tools to understand the context of Adobe Commerce’s GraphQL schema.

It’s now publicly listed on:

I’ve also published a quick YouTube demo showing how to set it up and use it.

⸻

Use Cases

🎯 Accelerate Adobe Commerce integrations
Code generation and autocompletion are aligned with the latest GraphQL APIs, directly inside AI-powered dev environments like Cursor.

🔍 Troubleshoot smarter
Identify deprecated fields or required inputs in mutations and queries—without digging through outdated docs.

✨ Create a better coding experience
Modernize how we work with Adobe Commerce. Let’s bring some of that “good vibe” experience from other ecosystems into Magento/Adobe Commerce.

⸻

What’s New in the Latest Version?

Hosted on Vercel for instant usage, no local setup required
Video tutorial included for easy onboarding
Now listed in major MCP directories for AI dev tools

⸻

Let’s Build Together

This project began as a personal proof of concept, but with over 150 downloads and growing interest, I’m excited to see where the community can take it. If you’re working with Adobe Commerce, I’d love your feedback, suggestions—or even better—your contributions.

Special thanks to early users for the feedback that helped shape this release.

A Comprehensive Guide for CTOs: Adobe Commerce SaaS vs Shopify

Rafael Corrêa Gomes — Tue, 03 Jun 2025 18:11:15 +0000

In today's fast-paced business world, choosing the right e-commerce platform can make all the difference. For CTOs, the decision between Adobe Commerce as a cloud service and Shopify can be overwhelming. This blog post aims to provide an in-depth analysis of these two platforms, focusing on key considerations businesses must evaluate to make informed technical and business decisions.

Introduction

Hello everyone. Today, we're diving into a critical comparison for CTOs: Shopify versus Adobe Commerce as a cloud service. We'll explore essential factors related to business and technical choices necessary for selecting the right platform. With years of experience, I've identified four main pillars to consider, offering a clear view of each platform's position in terms of business analysis.

Identifying the Four Main Pillars

Strict and Complex Requirements

The first pillar involves strict and complex requirements. When a platform needs to be tailored precisely to customer and business needs—such as integrating custom CRM, marketing tools, or ERP systems—strict requirements come into play. These cannot be easily altered, necessitating careful modeling and planning.

TCO and Flexibility

On the right side, we have the Total Cost of Ownership (TCO) and flexibility. TCO increases with customization, as the more flexible a platform is, the more it can be tailored, but at a higher cost. Understanding which components to build from scratch is crucial, as maintaining these custom elements will be your responsibility on either platform.

Faster ROI and Time to Market

On the left, we examine faster ROI and time to market. Moving in this direction allows for rapid platform launch, resulting in a quicker return on investment. Minimal initial investment makes this option appealing for many businesses.

Flexible Business Requirements

Lastly, considering flexible business requirements means adapting your business to the platform, rather than the other way around. By using market best practices and existing tools, businesses can streamline operations and processes, leading to faster time to market and ROI.

Platform Deep Dive

Shopify Basic to Advanced

Shopify’s basic and advanced options offer the fastest way to go live. With no contract required on Shopify Plus, you can create your own store independently, making this a flexible option. It's ideal for businesses looking for quick ROI and time to market while being adaptable.

Shopify Plus

Shopify Plus maintains a favorable time to market while offering certain flexibilities. To achieve faster ROI, leveraging Shopify's massive ecosystem of apps is necessary. Customization is possible, but it's important to note that increased TCO might push you towards headless requirements.

Commerce Components and Adobe Commerce SaaS

Adobe Commerce SaaS and Shopify’s commerce components represent platforms where TCO is higher from the start due to headless architecture demands. Extensive coding and architecture planning are imperative. These platforms provide significant flexibility, but with a trade-off of increased TCO and time to market.

Specific Use Cases

For those needing custom customer experiences, such as scripts for VIP customer interfaces without affecting performance, server-side rendering is essential—highlighting the utility of commerce components or Adobe Commerce. Additionally, businesses needing an unaltered URL structure may find that headless platforms offer the necessary flexibility not available in Shopify Plus.

Conclusion

This high-level comparison provides valuable insights into how Shopify and Adobe Commerce SaaS stand relative to TCO, flexibility, ROI, and business requirements. For CTOs navigating this complex decision, understanding these elements will support better business and technical decision-making. Should you need further assistance, feel free to reach out. Until next time, best of luck with your e-commerce endeavors!

A Comprehensive Guide for CTOs: Adobe Commerce SaaS vs Shopify

Rafael Corrêa Gomes — Mon, 31 Mar 2025 20:51:34 +0000

Introduction

Identifying the Four Main Pillars

Strict and Complex Requirements

TCO and Flexibility

Faster ROI and Time to Market

Flexible Business Requirements

Platform Deep Dive

Shopify Basic to Advanced

Shopify Plus

Commerce Components and Adobe Commerce SaaS

Specific Use Cases

Conclusion

Adobe Commerce as a Cloud Service is NOT like Shopify

Rafael Corrêa Gomes — Fri, 21 Mar 2025 20:40:43 +0000

The new Adobe Commerce as a Cloud Service is launching in June 2025, and there’s a lot of buzz around it. Many people expect it to be like Shopify Advanced, but that’s far from reality. Even Shopify Plus isn’t a direct comparison. Here’s why:

Headless by Default – Unlike Shopify, where headless is optional (and mostly a Shopify Plus + Hydrogen + Components game), Adobe’s new SaaS offering mandates headless. This means it’s targeting merchants with more complex needs right from the start.
10x Easier to Deploy – Adobe is promising provisioning in minutes, making it significantly easier to set up compared to its current Cloud infrastructure. But easier doesn’t mean “plug-and-play” like Shopify, it’s still geared toward enterprise-level customization.
Lower TCO & Licensing Costs – A major shift from the traditional Adobe Commerce model, bringing it closer to Shopify Plus in terms of affordability and predictability.

So where does it fit?
This isn’t a direct competitor to Shopify Advanced, nor does it aim for SMBs. Instead, it positions itself for stores that would otherwise require Shopify Plus + Hydrogen + Components, making it an option for enterprises that demand headless architecture by default rather than as an add-on.

Adobe Commerce as a Cloud Service is not a Shopify killer, but it does carve out its space for brands needing enterprise-grade flexibility in a fully managed SaaS environment.

Are you planning to implement Adobe Commerce as a Cloud Service or Shopify? Let’s discuss!

Adobe Commerce Saas Announcement

Rafael Corrêa Gomes — Tue, 18 Mar 2025 16:38:09 +0000

Adobe is announcing two major products set to launch in June 2025:

✅ Adobe Commerce as a Cloud Service – A fully SaaS-based commerce platform with instant provisioning, AI-powered content creation, and high-performance storefronts powered by Edge Delivery Services.

✅ Adobe Commerce Optimizer – A platform-agnostic experience layer that enhances any eCommerce system with AI-driven personalization, ultra-fast storefronts, and seamless API integrations—without requiring a full replatform.

🔎 In this podcast, they break down:

What these new products mean for Adobe Commerce developers and merchants.
How Edge Delivery Services will redefine performance and SEO.
The implications of moving from PaaS/on-premise to SaaS.

Why Adobe is making this shift and how businesses can transition gradually.

Adobe Commerce's Big Announcement: A Technical Deep Dive

Rafael Corrêa Gomes — Fri, 14 Mar 2025 16:49:27 +0000

Adobe Commerce's Big Announcement: A Technical Deep Dive

The future of Adobe Commerce is undergoing a significant transformation with the announcement of two new products: Adobe Commerce as a Cloud Service and Adobe Commerce Optimizer. Both solutions, launching in June 2025, aim to optimize performance, scalability, and integration flexibility for businesses.

This post provides a technical breakdown of these innovations and what they mean for developers and eCommerce architects.

🚀 Key Changes in Adobe Commerce

1️⃣ Adobe Commerce as a Cloud Service

A fully SaaS-based eCommerce platform designed for speed, scalability, and reduced operational complexity.

Instant Provisioning: Deploy a new store in minutes.
Managed SaaS Updates: Adobe handles patches and releases automatically.
Edge Delivery Services: Speeds up storefront load times by caching content closer to users.
AI-powered Content Creation: Uses GenAI for personalized experiences and A/B testing.
Enterprise-Grade Scalability:
- Supports 250M SKUs.
- Up to 30K unique prices per SKU.
- Enables real-time catalog syndication across multiple channels.
Native Integration with Adobe Tools: Includes Adobe Express, Firefly, and Digital Asset Management (DAM).

2️⃣ Adobe Commerce Optimizer

An independent experience layer that enhances existing eCommerce platforms, making it technology-agnostic.

Lightning-Fast Storefronts: Optimized UI/UX for enhanced user engagement.
Pre-built Connectors & APIs: Enables seamless integration with various backend systems.
AI-enhanced Merchandising & Personalization: Dynamically adjusts content based on user behavior.
Performance Analytics & Optimization:
- Before-and-after reporting to measure impact.
- A/B testing capabilities to fine-tune strategies.

🛠️ Technical Implications for Developers

🆚 SaaS vs. PaaS vs. On-Premise

Adobe has assured ongoing support for on-premise and PaaS deployments, but the emphasis is on transitioning to SaaS. Developers should consider:

Infrastructure Reduction: No more server management or patch maintenance.
Customization Trade-offs: SaaS limits deep code modifications but offers APIs and extensibility options.
Security & Compliance: Automatic updates reduce vulnerability risks, ensuring PCI compliance.

⚡ What Edge Delivery Services Mean for Performance

Adobe’s Edge Delivery Services leverage a CDN-like architecture to reduce load times. Developers can expect:

Faster Page Loads: Content is served from the nearest edge location.
Improved SEO & Organic Traffic: Faster sites rank higher on Google.
Lower Server Load: Reduces backend requests by caching frequently accessed content.

🤖 AI-Powered Content & Merchandising

The introduction of GenAI-driven content tools changes the way eCommerce teams work:

Automated Product Descriptions: Dynamic generation based on user preferences.
Personalized Promotions: AI adapts discounts and messaging in real-time.
Integrated A/B Testing: Optimizes layouts and CTAs without manual intervention.

🎙️ Podcast Discussion: A Technical Deep Dive

https://youtu.be/aZkFN45kmzk

In our latest Deep Dive Podcast, we analyze these new Adobe Commerce features and their impact on the developer community. Key points discussed:

How Edge Delivery Services fundamentally changes performance optimization.
The real-world benefits of SaaS eCommerce vs. traditional PaaS/on-premise models.
The trade-offs of adopting Adobe Commerce Optimizer on non-Adobe platforms.
Strategies for migrating gradually vs. full transition to Adobe Commerce as a Cloud Service.

🏗️ Developer Roadmap: Preparing for the Shift

✅ 1. Evaluate Your Stack

If you are currently using Adobe Commerce (Magento) on-premise, start identifying features that can transition to Adobe Commerce Optimizer.
If your business is considering a full migration, prepare for API-based customizations rather than deep core modifications.

✅ 2. Prepare for API-First Development

Learn the new API architecture for headless commerce and custom integrations.
Leverage GraphQL and REST APIs for storefront interactions.
Understand the Adobe Experience Cloud ecosystem for content and asset management.

✅ 3. Optimize Performance with Edge Delivery Services

Implement best practices for CDN-based caching.
Analyze Google Lighthouse scores to benchmark performance improvements.
Test with high SKU catalogs to assess real-world scalability.

🔥 Final Thoughts

Adobe’s push towards a SaaS-first commerce ecosystem is a major shift for developers and businesses alike. While PaaS and on-premise solutions remain supported, the future clearly points towards cloud-native, AI-powered commerce. Developers should start adapting by exploring Adobe Commerce APIs, Edge Delivery Services, and GenAI integrations.

💬 What are your thoughts on Adobe's new approach?

Will your team adopt Adobe Commerce as a Cloud Service or test Adobe Commerce Optimizer? Let’s discuss in the comments!

Magento PWA Studio setup in minutes

Rafael Corrêa Gomes — Fri, 23 Jun 2023 14:52:34 +0000

Many developers take some time setting up Adobe Commerce + PWA Studio for the first time. Mainly on their local machines to start their tests and possibly contribute to this OpenSource software.

Since the last release v13.2.0, you can start to use DevContainer online or locally. Here I'll describe how to start using it.

Github Codespaces

The easiest way to start is by using Github Codespaces. You can initialize your environment by accessing PWA Studio on Github and clicking on Create codespace on develop from there.

All the required initial steps have been executed automatically, installing the NPM packages, running the build, and initializing the watch command through port 10000.

Running PWA Studio locally

After cloning the PWA Studio locally from Github, open in on Visual Studio Code, and you will see this message to open in on DevContainer. Before clicking on it, confirm you have Docker running.

If you missed the button above, you can click on the bottom left side of the screen and Reopen in Container.

Locally might take more time than Github Codespace. In the end, you will have it running, as you can see in the image below.

Now you have an environment ready to test and contribute! Certainly, the best part is that we have it running in development mode. Any change you make to the files will be instantaneously reflected on your local Venia demo store.

For more articles, check out my blog section.

No more Carrier Service API on Shopify

Rafael Corrêa Gomes — Thu, 01 Dec 2022 17:25:30 +0000

Today Shopify announced that starting January 1, 2023, stores on the Shopify Starter and Basic plans will no longer be able to request access to the Carrier Service API. It means that it's not all Shopify plans will have access to Shipping apps that offer shipping rates.

Stores on the Shopify Advanced and Plus plans will continue to have access to the Carrier Service API. Stores on the Shopify plan can continue to request access by contacting Shopify support. Stores on the Shopify Starter or Basic plans that were previously granted access are not impacted by this change and will keep their access to the Carrier Service API.

Next steps

Update your Shopify App Store listing and any other external communications to reflect this change by January 1, 2023.
Inform your support staff about the changing access requirements and timelines.

How to use custom URLs with Shopify Hydrogen

Rafael Corrêa Gomes — Wed, 06 Apr 2022 01:47:23 +0000

Shopify Headless is used in different ways. The way I recommend most to merchants is through Shopify Hydrogen. In this article, I'm going to show you how to set up a custom URL for your international store to improve your SEO results and give a better experience to your clients by supporting other languages.

If you want to learn how to create a fantastic production-ready Shopify Headless store with Hydrogen, check out my course on Udemy.

How custom URLs work

All your old URLs on your Shopify store will remain the same, but the main difference is that your headless will control what to show on each page URL. It gives you total flexibility of customization and increases your responsibility of maintaining it simultaneously.

Translating and customizing category URL

As you can see in the image below, the first step will be changing a folder name and the folder collections inside the routes folder, which defines which route (URL path) to predict.

You will be able to access the new translated URL right away. I changed collection to categorias in Portuguese.

The second step is to change all the links in your theme that might include collections in the link statically. I had to change it in my Navigation file, as you can see in the image below.

It can become enormously tricky depending on the project, but at least now, you don't need to start from scratch in your analysis. I hope it helped you understand how Shopify architecture works with a headless store and custom URLs.

How to use custom domains? Shopify Hydrogen + Cloudflare Workers

Rafael Corrêa Gomes — Fri, 11 Mar 2022 00:06:25 +0000

Introduction on Cloudflare Workers to host your Shopify Hydrogen theme and setup your custom domain

Shopify Hydrogen custom domain setup is the last, you're ready to host it on Cloudflare Workers. In this post, we will cover a few questions about Cloudflare Workers when setting up your custom domain.

Shopify Hydrogen custom domain

The backend of our Shopify Hydrogen will be our Shopify store, we still using the default domain, and the main domain will be attached to your serverless frontend on Cloudflare.

This is my Shopify Hydrogen Headless demo, and this is my Shopify Hydrogen Course where I cover this and many other topics.

Start to configure your Cloudflare Workers

Cloudflare will be responsible for keeping your main domain, DNS control and cache. If you don't have your domain control via Cloudflare, this is your first step.

The second step is to set up Wrangler, a CLI tool that will allow you to control your Serverless applications from your terminal.

npm install -g @cloudflare/wrangler
wrangler configure

If you didn't prepare your Hydrogen theme to run in your Cloudflare Workers instance, I recommend checking my article teaching how to set up your project for Cloudflare Workers.

Custom domain

The first thing you will see in your Cloudflare panel will be your main DNS domain. Make sure to add these two records to your DNS records, it's a kind of fake redirect just for internal purposes.

Cloudflare DNS record to Workers

Clicking on it you can access Workers in the left bar and configure the new HTTP route, don't forget the /* in the end. It means you are creating a new subdomain or domain pointing to your serverless application.

Open your Workers and make sure you can see your new serverless project as the image below.

Cloudflare Workers panel

I got my account_id and zone_id from my panel.

Cloudflare API keys

My wrangler.toml file is like this below.

name = "course-shopify-hydrogen"
type = "javascript"
account_id = "120dfc03120dfc03120dfc03120dfc0"
workers_dev = true
compatibility_date = "2022-01-28"
compatibility_flags = ["streams_enable_constructors"]
zone_id = "r856ea704f7c4r856ea704f7c4r856ea704f7c4"

[env.production]
route = "course-shopify-hydrogen.rafaelcg.com/*"

[site]
bucket = "dist/client"
entry-point = "dist/worker"

[build]
upload.format = "service-worker"
command = "yarn && yarn build"

Advantages to use Shopify Hydrogen with Serveless

In general, these below are the main points.

Lower costs -- Generally very cost-effective.
Simplified scalability -- Developers using serverless architecture don't have to worry about policies to scale up their code. The serverless vendor handles all of the scaling on demand.
Simplified backend code -- With FaaS, developers can create simple functions that independently perform a single purpose, like making an API call.
Quicker turnaround -- The easiest way to go-live, serverless architecture can significantly cut time to market.

To know more details, please check the last post.

DEV Community: Rafael Corrêa Gomes

Why Brands Join (and Leave) Shopify?

Why Brands Join Shopify

Why Brands Leave Shopify

My Take on the Market

The strategy evolves when the platform changes

The Migration Journey (M1 to M2)

A Different Kind of Transition (Going to Saas)

This Time, Strategy Beats Manual Work

Why I Built an Adobe Commerce Dev MCP Server and How It Can Help You Code Faster

What Is It?

A Comprehensive Guide for CTOs: Adobe Commerce SaaS vs Shopify

Introduction

Identifying the Four Main Pillars

Platform Deep Dive

Specific Use Cases

Conclusion

A Comprehensive Guide for CTOs: Adobe Commerce SaaS vs Shopify

Introduction

Identifying the Four Main Pillars

Platform Deep Dive

Specific Use Cases

Conclusion

Adobe Commerce as a Cloud Service is NOT like Shopify

Adobe Commerce Saas Announcement

Adobe Commerce's Big Announcement: A Technical Deep Dive

Adobe Commerce's Big Announcement: A Technical Deep Dive

🚀 Key Changes in Adobe Commerce

1️⃣ Adobe Commerce as a Cloud Service

2️⃣ Adobe Commerce Optimizer

🛠️ Technical Implications for Developers

🆚 SaaS vs. PaaS vs. On-Premise

⚡ What Edge Delivery Services Mean for Performance

🤖 AI-Powered Content & Merchandising

🎙️ Podcast Discussion: A Technical Deep Dive

🏗️ Developer Roadmap: Preparing for the Shift

✅ 1. Evaluate Your Stack

✅ 2. Prepare for API-First Development

✅ 3. Optimize Performance with Edge Delivery Services

🔥 Final Thoughts

💬 What are your thoughts on Adobe's new approach?

Magento PWA Studio setup in minutes

Github Codespaces

Running PWA Studio locally

No more Carrier Service API on Shopify

Next steps

How to use custom URLs with Shopify Hydrogen

How custom URLs work

Translating and customizing category URL

How to use custom domains? Shopify Hydrogen + Cloudflare Workers

Shopify Hydrogen custom domain

Start to configure your Cloudflare Workers

Custom domain

Advantages to use Shopify Hydrogen with Serveless

Cloudflare Workers Documentations