The starting point for Developers at Zalando

1. The starting point for Developers at Zalando

2. ABOUT ME Levi Ferreira Head of ML Platform & Developer Productivity @ Zalando - Former Engineering Manager for Sunrise @ Zalando - Ex Shopify, Ex Rocket Internet Linkedin: linkedin.com/in/leviferreira/

3. Zalando. The Starting Point for Fashion. 3

4. This is Zalando We take the lead in European fashion. 14.7 bn Euro GMV >50 m Active Customers >5,800 Brands 4

5. Platform The power of platform Partner Program Fashion Store Marketing Services Lounge Fulfillment Solutions Outlets Connected Retail 5

6. SOFTWARE PRODUCT DEVELOPMENT AT ZALANDO 5 tech hubs Across Europe > 2,000 > 220 employees In Tech From > Nations 100 Cross-functional, Agile Delivery Teams

7. > 4000 Services 7

8. So what exactly is Sunrise?

9. History: Developer Console

10. Technology built in-house at Zalando Mosaic: https://www.mosaic9.org/

11. Why move away from existing Developer Console ? - Onboarding experience was difficult: Learning Curve was too high for other teams to contribute - Not easily composable + + - Not possible to share components + - Generated a fragment internal developer tooling product landscape + Easy to onboard new teams to provide Plugins Easily composable Shareable components Standardization of Software patterns, Architecture + Design

12. Sunrise is the daily starting point for Builders Software & Data Engineers & Managers Applied & Data Scientists Project, Program, & Product Managers & designers 󰟲 󰞅 Fragmented Experience 😃 Builder Happiness 😃 🚀 Builder Productivity 🚀 🔍 Discoverability 🔍 🙌 Collaboration 🙌 🧰 Usability 🧰

13. Sunrise is the daily starting point for Builders Sunrise centralizes all ● ● ● Tooling Information & access to Resources which are necessary for building & operating digital products. Presenting this content in a ● ● ● Consistent Accessible and Beautiful way so that it is both discoverable and easy to use. 🤔

14. Sunrise is a Platform Sunrise is a Multi-sided, expandable platform, collaboratively built through various methods in Zalando’s premise contribution model. ● Easy integration ● Improves delivery speed ● Interoperability ● Effortless connection to customers ● Behavioral insights As a user, your engagement incentivises Providers of Software Development & Data tooling to integrate. Mission to integrate the entire Builder experience by the end of 2023.

15. How are we doing so far 15 49% 78.4% 100% Engineers Daily Active Engineers Weekly Active Engineers Monthly Active + 300 non-engineers 65% 99 36 Share of Landscape Integrated Contributors across Zalando Self-built plugins

16. HOMEPAGE

17. SIDEBAR

18. SEARCH

19. TALK TO SUNRISE

20. TALK TO SUNRISE

21. SEARCH APPLICATIONS

22. SEARCH APIS opensource.zalando.com/restful-api-guidelines/

23. APPLICATIONS

24. APPLICATION DETAILS

25. APPLICATION DETAILS

26. CONTINUOUS DELIVERY PLATFORM

27. DEPLOYMENT

28. CI/CD INSIGHTS

29. DOCUMENTATION (MKDOCS)

30. API DEPENDENCIES

31. APPLICATION EVENT PUB/SUB

32. INFRASTRUCTURE ACCOUNTS

33. RELIABILITY CENTER

34. TEAMS

35. PEOPLE

36. APPLICATION TEMPLATES

37. CREATING A NEW SERVICE

38. Machine Learning Platform

39. PRODUCT PORTFOLIO

40. SUPPORT

41. TECH RADAR opensource.zalando.com/tech-radar/

42. Challenges & Learnings

43. Challenges 1. Small Team 2. Team was largely unfamiliar with Typescript 3. Backstage under heavy developments - frequent changes involving lot of refactoring and updates 4. Abstractions and improvements were not well-defined. 5. Lots of throwaway code and temporary workarounds 6. Tooling and dependencies - configuring and keeping them to a minimum

44. What Helped? 1. The Backstage community was extremely helpful ! 2. Core abstractions - Entities, plugins, Apis are solid and make it easy to evolve code independently 3. Very iterative development - Making even 5-6 deployments per day. 4. Well-defined goals and achievables 5. Having a community driven software meant a lot of bugs were detected and fixed by others in the community before we could even file an issue.

45. Learnings 1. Small central teams can deliver a lot of value utilising the platform 2. Have well defined outcomes and clear deadlines. 3. Leverage types to keep code size from being a problem. 4. Trust first approach - Assume that other contributing teams have their best interests at heart and build towards a common goal. 5. Contribution guidelines on the principles and policies of contribution is very important. 6. Introduce Quality Gates to ensure superb metadata health.

46. Q&A