Scaling Architecture @ Zalando Felix Mller - @fmueller_bln About - - PowerPoint PPT Presentation

▶

Sep 08, 2023 413 likes •1.12k views

Scaling Architecture @ Zalando Felix Mller - @fmueller_bln About me Software Architect @ Zalando Software Engineer by heart 8 years in IT 2 years as an Architect Twitter: @fmueller_bln Zalando Who knows Zalando? 2008 2 monoliths...

SLIDE 1

Scaling Architecture @ Zalando

Felix Müller - @fmueller_bln

SLIDE 2

About me

Software Architect @ Zalando Software Engineer by heart 8 years in IT 2 years as an Architect Twitter: @fmueller_bln

SLIDE 3

Zalando

SLIDE 4

Who knows Zalando?

SLIDE 5

2008

SLIDE 6

2 monoliths...

SLIDE 7

2015

SLIDE 8

How big are we now?

SLIDE 9

Zalando in Numbers

~ EUR 3 billion revenue > 160m visits per month > 11000 employees in Europe ~ 1600 tech employees 7 tech hubs: Berlin, Dublin, Helsinki...

SLIDE 10

Still growing rapidly

SLIDE 11

2015 something more happened...

SLIDE 12

We want autonomous teams to deliver amazing products efficiently at scale.

SLIDE 13

Radical Agility

SLIDE 14

SLIDE 15

Tech Constitution

SLIDE 16

SLIDE 17

Rules of Play

https://github.com/zalando/zalando-rules-of-play

SLIDE 18

Which architecture style is fostered by Radical Agility?

SLIDE 19

Architecture Principles

SLIDE 20

Architecture Principles

https://github.com/zalando/zalando-rules-of-play#architecture

We prefer loosely coupled services.

SLIDE 21

Architecture Principles in detail

Microservice with RESTful APIs Favor message-driven Everything fails Operational Excellence Loosely coupled systems Asynchronous communication Resilient systems Automate everything

SLIDE 22

How do we operate

ur services?

SLIDE 23

AWS Setup

SLIDE 24

AWS Setup

Each team has its own account You build it, you run it Deployment via our STUPS tooling

Team Team Team AWS Account AWS Account AWS Account T h e Internet

SLIDE 25

STUPS.io

SLIDE 26

STUPS.io

SLIDE 27

How do we test our services?

SLIDE 28

Testing

SLIDE 29

Testing

Of course, automated testing - a lot Trade-off: Time to prod <> test coverage (with real systems) Testing flows becomes harder with microservices

SLIDE 30

Our Testing Pyramid - where to run what

SLIDE 31

Consumer-driven Contracts

Better collaboration between teams Emphasize importance of APIs Lowers inter-team alignment efforts

SLIDE 32

How do teams collaborate?

SLIDE 33

Collaboration between teams

At best, not necessary to deliver Through APIs Through Code - shared code

SLIDE 34

Open Source Culture

SLIDE 35

Open Source Culture

https://github.com/zalando/zalando-howto-open-source

Open Source Evangelist, Lauri Apple Open Source Guild Management supports Open Source

SLIDE 36

Example for Open Source @ Zalando

https://github.com/integrations/zappr

Zappr Approvals for pull requests Started in our Innovation Labs Now an official Github plugin

SLIDE 37

Open Source First

SLIDE 38

Shared code between teams has to be open source.

SLIDE 39

Inner Source

SLIDE 40

And how does architecture work takes place?

SLIDE 41

T h e Architect

SLIDE 42

T h e Architect

SLIDE 43

Service architecture is designed by delivery teams.

SLIDE 44

Global architecture is owned by the Architecture team.

SLIDE 45

Architecture Team

SLIDE 46

Architecture Team

Overarching team to support delivery teams

4 in Berlin, 1 in Dublin Focus on new platform and APIs Tech decisions with company-wide impact

SLIDE 47

We support teams in building most appropriate tech solutions.

SLIDE 48

Radical Agility vs Arc Team?

We respect self-autonomy of teams. We support teams as technical consultants. We can provide outside perspective + broader technical

verview.

We let teams make their own architecture decisions.

SLIDE 49

There was team collaboration through APIs...

SLIDE 50

API Guild

SLIDE 51

API Guild

Group of Architect and Engineers Develops API Guidelines Drives API Reviews

SLIDE 52

API First

SLIDE 53

API Reviews

Feedback Culture

Foster review culture Get feedback as soon as possible API Guild is public review partner

SLIDE 54

API Guidelines

SLIDE 55

API Guidelines

https://github.com/zalando/restful-api-guidelines

REST Maturity Level 2 Backward compatibility over versioning Common Naming Rules and Data Objects

SLIDE 56

API Guidelines

SLIDE 57

Our future system will consist of thousands of microservices.

SLIDE 58

How do teams find available APIs?

SLIDE 59

API Discovery

SLIDE 60

API Discovery

A system to crawl and curate all deployed APIs.

https://github.com/zalando-stups/twintip-storage https://github.com/zalando-stups/twintip-crawler https://github.com/zalando-stups/swagger-ui Twintip Crawler Twintip Storage Swagger UI APIs

SLIDE 61

API Discovery

SLIDE 62

How do teams choose tech stacks?

SLIDE 63

Technologists Guild

SLIDE 64

Technologists Guild

Knowledge sharing and discussion Owns and curates Tech Radar Owns internal Tech Compendium

SLIDE 65

Tech Radar

SLIDE 66

Tech Radar

We try to give delivery teams guidance in choosing technologies. Tech Radar is created by involved engineers in the technologists guild. Each team is encouraged to contribute experience reports.

https://zalando.github.io/tech-radar

SLIDE 67

SLIDE 68

Scaling Architecture @ Zalando

Zalando in general Autonomous delivery teams Overarching architecture team Rules of Play Architecture Principles Open Source Culture Architecture specific API Guild + Guidelines API Reviews API Discovery Technologists Guild Tech Radar

SLIDE 69

Thanks. Questions?

Twitter: @fmueller_bln