What is Magento? — Adobe Commerce Enterprise E-Commerce Platform Explained
In this tutorial, you'll learn what Magento is, how its e-commerce architecture works, and why it powers enterprise-level online stores for thousands of businesses worldwide.
What You'll Learn
- The history of Magento from a small PHP project to Adobe Commerce
- Magento Open Source compared to Adobe Commerce and Commerce Cloud
- How Magento compares to WooCommerce, Shopify, and BigCommerce
- Why enterprises choose Magento for multi-store and B2B scenarios
- The Magento ecosystem of extensions, agencies, and developers
- Key architectural concepts like EAV, modules, themes, and scopes
- What you can build with Magento — from single stores to marketplaces
Why It Matters
Choosing the right e-commerce platform determines your store's performance, scalability, and total cost of ownership. Magento is the only open-source enterprise platform that handles complex product catalogs, multi-store architectures, B2B features, and headless commerce out of the box. If you plan to build or maintain a serious e-commerce operation, understanding Magento is a career-defining skill.
Real-World Use
A global electronics retailer needs to sell across 12 countries with different currencies, tax rules, and languages. Their catalog has 50,000 SKUs with configurable options like storage capacity and color. They need B2B pricing for wholesale customers, a separate store for each country, and integration with their ERP system. Magento handles all of this in a single installation, where WordPress with WooCommerce would require dozens of plugins and custom work.
Learning Path
flowchart LR A["What is Magento?
← You are here"]:::current A --> B["Local Installation"] B --> C["Admin Dashboard"] C --> D["Magento Hosting"] D --> E["Product Types"] classDef current fill:#38bdf8,color:#0f172a,stroke-width:2px
History of Magento
Magento started in 2008 as a project by Varien, a small PHP development company. Roy Rubin and Yoav Kutner led the development. The first public beta released in August 2008, and Magento 1.0 launched in March 2009.
In 2011, eBay acquired Magento for approximately $180 million. Under eBay, Magento grew significantly but also saw changes in leadership and direction. In 2015, Magento split from eBay into an independent company backed by private equity.
The defining moment came in 2018 when Adobe acquired Magento for $1.68 billion and rebranded it as Adobe Commerce. This brought Magento into the Adobe Experience Cloud, alongside Adobe Analytics, Adobe Target, and Adobe Experience Manager.
Magento 2 was first released in 2015 (after years of development that began around 2011). The codebase was completely rewritten with modern PHP practices, Composer dependency management, and a plugin-based architecture. Magento 1 reached end of life in June 2020, forcing migrations to Magento 2 or other platforms.
Magento Editions
Magento comes in three editions, each targeting different business needs:
| Edition | Former Name | Best For | Cost |
|---|---|---|---|
| Magento Open Source | Community Edition (CE) | Small-medium stores, developers learning Magento | Free (MIT license) |
| Adobe Commerce | Enterprise Edition (EE) | Mid-large enterprises, B2B, multi-store | License fee (revenue-share) |
| Adobe Commerce Cloud | Enterprise Cloud Edition | High-traffic enterprises, PCI-compliant hosting | License + Cloud fee |
Magento Open Source gives you the full core platform. You handle hosting, security, performance tuning, and everything else yourself. It is ideal for learning, small stores, and custom projects.
Adobe Commerce adds B2B features (shared catalog, company accounts, quotes), advanced inventory, customer segmentation, visual merchandising, and the Page Builder tool. You get priority support from Adobe.
Adobe Commerce Cloud is Adobe Commerce running on Adobe's managed infrastructure. It provides a PaaS environment with Git-driven deployments, integration/staging/production branches, 24/7 monitoring, and PCI compliance baked in.
Magento vs WooCommerce vs Shopify vs BigCommerce
Here is a comparison of the major e-commerce platforms:
| Feature | Magento (Adobe Commerce) | WooCommerce (WordPress) | Shopify | BigCommerce |
|---|---|---|---|---|
| Type | Self-hosted | WordPress plugin | Hosted SaaS | Hosted SaaS |
| Open source | Yes (Open Source) | Yes | No | No |
| Multi-store | Native | Add-ons only | Apps needed | Add-ons |
| B2B features | Built-in (Adobe Commerce) | Plugins | Plugins | Built-in |
| Scalability | Enterprise-grade | Medium | High | High |
| Customization | Unlimited (code level) | High (PHP + plugins) | Limited (Liquid) | Medium |
| Performance | Needs tuning | Plugin-dependent | Managed | Managed |
| Total cost | Moderate to high | Low to moderate | Monthly subscription | Monthly subscription |
| Best for | Large, complex catalogs | Small-medium stores | Quick start, SMB | Mid-market |
Why Enterprises Choose Magento
Enterprises choose Magento for several compelling reasons:
Multi-store capability. A single Magento installation can run multiple stores under different domains, with separate product catalogs, pricing, currencies, and designs. A retailer selling in the US, UK, and Japan under different brand names can manage everything from one admin panel.
B2B features. Adobe Commerce includes company accounts, shared catalogs (different products/prices per company), negotiated quotes, and purchase orders. For a wholesale distributor with thousands of business customers, this is essential.
Complex catalog management. With the EAV (Entity-Attribute-Value) architecture, Magento can handle products with arbitrary attributes. A laptop has processor, RAM, storage, screen size — Magento handles these without database schema changes.
Flexible pricing. Special prices, tier pricing, group pricing, catalog rules, and cart rules give complete control over pricing strategies. A store can show different prices to different customer groups automatically.
Integration capabilities. Magento's REST API, GraphQL API, message queues, and event system allow deep integration with ERPs, CRMs, PIMs, and warehouse management systems. JavaScript front-ends can communicate via GraphQL.
Security. Adobe Commerce includes PCI DSS compliance tools, a dedicated security team that releases regular patches, and security scanning tools.
The Magento Ecosystem
Magento has a rich ecosystem of developers, agencies, and partners:
Magento Marketplace. Thousands of extensions for shipping, payments, marketing, SEO, and integrations. Many are free; premium extensions range from $50 to $500+.
Solution partners. Agencies specializing in Magento development, design, and consulting. Adobe has a partner certification program.
Magento developers. A global community of developers maintaining open-source modules, contributing to Magento core, and writing tutorials. The Magento Association organizes events and training.
Adobe partners. For Adobe Commerce, Adobe provides official support, training, and certification programs including the Adobe Commerce Certified Developer exam.
Key Architecture Concepts
Understanding these concepts is essential before you start working with Magento:
EAV (Entity-Attribute-Value). Instead of adding columns to database tables for each product attribute, Magento stores attributes as rows in multiple tables. This allows unlimited product attributes without schema changes. Product name, price, color, size — all are attributes stored in the EAV structure.
Modules. Everything in Magento is a module. A module is a directory with a registration.php and module.xml file. Core features like Catalog, Sales, and Customer are themselves modules. Third-party extensions are modules.
Themes. A theme customizes the storefront. Themes inherit from parent themes. The Blank theme is the base parent for most custom themes. Layout XML files control page structure, and PHTML template files control HTML rendering.
Stores, Websites, and Store Views. A Magento installation can have multiple websites (different domains). Each website can have multiple stores (different root categories). Each store can have multiple store views (different languages). This is the scope hierarchy.
Scopes. Configuration settings can be set at Global, Website, or Store View level. A price might be global, a currency setting might be per website, and a language setting per store view.
Dependency Injection. Magento 2 uses a DI container configured via di.xml files. You specify class preferences, plugin configurations, and constructor argument injection in XML.
Plugins (Interceptors). Plugins, also called interceptors, let you modify the behavior of any public method in the system without modifying the original class. You can run code before, after, or around the original method.
What You Can Build with Magento
Magento adapts to nearly any e-commerce use case:
| Type | Description | Key Features Used |
|---|---|---|
| Single store | One brand, one country | Simple setup, standard catalog |
| Multi-store | Multiple brands/countries | Websites, store views, scopes |
| B2B | Wholesale only | Shared catalog, quotes, company accounts |
| B2C | Retail to consumers | Standard catalog, promotions, cart rules |
| B2B + B2C | Hybrid | Customer groups, group pricing |
| Marketplace | Multi-vendor | Third-party marketplace extensions |
| Headless | Decoupled front-end | GraphQL API, PWA Studio |
| Multi-language | International | Store views per language, inline translation |
Common Mistakes
Treating Magento like WordPress. Magento is not a plug-and-play system. Beginners often expect it to work out of the box without configuration. Magento requires deliberate design of catalog structure, attribute sets, and tax rules before launching.
Choosing the wrong edition. Starting with Magento Open Source for a complex multi-store enterprise project when you need Adobe Commerce's B2B features. Conversely, paying for Adobe Commerce when Open Source would suffice.
Ignoring hosting requirements. Running Magento on shared hosting. Magento needs dedicated servers with PHP 8.2+, Elasticsearch/OpenSearch, Redis, Varnish, and at least 16 GB RAM. Cheap hosting leads to slow performance and unreliable stores.
Overinstalling extensions. Every extension adds code, database queries, and potential conflicts. Beginners install too many free extensions instead of using built-in features or writing custom code.
Skipping the learning curve. Jumping into custom module development without understanding the EAV system, service contracts, and dependency injection leads to code that breaks with every update.
Practice Questions
What is the difference between Magento Open Source and Adobe Commerce? Answer: Magento Open Source is the free version with core e-commerce features. Adobe Commerce adds B2B features (shared catalog, company accounts, quotes), Page Builder, advanced inventory, customer segmentation, visual merchandising, and Adobe support.
Why does Magento use the EAV architecture instead of flat database tables? Answer: EAV allows unlimited product attributes without schema changes. Adding a new attribute like "processor speed" does not require adding a column to a database table. The attribute is stored as rows in the EAV tables, making the system flexible for products with different attribute sets.
What are the three editions of Magento and who should use each? Answer: Magento Open Source (small-medium stores, developers), Adobe Commerce (mid-large enterprises, B2B, multi-store), Adobe Commerce Cloud (high-traffic enterprises needing managed PCI-compliant hosting with deployment pipelines).
Challenge: Visit three e-commerce sites you use regularly. Identify whether they run on Magento using tools like BuiltWith or by checking the page source for
/static/versionpaths. For each site, list three clues. Magento sites typically have URLs like/checkout/cart/, static content versioning in paths, and specific cookie names likemage-messages.
FAQ
{{< faq "Is Magento free?" "Magento Open Source is free under the MIT license. Adobe Commerce and Adobe Commerce Cloud require paid licenses. The free version includes the full core platform. You pay for hosting, extensions, development, and maintenance. A typical Magento store costs significantly more to run than a {{< ilink "WordPress" >}} / WooCommerce store." >}}
{{< faq "What programming language is Magento written in?" "Magento is written in {{< ilink "PHP" >}} (8.2+ for Magento 2.4.7+). It uses Composer for dependency management, {{< ilink "JavaScript" "JavaScript" >}} and RequireJS for the front-end, {{< ilink "MySQL" >}} / MariaDB for the database, and XML for configuration. The architecture follows object-oriented Design Patterns including dependency injection, service contracts, and MVC." >}}
{{< faq "What is the difference between Magento 1 and Magento 2?" "Magento 2 is a complete rewrite with modern {{< ilink "PHP" >}} (namespaces, traits, generators), Composer integration, improved performance (Varnish, Redis, full-page cache), declarative database schema, plugin architecture (interceptors), and {{< ilink "JavaScript" "JavaScript" >}} improvements (RequireJS, Knockout). Magento 1 reached end of life in June 2020 and is no longer supported." >}}
Mini Project
Your task: Research three Magento-powered stores and identify their components.
- Visit builtwith.com and search for sites using Magento. Alternatively, visit known Magento stores like landrover.com/experience, hellyhansen.com, or jackjones.com.
- For each store, identify:
- Whether it runs Magento Open Source or Adobe Commerce (check page source for
/static/version/paths) - What third-party extensions it likely uses (look for payment gateways, shipping carriers, SEO tools)
- What edition best fits their needs (single store, multi-store, B2B)
- Whether it runs Magento Open Source or Adobe Commerce (check page source for
- Use your browser's Inspect tool to find Magento-specific elements:
require.jsloading,baseUrlconfiguration,form_keyhidden inputs, andproduct_addtocart_formselectors. - Write up your findings — what made Magento the right choice for each site?
This exercise trains you to identify Magento stores in the wild, which you will do constantly as a Magento developer.
What's Next
Now that you understand what Magento is and what it can do, let's install it on your computer so you can start building:
Continue to Lesson 2: Local Installation — Install Magento locally with Composer.
Related lessons:
- Magento Admin Dashboard — Navigate every menu and screen
- Magento Hosting — Cloud, VPS, and server requirements
- PHP Basics — Learn the language Magento is built on
Built by the developers of DodaTech
Doda Browser, DodaZIP & Durga Antivirus Pro