mirror of
https://github.com/zitadel/zitadel.git
synced 2025-04-23 16:21:32 +00:00
68827dfdcd
* Architecture Scenarios B2B B2C * b2b b2c * cleanup concepts * homepage links, b2c docs * b2c, new homepage, custom components * more content * fix rxjs * temp remove architecture scenarios * temp remove architecture scenarios * Update docs/src/pages/index.js Co-authored-by: Florian Forster <florian@caos.ch> * update docusaurus & review scenarios * refactor user login guide (#2921) * Update docs/docs/guides/architecture-scenarios/b2b.mdx Co-authored-by: Fabi <38692350+fgerschwiler@users.noreply.github.com> * Update docs/docs/guides/architecture-scenarios/b2b.mdx Co-authored-by: Fabi <38692350+fgerschwiler@users.noreply.github.com> * Update docs/docs/guides/architecture-scenarios/b2b.mdx Co-authored-by: Fabi <38692350+fgerschwiler@users.noreply.github.com> * Update docs/docs/guides/architecture-scenarios/b2b.mdx Co-authored-by: Fabi <38692350+fgerschwiler@users.noreply.github.com> * Update docs/docs/guides/architecture-scenarios/b2c.mdx Co-authored-by: Fabi <38692350+fgerschwiler@users.noreply.github.com> * Update docs/docs/guides/architecture-scenarios/b2c.mdx Co-authored-by: Fabi <38692350+fgerschwiler@users.noreply.github.com> * Update docs/docs/guides/architecture-scenarios/b2b.mdx Co-authored-by: mffap <mpa@caos.ch> * Update docs/docs/guides/architecture-scenarios/b2b.mdx Co-authored-by: mffap <mpa@caos.ch> * Update docs/docs/guides/architecture-scenarios/b2b.mdx Co-authored-by: mffap <mpa@caos.ch> * Update docs/docs/guides/architecture-scenarios/b2c.mdx Co-authored-by: mffap <mpa@caos.ch> * Update docs/docs/guides/architecture-scenarios/b2c.mdx Co-authored-by: mffap <mpa@caos.ch> * Update docs/docs/guides/architecture-scenarios/b2c.mdx Co-authored-by: Fabi <38692350+fgerschwiler@users.noreply.github.com> * user-login splitup * files * organize files * cleanup authmethods * solution scenarios * add link to authz * Update docs/docs/guides/authentication/authmethods/implicit.mdx Co-authored-by: Livio Amstutz <livio.a@gmail.com> * Update docs/docs/guides/authentication/authmethods/implicit.mdx Co-authored-by: Livio Amstutz <livio.a@gmail.com> * fix broken links * Update docs/docs/guides/solution-scenarios/b2c.mdx Co-authored-by: Florian Forster <florian@caos.ch> * c for consumer Co-authored-by: Florian Forster <florian@caos.ch> Co-authored-by: Fabi <38692350+fgerschwiler@users.noreply.github.com> Co-authored-by: mffap <mpa@caos.ch> Co-authored-by: Livio Amstutz <livio.a@gmail.com>
24 lines
854 B
Markdown
24 lines
854 B
Markdown
---
|
|
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 so solve complex problems outside of 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
|