mirror of
https://github.com/andwati/zitadel.git
synced 2026-10-18 05:52:51 +00:00
Wim Van LaerandGitHub
9b064d8b74
# Which Problems Are Solved - Typos - Punctuation - Markdown table formatting - ... (A bunch of issues my editor gave) # How the Problems Are Solved # Additional Changes # Additional Context
24 lines
851 B
Plaintext
24 lines
851 B
Plaintext
---
|
|
title: Principles
|
|
---
|
|
|
|
## ZITADEL engineering and design principles
|
|
|
|
- Be transparent about your decisions
|
|
- Embrace stateless application design
|
|
- System of records is the event store
|
|
- Everything else needs to be able to be regenerated
|
|
- Try not to solve complex problems outside the IAM Domain
|
|
- Use a scalable storage for the event store and read models
|
|
- Try to be idempotent whenever possible
|
|
- Reduce necessity of external systems or dependencies as much as possible
|
|
- Embrace automation
|
|
- Design API first
|
|
- Optimize all components for day-two operations
|
|
- Use only open source projects with permissive licenses
|
|
- Don't roll your own crypto algorithm
|
|
- Embrace (industry) standard as much as possible
|
|
- Make use of platform features
|
|
- Be able to run with a CDN and WAF
|
|
- Releases utilized semantic versioning and release whenever feasible
|