Magento 2.0 By Ghulam Murtaza Why Magento 2.0 1 Modernize web technology stack 1.1 PHP 5.4 will be the minimum requirement with support available upto PHP 5.5 1.2 MySql 5.6 1.3 CSS3 1.4 jQuery 1.5 UI library introduced. Magento 2 offers a complete UI library build up on LESS to match the specific system requirements. 1.6 RequireJS: It helps load JS resources asynchronously 2 Imporoved performace and scalability (in both CE and EE) 2.1 Improve indexers 2.2 Varnish 2.3 Full Page cache (in both CE and EE) 2.4 RDBMS Tabular Structure in new sections to avoid EAV slowness 2.5 Changes to increase the number of concurrent admin users 2.6 Area FrontName is fast and easy way to identify requested Area (See #6) 3 Easy customization 3.1 Component Oriented Architecture: (Module under one directory). In magento1.x we have multiple folders for a module like app/code/code pool, design/vendor/theme and skin etc. In magento 2 they have added module under one folder. 3.2 Unlimited theme inheritance: New layouts can be easily created by overwriting the elements of an inherited theme. 1.3.3 Reduce code coupling: ‘Mage’ class doesn’t exist anymore and broken down into many smaller ones. 3.4 Improve search: Magento 2 includes a modularized search interface and layered navigation so it is easier to customize search functions. 3.5 Ability to disable a feature without affecting the consistency of other features. 3.6 Speed translation efforts: il8n localization dictionaries are streamlined without module-specific configuration. 3.7 Better Error reporting for XML files: Implementation of XML configuration in the file schema validation. 3.8 Blank theme: To further support frontend projects, Magento 2 includes a Blank Theme. It is a great starting point for new theme development because it is devoid of specific customizations and contains useful examples for frontend developers. It allows developers to start with a stripped down version of the theme, and then simply add features and customizations that they want or need. 4 High code quality and testing framework 4.1 Integration Testing(framework) 4.2 Unit Testing 4.3 Static Testing 4.4 Performance Testing 4.5 JavaScript Testing 4.6 Performance test scripts 5 Clear installation and upgrades (Lower upgrade costs and efforts) 5.1 Installing Magento 2 via Composer, there will be a product version for the users and a software version with the Semantic Versioning standard. 5.2 Resue 3rd party extensions without bundling themw ith source code. 5.3 Component based architecture 5.4 Magento Connect will be Composer based as well. 6 Separate business logic from presentation. 6.1 Magento Area Introduction: New concept of presentation layer in Magento 2. its a layer that contains user oriented functionality, which is responsible for managing user interaction with the system, and consists of components that provide a common bridge into the core business logic encapsulated in the domain logic layer. we can disable area without having affect on other module 6.2 Request dispatching process changes - Upgrading to Magento 2.0 1) Data like users, products and orders can be migrated using export and import. 2) Themes and extensions have to be recreated (at least there is not any mechanism issued by magento 2.0) - Critics 1) Its already very late and in zf1. 2) almost 60% of new features are already there on magento connect in form of free or paid extensions. 3) Upgradting from magent 1.0 is seems difficult except data migration. References: https://wiki.magento/display/MAGE2DOC/Magento+2+Development+Updates dckap/blog/sneak-peek-into-the-features-of-magento-2/ https://alankent.wordpress/2014/08/02/magento-2-progress-towards-installation-via-composer/ Murtaza is a Web Team Lead @ Coeus Solutions GmbH
Posted on: Tue, 23 Dec 2014 13:18:00 +0000
Trending Topics
Recently Viewed Topics
© 2015