1 / 29

Ruslan Aharodnik

Migration from M1 to M2: How to increase your performance and decrease your headache. Ruslan Aharodnik. WELCOME FROM BELARUS. What would I talking about?. WHY TO MIGRATE?. How to increase performance?. Varnish + OPC!. FPC + SASS!. Migrate to M2!. WHAT IS THE PLAN? Preparation

eddyl
Télécharger la présentation

Ruslan Aharodnik

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Migration from M1 to M2: How to increase your performance and decrease your headache Ruslan Aharodnik

  2. WELCOME FROM BELARUS

  3. What would I talking about? WHY TO MIGRATE?

  4. How to increase performance?

  5. Varnish + OPC! FPC + SASS! Migrate to M2!

  6. WHAT IS THE PLAN? • Preparation • Migration • Testing

  7. Preparation it is better to start migration on a planned • Redesign • New functionality • New integration

  8. Preparation and Migration: integration

  9. Preparation: REFACTORING AND ARCHITECTURE REORGANISATION Two-step checkout Product attachments Elasticsearch Amazon Pay Drag-and-drop page builder B2B functionality ...

  10. WHAT IS THE PLAN? • Preparation • Migration • Testing

  11. NEW FUNCTIONALITY

  12. WHAT IS THE PLAN? • Preparation • Migration • Testing

  13. ACCEPTANCE Testing of each module separately

  14. ACCEPTANCE Testing of each module separately Overall project testing

  15. ACCEPTANCE Testing of each module separately Overall project testing Testing from a client’s side

  16. ACCEPTANCE Testing of each module separately Overall project testing Testing from a client’s side And all over again from the first stage

  17. WHAT IS THE PLAN? • Preparation • Migration • Testing

  18. PM Developer QA QA QA AS A RESULT

  19. SIDE BENEFITS • Regardless of your wish, you will have to remove all the unnecessary modules, code pieces, and other “trash” you wouldn’t even consider to deal with on a living working project. • You won’t have to migrate to Magento 2 later • You won’t have to update your server configuration to meet the M2 requirements

  20. What should QA team do? DUD ADVICES FOR M2 MIGRATION

  21. What should QA team do? DUD ADVICES FOR M2 MIGRATION • Never use Magento vanilla tools for migration along with modules - you will be good by your own efforts

  22. What should QA team do? DUD ADVICES FOR M2 MIGRATION • Never use Magento vanilla tools for migration along with modules - you will be good by your own efforts • Don’t improve the website work - just transit old modules to the new platform

  23. What should QA team do? DUD ADVICES FOR M2 MIGRATION • Never use Magento vanilla tools for migration along with modules - you will be good by your own efforts • Don’t improve the website work - just transit old modules to the new platform • Don’t test requirements and don’t perform customer acceptance - if he liked the old website, he would like the new one

  24. What should QA team do? DUD ADVICES FOR M2 MIGRATION • Never use Magento vanilla tools for migration along with modules - you will be good by your own efforts • Don’t improve the website work - just transit old modules to the new platform • Don’t test requirements and don’t perform customer acceptance - if he liked the old website, he would like the new one • Don’t combine the migration with other on-site activities - just freeze it for half a year and then perform all the updates and redesign

  25. What should QA team do? DUD ADVICES FOR M2 MIGRATION • Never use Magento vanilla tools for migration along with modules - you will be good by your own efforts • Don’t improve the website work - just transit old modules to the new platform • Don’t test requirements and don’t perform customer acceptance - if he liked the old website, he would like the new one • Don’t combine the migration with other on-site activities - just freeze it for half a year and then perform all the updates and redesign • Don’t use plugins, rework events in Magento 2 - it is a waste of time and you won’t notice the result anyway

  26. What should QA team do? DUD ADVICES FOR M2 MIGRATION • Never use Magento vanilla tools for migration along with modules - you will be good by your own efforts • Don’t improve the website work - just transit old modules to the new platform • Don’t test requirements and don’t perform customer acceptance - if he liked the old website, he would like the new one • Don’t combine the migration with other on-site activities - just freeze it for half a year and then perform all the updates and redesign • Don’t use plugins, rework events in Magento 2 - it is a waste of time and you won’t notice the result anyway • Don’t even think about B2B and B2C - why do you need extra problems?

  27. What should QA team do? DUD ADVICES FOR M2 MIGRATION • Never use Magento vanilla tools for migration along with modules - you will be good by your own efforts • Don’t improve the website work - just transit old modules to the new platform • Don’t test requirements and don’t perform customer acceptance - if he liked the old website, he would like the new one • Don’t combine the migration with other on-site activities - just freeze it for half a year and then perform all the updates and redesign • Don’t use plugins, rework events in Magento 2 - it is a waste of time and you won’t notice the result anyway • Don’t even think about B2B and B2C - why do you need extra problems? • Hire a fully fresh team for Magento 2 migration - new people will bring new opinions on what you really need

  28. Thank you for attention!

More Related