:quality(75))
Adobe Commerce (Magento) 2.4.4 was released on 12 April 2022. It is not a routine version bump: it moves the minimum PHP version, completes GraphQL coverage for B2B, and closes several security gaps at once.
PHP 8.1 is now the floor
2.4.4 mandates PHP 8.1, making it the minimum requirement. That is the change with the most immediate operational effect.
JIT compilation. Just-in-time compilation lets the runtime optimise hot code paths, worth 20-40% on typical workloads.
Lower memory per request, which means more concurrency on the same hardware.
Faster execution, across page loads, admin operations and behaviour under load.
For a high-traffic store that can be the difference between buying more infrastructure and handling peak on what you already have. On headless and API-driven builds the gains are more pronounced.
GraphQL now covers B2B
2.4.4 completes GraphQL coverage for B2B operations, including negotiable quotes — previously available only via REST. A B2B quote workflow can now run end to end through GraphQL, so a decoupled B2B front end stops being a compromise.
The wider point is a consistent API surface: shopping cart, checkout, customer accounts and B2B features all through GraphQL. Queries fetch what they ask for and nothing else, so payloads are smaller and transactions faster. And React, Vue and Next.js sit more naturally on GraphQL than on REST, which shortens the development cycle.
Security hardening
OAuth tokens and password reset tokens are encrypted in the database.
Session IDs are no longer stored in the database by default.
The deprecated email template syntax from earlier versions is gone.
Integration tokens can no longer be used for Bearer authentication by default.
None of these block an upgrade, but custom code that relies on the removed behaviour will need refactoring.
Performance beyond the runtime
AsyncOrder lets order placement run asynchronously, so backend processing delays stop showing up as a slow checkout. Database queries were profiled and optimised, and cache invalidation logic was refined to cut unnecessary misses. High-traffic merchants often see a 15-25% reduction in server load against 2.4.3, depending on workload.
Planning the upgrade
Audit your extensions. The bundled extensions were removed, Braintree excepted. Verify compatibility with 2.4.4 and plan replacements where you need them.
Review custom code against PHP 8.1 and the security changes — string handling, type strictness, deprecated functions.
Check the environment. On Adobe Cloud, PHP 8.1 is handled for you. On-premise, plan the infrastructure work.
Test properly. A full regression across checkout, payments, shipping, customer accounts, admin operations and every custom integration, plus performance testing under realistic load.
Deploy in stages. Development, staging, production, with clear success criteria at each gate and rollback ready — though for security-related changes, forward is the only safe direction.
What this means for you
2.4.4 is the baseline the later releases build on. Edge Delivery Services, deeper AI integration and composable commerce patterns all sit on the infrastructure it established. If you are on 2.4.3 or older, the question is not whether to upgrade — it is when you can give it the testing it deserves.