Evolve 19 | Kevin Campton & Sharat Radhakrishnan | Industry Focus | Autodesk - Year 6 AEM Update

Information about Evolve 19 | Kevin Campton & Sharat Radhakrishnan | Industry Focus |...

Published on August 16, 2019

Author: evolve_conference

Source: slideshare.net

Content

1. #evolve19 AUTODESK AEM JOURNEY- 6TH YEAR UPDATE Sharat Radhakrishnan, Platform Architect Kevin Campton, Principal DevOps Engineer

2. #evolve19 2 Autodesk is a leader in 3D design, engineering and entertainment software. If you’ve ever driven a high-performance car, admired a towering skyscraper, used a smartphone, or watched a great film, chances are you’ve experienced what millions of Autodesk customers are doing with our software. AUTODESK

3. #evolve19 EDUCATION COMMUNITY • EVENTS, LEARNING, FREE SOFTWARE DOWNLOAD • MICROSITES AUTODESK & AEM AUTODESK.COM • 150K+ LIVE PAGES • 22 LANGUAGES & 42 LOCAL SITES • 500+ USERS ON AUTHOR 201 3 201 4 201 5 201 6 201 7 ONLINE STORES • NORTH AMERICA • EUROPE IN-PRODUCT • WEB EXPERIENCES INSIDE 160+ SOFTWARE PRODUCTS • MARKETING, ECOMMERCE, LICENSE SUPPORT ECOMMERCE EXPANISION • ASIA-PACIFIC • EMERGING MARKETS 7 Sprint teams1M+ lines of code

4. #evolve19 4 1. Headless CMS + Headless Commerce 2. Adoption of Inner-source 3. Fully automated on-demand deployments KEY ACHIEVEMENTS IN THE LAST YEAR

5. #evolve19 5 Goals: 1. Increase time-to-market on all eCommerce features 2. Less reliance on engineering teams for front-end changes 3. Personalization and A/B tests at scale 4. Best out of AEM + Best out of Microservices + Best out of ReactJS 1. HEADLESS CMS + HEADLESS COMMERCE

6. #evolve19 6 1. HEADLESS CMS + HEADLESS COMMERCE WWW Deskto p Apps mobil e apps MICRO-SERVICES FOR E- COMMERCE CONTENT AS APIS FRONT-END APPLICATIONS AEM COMPONENT LIBRARY REST APIS

7. #evolve19 7 CHECKOUT EXPERIENCE Web Desktop App (In- product) MICRO- SERVICES FOR COMMERCE CONTENT AS APIS FROM AEM EXPERIE NCE Sales Agent Portal Cart Account Sign- in Payment Methods Review & Completion REACTJS LIBRARY

8. #evolve19 8 EXAMPLE Offering API AEM ComponentAUTHOR ENABLED CONTENT AS JSON Cart Persistence API * Redux to manage state & flows between components React Cart Component for New Subscription product:

9. #evolve19 9 • Key Challenge: • How can we sustainably re-use and maintain common code and yet allow for independent development? • Solution: • Enable Open-source culture and workflows: • Any developer can contribute to artifacts. Pre-defined code standards enforced through automation • Any team can consume and extend versioned artifacts 2. INNER SOURCE 250+ software engineering teams at Autodesk. 7 teams focused on AEM ecosystem More than 1 million lines of custom code for AEM ecosystem Multiple AEM Stacks

10. #evolve19 10 Examples: • AEM Author Widget Library • AEM – Hashicorp Vault Integration (Secret Management) • React Component Library • UI Style Guides • AEM – SSO Integration • more to come.. • AEM – Akamai CDN Integration • AEM Custom Workflows • User group definitions in Github 2. INNER SOURCE AND AEM

11. #evolve19 11 3. FULLY AUTOMATED ON-DEMAND DEPLOYMENTS Before: 1. Functional Code 2. Unit tests Now: 1. Functional Code 2. Unit tests 3. Mock based integration tests 4. API Contract tests 5. Browser Automation tests 6. Build workflow as code 7. Feature Flag 8. Monitoring instrumentation as code: • Real-user • Synthetic • Application WHAT’S INSIDE A PULL REQUEST FOR CODE COMMIT? Every code commit is releasable to live users right away

12. #evolve19 12 HOW DID WE GET THERE?

13. #evolve19 13 1. Consumer-driven API contract documentation 2. Parallel execution of browser/mobile tests 3. Utilizing Docker build containers and test containers 4. Release metadata management 5. Infrastructure creation for AEM and build systems 6. Self Service tools 1. AUTOMATION, AUTOMATION, AUTOMATION

14. #evolve19 14 • Extensive training and Jenkins Pipeline onboarding to the engineers • Developers’ local setup is identical to release pipeline • Self-service AEM stack dispenser for local development • Developers accountable for all tests – unit, integration, performance, browser, etc • Developers can deploy to Prod anytime • No release engineers. No release planning • Multiple deployment surfaces for Development 3. SELF SUFFICIENT TEAMS

15. #evolve19 15

16. #evolve19 16

17. #evolve19 17 Mo MO Monitoring dashboard

18. #evolve19 18 1. Roll-out on-demand release workflow to the last remaining AEM Stack 2. AEM 6.5 Upgrade 3. Real-time Analytics driven user journey orchestration 4. Automated load tests on every commit 5. Continue enhancements to CI/CD tools IN THE PIPELINE FOR THIS YEAR

19. #evolve19 19 ABOUT US Kevin Campton Principal DevOps Engineer Autodesk [email protected] Sharat Radhakrishnan Platform Architect Autodesk [email protected]

20. #evolve19 THANK YOU!

#evolve19 presentations

Related presentations


Other presentations created by evolve_conference