Adobe Commerce Developer Professional flashcards
Adobe Commerce Developer Professional · Build recall with a focused review session.
32 cards. Read the term and the definition here. The deck at the top of this page is optional.
- Object Manager
- The service container in Adobe Commerce that instantiates classes and resolves dependencies. It is configured via di.xml and should not be used directly in code; use dependency injection instead.
- Dependency Injection
- A design pattern where objects receive their dependencies from an external source. In Adobe Commerce, configured in di.xml, enabling preferences, virtual types, and argument injection.
- Plugin (Interceptor)
- A mechanism to modify the behavior of public methods without changing the class. Types: before, around, after. Configured in di.xml and executed in order of sortOrder.
- Around Plugin
- A plugin method that wraps the original method, receiving a callable $proceed to invoke the next plugin or original method. It can modify arguments and return value.
- Area
- A logical scope in Adobe Commerce that determines configuration and dependency injection. Examples: frontend, adminhtml, webapi, crontab. Each area can have its own di.xml.
- Event and Observer
- Events are dispatched by code to allow other modules to react. Observers are configured in events.xml and execute synchronously when the event is dispatched.
- Cron Job
- A scheduled task defined in crontab.xml. Groups and schedules are configured; system cron must run bin/magento cron:run periodically to execute jobs.
- Deployment Mode
- A setting that affects performance and behavior: default, developer, or production. Set via bin/magento deploy:mode:set. Production mode requires static content deployment and DI compilation.
- env.php
- A configuration file in app/etc/ that stores system-specific settings like database credentials, cache hosts, and encryption key. It is not version-controlled.
- config.php
- A configuration file in app/etc/ that stores the list of enabled modules and scopes. It is version-controlled and updated by bin/magento commands.
- Indexer Modes
- Two modes: Update on Save (index updates immediately when data changes) and Update by Schedule (index updates via cron). Configured per indexer via bin/magento indexer:set-mode.
- Static Content Deployment
- The process of generating and deploying static files (CSS, JS, images) to pub/static. Required in production mode; executed via bin/magento setup:static-content:deploy.
- Configuration Scope
- The hierarchy of configuration levels: default, website, store, and store view. Values set at a higher scope cascade to lower scopes unless overridden.
- Cache Types
- Individual cache segments (e.g., config, layout, block_html, full_page) that can be enabled or disabled. Managed via bin/magento cache:enable/disable/clean/flush.
- Setup Upgrade
- The command bin/magento setup:upgrade that applies database schema and data changes from modules. It runs install/upgrade scripts and patches.
- Theme Structure
- A theme consists of theme.xml, registration.php, etc/view.xml, and directories like Magento_Module/layout, templates, web/css/source. It defines the visual design.
- Layout XML
- XML files that define the structure of a page by declaring blocks, containers, and actions. Located in etc/ or view/ directories of modules and themes.
- Template (.phtml)
- A PHP template file that contains the HTML and PHP code for rendering a block. It is rendered by a block class and can be overridden in a theme.
- View Model
- A class that provides data and logic to templates without modifying the block. It implements ArgumentInterface and is assigned via layout XML arguments.
- Layout Handle
- An identifier used to apply specific layout updates. Examples: default, cms_index_index. Custom handles can be added via controllers or observers.
- UI Component
- A reusable UI element configured via XML (ui_component) and rendered with KnockoutJS and RequireJS. Used in admin and frontend for complex interfaces.
- Theme Fallback
- The order in which Adobe Commerce searches for templates and layouts: module, parent theme, child theme, base theme. Configured in theme.xml.
- module.xml
- A file that declares a module and its dependencies. Located in etc/. It defines the module name and sequence, affecting load order and schema.
- registration.php
- A file that registers a module or theme with the component registrar. It uses ComponentRegistrar::register() and is required for the component to be recognized.
- routes.xml
- A configuration file that defines route front names for a module. Located in etc/frontend/ or etc/adminhtml/. It maps URLs to controllers.
- Declarative Schema
- A method to define database tables and columns via db_schema.xml. Changes are applied during setup:upgrade and tracked in db_schema_whitelist.json.
- Data Patch
- A class implementing DataPatchInterface that modifies data during setup:upgrade. Patches run once and are recorded in the patch_list table.
- Preference
- A di.xml configuration that specifies which class should be used for a given interface or class. It replaces the default implementation globally.
- Web API
- An interface for integrating with Adobe Commerce via REST or SOAP. Services are exposed in webapi.xml and authenticated via tokens or OAuth.
- EAV Model
- Entity-Attribute-Value model used for products, customers, and categories. Attributes are stored in eav_attribute and backend tables based on backend type.
- Attribute Backend Type
- Determines the storage table for an attribute: static (main entity table), varchar, int, text, decimal, datetime. Set when creating the attribute.
- Flat Tables
- Denormalized tables (catalog_product_flat, catalog_category_flat) that store product/category data for faster reads. Populated by flat indexers.