@SmaineDev

credit @yOyO38

afup

🐣Engineering Manager🐥

🚀 www.smaine.me

     @SmaineDev

🖊  smaine-milianni.medium

      ismail1432

     smainemilianni

🍿 github.com/ismail1432/conferences

Smaïne Milianni

@SmaineDev

JOIN US 🫵

https://yousign.teamtailor.com/jobs

BLUE - GREEN 

DEPLOYMENT

@SmaineDev

Production Version

Release Version

Version N+1

Version N

@SmaineDev

Production Version

Version N

Release Version

Version N+1

@SmaineDev

🗑️

Realease Version

Version N+1

Production Version

Version N

@SmaineDev

🗑️

What is ZDD* ?

ZDD*: Zero downtime deployment but you already know this 😄

Why and what is ZDD ?

✅ Deploy a new release without Downtime

Why and what is ZDD ?

✅ Deploy a new release without Downtime

🚀 Release at any time (even on Friday 🤪)

Why and what is ZDD ?

✅ Deploy a new release without Downtime

🚀 Release at any time (even on Friday 🤪)

😍 Release is transparent for the users

Why and what is ZDD ?

✅ Deploy a new release without Downtime

🚀 Release at any time (even on Friday 🤪)

😍 Release is transparent for the users

🎉 No more waking up at dawn 🐓 or at night 🌙

Why and what is ZDD ?

✅ Deploy a new release without Downtime

🚀 Release at any time (even on Friday 🤪)

😍 Release is transparent for the users

🎉 No more waking up at dawn 🐓 or at night 🌙

⏮️ Make the rollback easier

@SmaineDev

ZDD Golden Rules 📖

1️⃣ The changes should be backward compatible!

 

2️⃣ The changes should be done per release.

@SmaineDev

ZDD Golden Rules 📖

🔀 Backward compatible

🐾 Done per release

@SmaineDev

Backward Compatibility

Version N + 1

Version N

WWW

📆 Change per release

Version N

release tag 7.10.24

Version N + 1

release tag 8.10.24

Version N + 2

release tag 9.10.24

@SmaineDev

No panic, it's just a release

@SmaineDev

Start Deployment ▶️

Deploy ▶️

Version N

@SmaineDev

Deploy ⏳

Version N

Deployment in progress ⏳

Deploy ✅

Version N

Version N+1

Deployment done without downtime 🎉

@SmaineDev

Deploy Fail 😱

Version N

Version N+1

👌App is still up, event the deploy failed

Version N

@SmaineDev

Deploy ✅

Version N

Version N+1

🔙 Rollback easy

Version N+1

@SmaineDev

🔙 Rollback easy

Principal Engineer

@Back Market

@SmaineDev

ZDD in practice 🥋

@SmaineDev

ZDD in practice 🥋

🗃️ Database

✉️ Message brokers

☁️ API

@SmaineDev

Database

Add a `Not Null`column

Version N

Version N+1

Version N

Version N+1

DEPLOYMENT 🚀

Code version N is alive with

Database schema version N+1

@SmaineDev

Release 1️⃣

Add the column nullable

The code should write in the column

Release 2️⃣

Update existing rows with a value and add the NOT NULL constraint

Release 1️⃣

  • Add the column and make it nullable
  • Codebase write in the column ✍🏿

Release 2️⃣

  • Update null rows with default value
  • Add the not null constraints 🔐

💡 Prepare all pull request to not forget

@SmaineDev

  • DELETE a column
  • UPDATE a column type
  • RENAME a column
  • ADD a NOT NULL constraint
  • ...

Database

TOOLING ⚒️

👉🏽 https://github.com/ismail1432/safe-migrations-bundle

TOOLING ⚒️

👉🏽 https://github.com/Yousign/safe-migrations

Make your migrations safer:

  • by preventing lock
  • using a retry strategy

 

$ bin/symfony console d:m:m

[notice] Migrating up to DoctrineMigrations\Version20231224200000
09:30:38 WARNING   [app] (1/3) Lock timeout reached: retrying in 10 seconds...
["sql" => "ALTER TABLE test_retry ADD COLUMN name text DEFAULT NULL"]
09:30:51 WARNING   [app] (2/3) Lock timeout reached: retrying in 10 seconds... ["sql" => "ALTER TABLE test_retry ADD COLUMN name text DEFAULT NULL"]
09:30:51 WARNING   [app] (3/3) Lock timeout reached: retrying in 10 seconds... ["sql" => "ALTER TABLE test_retry ADD COLUMN name text DEFAULT NULL"]


[error] Migration DoctrineMigrations\Version20231224200000 failed during Execution. 
Error: "An exception occurred while executing a query: SQLSTATE[55P03]: Lock not available: 7 
ERROR:  canceling statement due to lock timeout" 
09:31:17 CRITICAL  [console] Error thrown while running command "'d:m:m'".

