![PRACTICAL EXAMPLE: SALES ORDERS AND STYLE PERFORMANCE
50
PLM B2B
Sales
Systems
• An order is requested in the B2B
systems [Status: Pending]](https://image.slidesharecdn.com/cloudcomputingintheenterprise-181121123856/85/Cloud-Computing-in-the-Enterprise-50-320.jpg)
![PRACTICAL EXAMPLE: SALES ORDERS AND STYLE PERFORMANCE
51
PLM B2B
Sales
Systems
• An order is requested in the B2B
systems [Status: Pending]
• The request is committed in the
B2B fractal and a Local Event is
fired. [Status: Pending]](https://image.slidesharecdn.com/cloudcomputingintheenterprise-181121123856/85/Cloud-Computing-in-the-Enterprise-51-320.jpg)
![PRACTICAL EXAMPLE: SALES ORDERS AND STYLE PERFORMANCE
52
PLM B2B
Sales
Systems
• An order is requested in the B2B
systems [Status: Pending]
• The request is committed in the
B2B fractal and a Local Event is
fired. [Status: Pending]
• Sales systems perform the required
checks and operations and fires an
Enterprise Event [Status:
Pending]](https://image.slidesharecdn.com/cloudcomputingintheenterprise-181121123856/85/Cloud-Computing-in-the-Enterprise-52-320.jpg)
![PRACTICAL EXAMPLE: SALES ORDERS AND STYLE PERFORMANCE
53
PLM B2B
Sales
Systems
• An order is requested in the B2B
systems [Status: Pending]
• The request is committed in the
B2B fractal and a Local Event is
fired. [Status: Pending]
• Sales systems perform the required
checks and operations and fires an
Enterprise Event [Status:
Pending]
• Both PLM and B2B fractals receive
the Enterprise Event and update
their state [Status: Approved]](https://image.slidesharecdn.com/cloudcomputingintheenterprise-181121123856/85/Cloud-Computing-in-the-Enterprise-53-320.jpg)
![CONWAY’S LAW
60
Organizations which design systems [...] are constrained to
produce designs which are copies of the communication
structures of these organizations.
”
”- Melvin Conway](https://image.slidesharecdn.com/cloudcomputingintheenterprise-181121123856/85/Cloud-Computing-in-the-Enterprise-60-320.jpg)
Cloud Computing in the Enterprise
- 1. 13.11.2018 CLOUD COMPUTING IN THE ENTERPRISE
- 2. ANGELO AGATINO NICOLOSI 2 https://dk.linkedin.com/in/anicolosi
- 3. OUR DREAM: AGILE ENTERPRISE 3
- 4. HOW TO GET THERE Cloud Computing Evolutionary Architecture Engineering Culture 4
- 10. Operative System Container Engine OS App OS App OS App VIRTUALIZATION Operative System Application App App App App App App
- 13. Hypervisor OS App OS App OS App CLOUD COMPUTING App App App App App App Operative System Container Engine OS App OS App OS App App App App App App App OS App OS App OS App Hypervisor OS App OS App OS App
- 14. CLOUD COMPUTING Hardware Hardware Hardware Hardware Virtualization Virtualization Virtualization Virtualization OS OS OS OS Containers Containers Containers Containers Runtime Runtime Runtime Runtime Applications Applications Applications Applications Functions Functions Functions Functions IaaS CaaS PaaS FaaS Unit of Scale Vendor Customer
- 15. CLOUD DEMO 15
- 16. HOW TO GET THERE Cloud Computing Evolutionary Architecture Engineering Culture 16
- 17. OUR DREAM: AGILE ENTERPRISE 17
- 18. TO BE ABLE TO ADAPT TO CHANGE IS VERY IMPORTANT 18 It is not the most intellectual of the species that survives, nor the strongest that survives. It is the one that is most adaptable to change. ” ”- Leon C. Megginson on Darwin’s Origin of Species
- 19. THE MONOLITH 19
- 20. THE MONOLITH 20
- 21. EVOLUTIONARY ARCHITECTURE 21 An evolutionary architecture designs for incremental change in an architecture as a first principle. ” ”- Neal Ford and Rebecca Parsons
- 23. MICROSERVICES AS EVOLUTIONARY ARCHITECTURE 23
- 25. UNDERSTANDING MICROSERVICES 25 Application Programming Interface
- 26. APIS: HOW DOES IT LOOK LIKE? HTTPS://PETSTORE.SWAGGER.IO/#/26
- 27. UNDERSTANDING MICROSERVICES API GATEWAY 27 API Gateway
- 28. 12 FACTORS APPS HOW TO CREATE MICROSERVICES RIGHT 28
- 33. TOLERANT READER PATTERN POSTEL'S LAW 33 Be conservative in what you do, be liberal in what you accept from others. ” ”- Jon Postel
- 34. REACTIVE MANIFESTO HOW TO CREATE MICROSERVICES RIGHT 34 Producer Consumer
- 35. REACTIVE MANIFESTO HOW TO CREATE MICROSERVICES RIGHT 35 Producer Consumer• Message driven
- 36. REACTIVE MANIFESTO HOW TO CREATE MICROSERVICES RIGHT 36 Producer Consumer• Message driven Supervisor
- 37. REACTIVE MANIFESTO HOW TO CREATE MICROSERVICES RIGHT 37 Producer• Message driven • Elastic Consumer Supervisor
- 38. REACTIVE MANIFESTO HOW TO CREATE MICROSERVICES RIGHT 38 Producer• Message driven • Elastic Consumer Supervisor Consumer 2
- 39. REACTIVE MANIFESTO HOW TO CREATE MICROSERVICES RIGHT 39 Producer• Message driven • Elastic Consumer Supervisor Consumer 2Workflow Processor
- 40. REACTIVE MANIFESTO HOW TO CREATE MICROSERVICES RIGHT 40 Producer• Message driven • Elastic • Resiliant • Responsive Consumer Supervisor Consumer 2Workflow Processor Flow Monitor
- 41. BACKEND FOR FRONTEND (BFF) FRONTEND ARCHITECTURE 41 API Gateway
- 42. BACKEND FOR FRONTEND (BFF) FRONTEND ARCHITECTURE 42 API Gateway
- 43. BACKEND FOR FRONTEND (BFF) FRONTEND ARCHITECTURE 43 API Gateway BFF
- 44. DEMO: SINGLE PAGE APPLICATION FRONTEND ARCHITECTURE 44
- 47. FRACTAL - DEFINITION MICROSERVICES FOR THE ENTERPRISE 47 A fractal is a self-sufficient, secured and isolated platform composed of a set of services supporting any number of external or internal applications that resides within the same enterprise business domain.
- 48. - It has a single inbound (API Gateway) and a single outbound (Integration) network microsegment. - Microservices in the API Gateway and Integration Context are completely stateless (regarding the transactions/requests). - It segregates business domains in different microsegments of network - Synchronous communication is discouraged (besides for data queries). - Mutual TLS everywhere microsegments are crossed. - Authorization through JWTs SOME DETAILS Security Business DomainsBusiness DomainsBusiness Domains API Gateway Integration
- 49. FRACTAL ARCHITECTURE EVOLUTIONARY ARCHITECTURE AT SCALE 49 L O C A L E N T E R P R I S E
- 50. PRACTICAL EXAMPLE: SALES ORDERS AND STYLE PERFORMANCE 50 PLM B2B Sales Systems • An order is requested in the B2B systems [Status: Pending]
- 51. PRACTICAL EXAMPLE: SALES ORDERS AND STYLE PERFORMANCE 51 PLM B2B Sales Systems • An order is requested in the B2B systems [Status: Pending] • The request is committed in the B2B fractal and a Local Event is fired. [Status: Pending]
- 52. PRACTICAL EXAMPLE: SALES ORDERS AND STYLE PERFORMANCE 52 PLM B2B Sales Systems • An order is requested in the B2B systems [Status: Pending] • The request is committed in the B2B fractal and a Local Event is fired. [Status: Pending] • Sales systems perform the required checks and operations and fires an Enterprise Event [Status: Pending]
- 53. PRACTICAL EXAMPLE: SALES ORDERS AND STYLE PERFORMANCE 53 PLM B2B Sales Systems • An order is requested in the B2B systems [Status: Pending] • The request is committed in the B2B fractal and a Local Event is fired. [Status: Pending] • Sales systems perform the required checks and operations and fires an Enterprise Event [Status: Pending] • Both PLM and B2B fractals receive the Enterprise Event and update their state [Status: Approved]
- 54. PRACTICAL EXAMPLE: SALES ORDERS AND STYLE PERFORMANCE 54 PLM B2B Sales Systems • Why do we use Local Events instead of simple queues? Audit
- 55. MULTI-CLOUD EVOLUTIONARY ARCHITECTURE AT SCALE 55
- 56. SECURITY & COMPLIANCE 56 Security Business DomainsBusiness DomainsBusiness Domains API Gateway Integration • The Enclave setup helps minimizing the blast radius in case of attacks. • Moreover, with the concept of EUP Ticket, cross platform communication is much more complicated to misuse
- 57. MUST HAVE EVOLUTIONARY ARCHITECTURE AT SCALE 57
- 58. TOOLS 58
- 59. HOW TO GET THERE Cloud Computing Evolutionary Architecture Engineering Culture 59
- 60. CONWAY’S LAW 60 Organizations which design systems [...] are constrained to produce designs which are copies of the communication structures of these organizations. ” ”- Melvin Conway
- 61. CONWAY’S LAW 61
- 62. INVERSE CONWAY MANEUVER BUILD TEAMS THAT LOOK LIKE THE ARCHITECTURE YOU WANT 62
- 63. DEVOPS 63
- 64. CONTINUOUS INTEGRATION & CONTINUOUS DELIVERY 64
- 65. SECOPS 65
- 66. INNERSOURCING 66
Editor's Notes
- #3: Angelo, worked in several companies during my carreer. Both in start-ups and large enterprises. About the latter, I have been in Danske Bank for 7 years where I grew from IT Developer to Head of Software Engineering. Recently I joined BESTSELLER, one of the leaders in the Fashion Business.
- #4: Our dream was the one shared by any other enterprise: to bring the way of working and time to market you can have in start-ups while having the amazing challenges that only the enterprise world can offer you. From this the need for a higher degree of agility.
- #18: Our dream was the one shared by any other enterprise: to bring the way of working and time to market you can have in start-ups while having the amazing challenges that only the enterprise world can offer you. From this the need for a higher degree of agility.
- #28: Hide internal implentation Security, monetization, etc. Still: synchronous communication
- #33: Hide internal implentation Security, monetization, etc. Still: synchronous communication
- #48: We started to define a set of best practices that then, based on input from our experiences in production, turned into a full blown architecture description.