Adobe’s Commerce options

Learn about Adobe’s commerce options. Understand what some of the main features include, how it’s hosted, and who each model is best suited for. You learn the differences between running everything themselves (on-prem), using Adobe-managed cloud infrastructure (PaaS), adopting a fully managed SaaS approach, or modernizing only the storefront layer with Commerce Optimizer while keeping an existing backend.

Who is this video for?

  • VP/Director of Commerce
  • Technical leadership
  • DevOps/Platform engineers
  • Marketing Technology Manager

Video content

  • Compare Adobe Commerce deployment models: on-prem, cloud, SaaS, and Optimizer
  • Learn who manages infrastructure vs applications in each option
  • Understand when to modernize storefronts without replacing your backend
  • Identify the best fit based on DevOps resources, scalability, and business goals
Transcript

Hi, this is Russell with Adobe. In this video, we’ll walk through the options available for Adobe’s Commerce capabilities.

First, we have Adobe Commerce. Next would be Adobe Commerce Cloud, followed by Adobe Commerce as a Cloud Service, and our last one is Adobe Commerce Optimizer. By the end of the video, you’ll understand what each option includes, how it’s hosted, and what a business might choose one approach over another.

So we’ll start with Adobe Commerce. This on-premise option of Adobe Commerce provides the core set of capabilities, things like product and catalog management, pricing and promotions, coupons, checkout, order management. It also has B2B features, things like company accounts and quotes. It also includes a native front-end and supports headless integrations. In this model, you’ll deploy and operate everything, including the infrastructure, scaling, monitoring, tools, security, compliance, server patches, upgrades, code management. This is actually best for teams that have strict infrastructure or data residency needs, or you simply just want complete control over the runtime and deployments.

You also need to make sure that you have a strong in-house DevOps and security team.

The key takeaway here is that Adobe will provide the application and you’ll run the environment.

Up next, we have Adobe Commerce Cloud. This is our platform as a service model. You still have the same PHP codebase, but in this one, Adobe hosts and manages the cloud infrastructure. It includes a pre-configured Commerce Optimized Stack. It has Git-based workflows with automated builds and deployments. And you’re given a development, staging, and production environment, as well as a CDN and performance monitoring. This version also includes that same native storefront, but it also supports headless.

Adobe will manage the cloud infrastructure, and you’ll manage the application, those customizations, and the storefront configuration. This is a really good fit when you want the extensibility of Adobe Commerce, but you want Adobe to handle the hosting, the infrastructure stability, and the cloud tooling.

And next, we’ll talk about Adobe Commerce as a cloud service.

This is a software as a service SaaS model, and it is a cloud-native evolution of Adobe Commerce. It’s API first, and it’s services-based. It brings together the foundation commerce capabilities, things like the catalog management, the cart, checkout, B2B, B2C functionality, and it also provides the edge-delivered storefront for fast page delivery. You can also take advantage of the document-based authoring tools available for ACCS. You’ll also get the AI merchandising services for product discovery and product recommendations. Operationally, it’s always up to date with continuous features and security releases. There’s also auto-scaling, it’s cloud-native, and it has a composable architecture that’s API first, and it offers extensibility through Adobe’s app builder. Adobe is going to manage the entire infrastructure and the commerce services, and this allows your team to focus on business logic, integrations, and the storefront experience.

Compared to the PaaS, or the platform as a service offering, this model shifts more operational responsibility, and it takes advantage of the SaaS operating approach.

The final option is Adobe Commerce Optimizer. Adobe Commerce Optimizer modernizes the shopper-facing experience without having to replatform your backend. It offers fast edge-delivered storefront with drop-in components for things like product listing pages, product detail pages, the cart, customer accounts, the product pricing and catalog services, as well as an AI-powered search and recommendation.

It also includes the Adobe Commerce Catalog Data Model, the CCDM, with supporting features like multi-brand, multi-region, catalog views and policies, as well as thousands of price books for complex B2B needs.

The key point for this one is that ACO is designed to sit on top of your existing commerce engine, whether that be Adobe Commerce or any other e-commerce platform. It improves the storefront performance and offers personalization, discovery, and offers fast time-to-market for front-end changes. This is an excellent fit for when you want a modern, flexible storefront, but you’re not ready to replace your entire backend e-commerce system.

Let’s just recap on what we’ve learned. We’ll start with Adobe Commerce. This is where you would operate everything. Adobe is simply going to provide the app.

For Adobe Commerce Cloud, Adobe is going to run the cloud layer. You’ll manage the app, the extensions, and integrations.

For Adobe Commerce as a cloud service, Adobe manages both the infrastructure and the services. And then last, Adobe Commerce Optimizer. Adobe provides that storefront and merchandising layer to sit on top of your existing commerce backend. Well, that’s going to wrap it up for this session on Adobe’s Commerce Options. I hope you continue to come back to Experience League to learn more about Adobe Commerce as well as all of the other Adobe products.

recommendation-more-help
3a5f7e19-f383-4af8-8983-d01154c1402f