Developer Experience

Size: px

Start display at page:

Download "Developer Experience"

Stewart Waters
6 years ago
Views:

2 Developer Experience

3 Max Yekaterynenko Director of Community

4 Discover Install Design Develop Integrate Deploy Engage Maintain Monetize

5 Discover Install Design Develop Integrate Deploy Engage Maintain Monetize

6 Discover

7 Discover Install Design Develop Integrate Deploy Engage Maintain Monetize

9 Install

10 Install

16 Install

17 Discover Install Design Develop Integrate Deploy Engage Maintain Monetize

18 Design and Develop

19 Design and Develop

20 Design and Develop

21 Discover Install Design Develop Integrate Deploy Engage Maintain Monetize

22 Integrate

23 Integrate $ composer require fooman/printorderpdf-m

24 Discover Install Design Develop Integrate Deploy Engage Maintain Monetize

25 Deploy Development Staging Production Install DB Compile Deploy Static Install/Upgrade DB

26 Discover Install Design Develop Integrate Deploy Engage Maintain Monetize

27 Discover Install Design Develop Integrate Deploy Engage Maintain Monetize

28 Discover Install Design Develop Integrate Deploy Engage Maintain Monetize

29 Community Engineering

30 Team

31 Goals Enable Community Ease contribution Transparency

32 Issues Upvote - Thumb Up GitHub Issues

33 Upvote - Thumb Up GitHub Issues

34 GitHub Pull Requests

37 Thank you! Q&A Max

39 State of Art Architecture of Magento 2

40 Max Yekaterynenko Director of Community

41 Goals for Magento Platform Improve platform performance Reduce complexity Increase code consistency Reduce extension conflicts

42 Magento MVC & CQRS

43 Model-View-Controller MVC came from client applications

44 Fat client - MVC Presentation is separate from Model State modification is separate from retrieval

45 Command & Query Responsibility Segregation (CQRS)

46 Incorrect Server MVC Separation of Presentation from Model is preserved Violates HTTP (CQRS) State modification is done by same infrastructure as state retrieval (violates CQRS)

47 Improved but still Incorrect Server MVC Separation of Presentation from Model is preserved Obeys HTTP State modification is done by same infrastructure as state retrieval

48 Correct Server MVC Separation of Presentation from Model is preserved Obeys HTTP State modification and retrieval is partly done by different infrastructures

49 Correct MVC with CQRS Separation of Presentation from Model is preserved Obeys HTTP State modification and retrieval is done by different infrastructures

50 CQRS Separate Query API & Command API Command API optimized for write, have business logic Query API optimized for read, cacheable Query actualization through indexing

51 Persistence

52 Persistence class AbstractModel { /** */ public function save() // } /** */ public function delete() //

53 Persistence Persistence of entities should be separate from entities (element of DDD) $this->productresourcemodel->save($product);

54 Service Interfaces class ProductRepository implements ProductRepositoryInterface { public function createproduct (ProductInterface $product) { // logic } }

55 Data Interfaces interface ProductInterface { public function getsku(); public function setsku(); public function getname(); public function setname(); // only getters & setters }

56 Service Contract Service Contracts expose procedural API

57 Persistence OOP does not work well with Microservices No logic on models Persistence just mapping data transfer objects to DB

58 Customer Data and Sessions

59 Request Flow Customer-agnostic content (all routes) Customer Data API (/sections/ )

60 Customer Data No session usage in blocks Only Sections Controller knows about session

61 Inheritance Based API

62 Code Reuse Parent Trait Facade Class Method Behavior Dependency Private

63 Inheritance Problems Misused in 99% of cases Child depends on parent construct() Static coupling can t substitute/decorate parent Performance problem: all parent dependencies are inherited Product Model

64 Inheritance Based on APIs Model -> DTOs Resource Model -> Data Mapping Collection -> Query API Block -> Interface subtyping Controller -> Interface subtyping

65 Classes vs Namespaces

66 Classes vs Namespaces class IndexController { public function firstaction() { // } } public function secondaction() { // }

67 Classes vs Namespaces class IndexController { public function construct($dependencya, $dependencyb) // public function firstaction() { $this->dependencya->dosmth(); } } public function secondaction() { $this->dependencyb->dosmth(); }

68 Classes vs Namespaces class First implements Magento\Framework\App\ActionInterface { public function construct($dependencya) // } public function execute() { $this->dependencya->dosmth(); }

69 Continuing impromenets

70 Focus Continue applying CQRS on framework level Continue Micro-service-ready approach Continue Moving session management to browser Discourage Inheritance and abandon Inheritance-based APIs Stop using classes as namespaces Separate configuration from code

71 Thank you! Q&A Max

Magento Technical Guidelines

Magento Technical Guidelines Eugene Shakhsuvarov, Software Engineer @ Magento 2018 Magento, Inc. Page 1 Magento 2 Technical Guidelines Document which describes the desired technical state of Magento 2