Diese Präsentation wurde erfolgreich gemeldet.

Outlook on Magento 2

2

Teilen

Wird geladen in …3
×
1 von 23
1 von 23

Outlook on Magento 2

2

Teilen

Herunterladen, um offline zu lesen

If you already worked with the e-commerce software Magento you know it's the same as with folk music or Bayern Munich: you either love it or you hate it. The reason for this is that Magento is both flexible and complex, resource intensive and very capable. Plus it's about 7 years old now and still it's one of the (if not the) most popular cart softwares. But behold! Finally, Magento 2 is on the horizon and should be available by the end of the year. Let's have a look at the foundation of Magento 2, its current state and when you may want to use it.

If you already worked with the e-commerce software Magento you know it's the same as with folk music or Bayern Munich: you either love it or you hate it. The reason for this is that Magento is both flexible and complex, resource intensive and very capable. Plus it's about 7 years old now and still it's one of the (if not the) most popular cart softwares. But behold! Finally, Magento 2 is on the horizon and should be available by the end of the year. Let's have a look at the foundation of Magento 2, its current state and when you may want to use it.

Weitere Verwandte Inhalte

Ähnliche Bücher

Kostenlos mit einer 14-tägigen Testversion von Scribd

Alle anzeigen

Ähnliche Hörbücher

Kostenlos mit einer 14-tägigen Testversion von Scribd

Alle anzeigen

Outlook on Magento 2

  1. 1. Outlook on Magento 2 Matthias Zeis 13. Magento-Stammtisch Wien | Vienna PHP User Group „Ecommerce“ Meetup 18.05.2015
  2. 2. 2 Profile  Magento since 2009  Magento Blog 2010  Magento Certified 2011  Magento Meetup 2012  @mzeis  matthias-zeis.com
  3. 3. 3 LimeSoda  Founded 2002  Based in Vienna  Magento since 2009  25+ people  We‘re looking for you! limesoda.com/jobs/
  4. 4. 4 MAGENTO Do you know it / work with it?
  5. 5. 5 Magento  Most used E-Commerce software  Released 2008  Bought by eBay 2011  Open Source  Community Edition  Enterprise Edition http://www.datanyze.com/market-share/e-commerce-platforms/Alexa%20top%201M
  6. 6. 6 Magento  PHP & MySQL  OOP  Configuration over convention  XML configuration  PrototypeJS + jQuery  Very flexible  Complex http://www.datanyze.com/market-share/e-commerce-platforms/Alexa%20top%201M
  7. 7. 7 Magento  Multiple stores  Multiple languages  Multiple currencies  Multiple designs  Responsive theme  Common e-commerce & marketing features  Integration with other systems http://www.datanyze.com/market-share/e-commerce-platforms/Alexa%20top%201M
  8. 8. 8 WHY MAGENTO 2? If everything is so great…
  9. 9. 9 Why Magento 2?  Well… 2008!  Legacy code  Dependencies between modules  No automated tests  No Dependency Injection (DI)  No Composer, but PrototypeJS, …  Time has moved on!  Performance  Upgrades & Stability  Competition
  10. 10. 10 Goals for Magento 2 https://twitter.com/IgorKuzyk/status/545596886447427587
  11. 11. 11 Timeline https://twitter.com/ronpeled/status/545598115110088704
  12. 12. 12 Public repository at GitHub github.com/magento/magento2
  13. 13. 13 Documentation devdocs.magento.com
  14. 14. 14 Automated testing & CI travis-ci.org/magento/magento2
  15. 15. 15 Tech Stack  PHP 5.5, 5.6 & HHVM 3.6  Will be compatible with PHP 7  MySQL 5.6  Symfony, Zend Framework 2 & 1  jQuery, RequireJS  LESS, Grunt
  16. 16. 16 Composer
  17. 17. 17 Architecture changes  Convention over configuration (a bit more)  Dependency Injection (DI)  Aspect Oriented Programming (AOP)  Service contracts  Versioned & stable API
  18. 18. 18 Service contracts © Magento http://devdocs.magento.com/guides/v1.0/extension-dev-guide/service-contracts/service-contracts.html
  19. 19. 19 Good  Modern tech stack  Automated tests  Best practices  More community contribution  More documentation  Faster
  20. 20. 20 Not so good  Not real TDD (only for „new“ code)  Code still in refactoring (will go on until GA)  Not easier than Magento 1 (but maybe less pitfalls)  Manual migration from M1 to M2 (some tools available)  Not much/everywhere faster (they focus on that now)
  21. 21. 21 When should you look at M2?  Looking and playing around?  Now  Use in production?  >= 2016  Client budget?  >= 20 man-days (you don‘t just want a standard shop, right?)  Hosting?  Not your € 5 shared space
  22. 22. Questions?
  23. 23. Thank you! @mzeis limesoda.com/jobs/matthias-zeis.com

×