@SmaineDev

ASSERT ZDD COMPLIANCE

Manual test 🖱️

Run SQL migration of the NEXT RELEASE on the PRODUCTION version

@SmaineDev

ASSERT ZDD COMPLIANCE

2️⃣ Checkout on the `production` branch & run tests

💡Add a specific job in your CI

1️⃣ Load the DB schema in the branch you want to merge

Version N

Version N+1

🧠 Add an environment var to allow failure when needed

MESSAGE BROKERS

@SmaineDev

Serialization

Deserialization

Publisher

Consumer

MESSAGE BROKERS

Version N

@SmaineDev

Publisher

Version N

🛑 Consumers are stopped during the deployment

🚀 Deploy Version N+1

MESSAGE BROKERS

Serialization

Deserialization

Publisher

Consumer

Version N

Version N+1

Serialization

Deserialization

Publisher

Consumer

Version N

Version N+1

Publisher

Consumer

Version N

Version N+1

  • Set a default value
  • write in the property

Publisher

Consumer

Version N+1

Release 1️⃣

Version N+2

Release 2️⃣

  • Set a default value
  • Write in the property
  • Remove default value

MESSAGE BROKERS

Remove a property

Rename the class

Update property type

...

ASSERT ZDD COMPLIANCE

Manual test 🖱️

Publish messages with PRODUCTION code version and consume them with the NEXT RELEASE version

ASSERT ZDD COMPLIANCE

2️⃣ Consume them with the version of the branch you want to merge

💡Add a specific job in your CI

1️⃣ Publish messages with the production version

💡Add a specific job in your CI

👉🏽 https://github.com/Yousign/zdd-message-bundle

🖊️ Helpers to generate message(s)

🗃️ Validate messages can be unserialized

TOOLING ⚒️

FRONT

BACKEND

💔

FRONT

BACKEND

Version N

Version N+1

💥

  • Make a property required
  • Remove a property
  • Update or Remove the path
  • ...

BACKEND

Add a new required property

Make the property required

FRONTEND

Write in the property

BACKEND

Make the property optional

Release 1️⃣

Release 2️⃣

FRONTEND

😴

BACKEND

Remove a property

Remove the property

FRONTEND

Stop writing in the property

BACKEND

Make the property optional

Release 1️⃣

Release 2️⃣

FRONTEND

😴

BACKEND

Rename an endpoint

Remove the old endpoint

FRONTEND

BACKEND

Add the new endpoint

Release 1️⃣

Release 2️⃣

Use the new endpoint

FRONTEND

😴

BACKEND

Version N

Version N+1

  • Write in the new property
  • Don't send the property
  • Use the new path
  • ...

🤝

  • Add the property optional
  • Remove usage of property
  • Keep the old path
  • ...

FRONT

FRONT

BACKEND

TOOLING ⚒️

👉🏽 https://github.com/thephpleague/openapi-psr7-validator

1️⃣ Define API contract (`yaml` or `json`)

2️⃣ Generate Front class from the file

3️⃣ Assert that your API respect the OAS

 💡 OpenAPI Specification

https://swagger.io/specification/

ZDD LIMITATIONS 🛑

📅 Make sense if your release frequently

ZDD LIMITATIONS 🛑

📅 Make sense if your release frequently

⏹ Critical changes still need maintenance

ZDD LIMITATIONS 🛑

📅 Make sense if your release frequently

⏹ Critical changes still need maintenance

🛹 System unstable until the last step

ZDD LIMITATIONS 🛑

📅 Make sense if your release frequently

⏹ Critical changes still need maintenance

🛹 System unstable until the last step

🧠 Most changes require reflection and discipline

ZDD LIMITATIONS 🛑

Implement ZDD in your team 🫵🏿

Implement ZDD in your team 🫵🏿

🏉 Educate your team (workshops, code review...)

Implement ZDD in your team 🫵🏿

🏉 Educate your team (workshops, code review...)

📝 Documentation (reference each case)

Implement ZDD in your team 🫵🏿

🏉 Educate your team (workshops, code review...)

📝 Documentation (reference each case)

🧪 Learn from your failures (postmortems, feedback...)

Implement ZDD in your team 🫵🏿

🏉 Educate your team (workshops, code review...)

📝 Documentation (reference each case)

🧪 Learn from your failures (postmortems, feedback...)

✅ Tests

Implement ZDD in your team 🫵🏿

🏉 Educate your team (workshops, code review...)

📝 Documentation (reference each case)

🧪 Learn from your failures (postmortems, feedback...)

✅ Tests

🦸‍♂️ Assign a ZDD hero

Feedbacks👇

QUESTION