Magento Enterprise Edition (MEE) 1.13 has been released and is now available in Australia for deployment or upgrade. Here are some of Balance Internet’s must know and thoughts about MEE 1.13.

Melbourne, Australia
By James Horne
Solutions Architect and Managing Director of Balance Internet

The focus of the MEE 1.13 upgrade was performance and scalability improvements, as well as a number of smaller security enhancements.  MEE 1.13 has scaled Magento to handle increased traffic volumes, larger peak concurrent users and improve the usability of the administration functions under load.

When comparing MEE to other Tier 1 platforms a common view in the market was that MEE lacked scalability, performance and security the intent of MEE 1.13 was to address these concerns and improve the engine of the ecosystem. As 1 of the 3 global Magento Gold Partner’s involved in the Beta stage of MEE 1.13 our geeks 🙂 (sorry lads) were super impressed with the improvements especially in the re-indexing area.

In summary, the following has been upgraded in MEE 1.13 to improve performance and scalability:

  • Most indexing processes now run only to update products, categories, URL redirects, and so on that have changed eliminating the need for manual full reindexing
  • Additional option of using Redis NoSQL for cache and session storage in multi-host deployments (recommended for new deployments)
  • Full page caching now invalidates only pages that are affected by product or category changes
  • Optimized cache adapters for single-server systems
  • Elimination of many types of database deadlocks
  • Major overhaul of tax calculation formulas, correction of rounding errors, and additional assistance with configuration

Further to this, these additional security enhancements have been added to ensure peace of mind for all retailers:

  • The Magento Admin Panel and web stores does not allow web browsers to store user names or passwords.
  • The Magento web store has additional Cross Site Request Forgery (CSRF) protections, meaning an imposter can not impersonate a newly registered customer and perform actions on the customer’s behalf.
  • The cryptographic methods used to store passwords were improved to enhance security.

We are recommending all our clients consider upgrading to MEE 1.13, particularly if they are in MEE 1.12 as this IS not a too large of task particularly if the level of customisation and alteration to the Core is minimal.