Change-Id: I340486d90a1fb74e26b31f1f330f61ee2b570c43 Reviewed-on: https://cl.snix.dev/c/snix/+/30139 Autosubmit: Paul Meyer <katexochen0@gmail.com> Reviewed-by: Florian Klink <flokli@flokli.de> Tested-by: besadii
821 B
821 B
| title | slug | description | summary | date | lastmod | draft | weight | toc |
|---|---|---|---|---|---|---|---|---|
| Architecture | architecture | 2025-03-14T14:14:35+01:00 | 2025-03-14T14:14:35+01:00 | false | 31 | true |
Snix is more decoupled than the existing, monolithic Nix implementation.
In practice, we expect to gain several benefits from this, such as:
- Ability to use different builders
- Ability to use different store implementations
- No monopolisation of the implementation, allowing users to replace components that they are unhappy with (up to and including the language evaluator)
- Less hidden intra-dependencies between tools due to explicit RPC/IPC boundaries
In addition to many individual backend implementations, Builders and Store backends also provide a gRPC server and clients, allowing to plug in your own implementation.