Date post: | 08-Feb-2017 |
Category: |
Technology |
Upload: | session-digital |
View: | 230 times |
Download: | 3 times |
‣ A complete re-write? ‣ A series of refactoring? ‣ A re-architecture? ‣ A critical review?
What is Magento 2 ...
‣ Frontend themes ‣ Backend code ‣ Architecture changes ‣ Technology stack
What are the major changes?
‣More XML ‣RequireJS ‣CSS + LESS ‣Composer ‣Object Orientation ‣ Aspect Orientation ‣Design Patterns ‣ Varnish
What new skills will a team need?
‣ Improved admin UX ‣Responsive admin screens for mobile and tablet ‣Modern development tooling ‣ Service contracts ‣ Performance ‣ Scalability opportunities ‣Reduced upgrade impact ‣ Strict extension validation and certification ‣Greater compatibility and opportunity to use more existing solutions
New Features
‣ Further scalability capability with adoption of elastic search ‣Reduced reliance on caches ‣Quicker product updates to the website
‣Cloud compatibility ‣Close integration with separate OMS product ‣Close integration with separate EPOS product
Roadmap
‣ Vendor support for 3 years following M2 general availability ‣ Existing development skills and technical partners will be retained ‣Module vendors support will have individual SLAs
Magento 1
‣ Product enhancements and wider features as they are delivered ‣Greater performance and stability ‣Higher degree of integration and extension stability
What would an upgrade offer?
‣Much of the learning encapsulated by your existing systems can be translated to M2 ‣ The theme will need to be refactored heavily ‣Module vendors are working to deliver compatible modules for M2 ‣ Existing modules can be adapted to M2
Can I reuse any of my existing system
‣ Approach it like a legacy project rather than a new build ‣ Identify the value in your current system ‣ Prioritise the features that bring the most ROI ‣Maximise the impact ‣ Focus on value parity not feature parity
How much effort will an upgrade be?