microkernel-pattern-guide
/microkernel-pattern-guide
Pomaga projektować rozszerzalne systemy w architekturze mikrojądra: minimalny rdzeń i wymienne wtyczki wybierane przez rejestr, punkty rozszerzeń, negocjacja możliwości, moment wiązania i wstrzykiwanie zależności.
- Autor
- xonovex ↗
- Repozytorium
- platform ↗
- Licencja
- MIT
- Ostatnia zmiana repozytorium
- 08.10.2026
Ocena i bezpieczeństwo
- Pliki w paczce
- 10
- Skrypty
- 0
- Komentarze HTML
- 0
- Adresy URL w SKILL.md
- 0
Brak sygnałów. Repozytorium zmienione 08.10.2026, bez odwołań do wycofanych modeli i API.
MIT, otwarta: można używać i zmieniać, z zachowaniem informacji o autorze.
Co robi i kiedy
Pomaga projektować rozszerzalne systemy w architekturze mikrojądra: minimalny rdzeń i wymienne wtyczki wybierane przez rejestr, punkty rozszerzeń, negocjacja możliwości, moment wiązania i wstrzykiwanie zależności.
Wyzwalacze z opisu
Oryginalny opis (EN)
Use when building an extensible system: a minimal core plus interchangeable plug-ins selected through a registry. The microkernel / plug-in architecture. Triggers on plugin/extension-point/registry design, adding a backend or driver without editing the core, open/closed extension, capability negotiation and fail-closed / secure-by-default gating, binding time (compile vs load vs run-time), dependency-injection vs service-locator wiring, lazy activation, or versioning a plug-in contract, even when the user doesn't say 'microkernel' and only says 'plugin architecture'.
Jak działa
- Essentials
- Gotchas
- Example
- Progressive Disclosure
Podgląd SKILL.md
---
name: microkernel-pattern-guide
description: "Use when building an extensible system: a minimal core plus interchangeable plug-ins selected through a registry. The microkernel / plug-in architecture. Triggers on plugin/extension-point/registry design, adding a backend or driver without editing the core, open/closed extension, capability negotiation and fail-closed / secure-by-default gating, binding time (compile vs load vs run-time), dependency-injection vs service-locator wiring, lazy activation, or versioning a plug-in contract, even when the user doesn't say 'microkernel' and only says 'plugin architecture'."
---
# Microkernel (Plug-in) Architecture
A minimal core plus independent plug-ins, selected through a registry: extend the system by adding a plug-in, never by editing the core.
## Essentials
- **Core + plug-ins + registry** - the minimal core holds the least; features are registered plug-ins, see [references/core-plugins-registry.md](references/core-plugins-registry.md)
- **Open/closed** - add a plug-in and register it once; never edit a central switch, see [references/core-plugins-registry.md](references/core-plugins-registry.md)
- **Capabilities, fail-closed** - plug-ins self-declare guarantees; the core gates generically and securely-by-default, see [references/capabilities-fail-closed.md](references/capabilities-fail-closed.md)
- **Bind as late as cost allows** - compile vs load vs run-time selection picks the mechanism, see [references/binding-time.md](references/binding-time.md)
- **Wire at the root, don't locate** - inject the resolved plug-in; passing the registry into business logic is the service-locator anti-pattern, see [references/wiring.md](references/wiring.md)
- **Built on ports and adapters** - plug-ins are adapters behind contracts; for the port substrate see **hexagonal-pattern-guide**
## Gotchas
- A microkernel is not "just a hexagon". It adds an _open, registered_ plug-in set plus extensibility machinery; ports/adapters is only the substrate (hexagonal-pattern-guide).
- Passing the registry into business logic is the service-locator anti-pattern: hidden dependencies, runtime not-found errors, untestable; resolve at the root and inject the plug-in.
- A churning plug-in contract forces edits across every plug-in: the open/closed violation wearing an interface; keep the contract narrow and versioned.
- The capability gate must name no concrete plug-in: fail-closed on a self-declared guarantee, or a new plug-in can violate an invariant silently.
- The OS microkernel and this architecture pattern share a name, not a definition: keep the two senses separate, see [references/metapatterns-lens.md](references/metapatterns-lens.md).
## Example
```go
// composition root: the only importer of concrete plug-ins
reg := Registry{Backends: map[string]Backend{
"s3": s3.New(), "gcs": gcs.New(), // adding "azure" = one leaf + one line
}}
b, ok := reg.Backends[kind] // open/closed: no central switch to edit
if !ok { return ErrUnknownBackend }
if !b.Guarantees().Has(Durable) { return ErrPolicy } // fail-closed, names no plug-in
```
## Progressive Disclosure
- Read [references/core-plugins-registry.md](references/core-plugins-registry.md) - Load when designing the core, plug-in contract, and registry (open/closed)
- Read [references/capabilities-fail-closed.md](references/capabilities-fail-closed.md) - Load when gating plug-ins by self-declared capabilities, secure-by-default
- Read [references/binding-time.md](references/binding-time.md) - Load when deciding when a plug-in is selected (compile/load/run-time)
- Read [references/wiring.md](references/wiring.md) - Load when wiring plug-ins (dependency injection vs service locator, lazy activation, contract versioning)
- Read [references/metapatterns-lens.md](references/metapatterns-lens.md) - Load when relating microkernel to hexagonal/middleware/mesh (one non-canonical synthesis, with caveats)
Pliki w paczce (10)
- SKILL.md 4 KB
- SOURCES.md 3 KB
- eval-queries.json 5 KB
- evals.json 3 KB
- moon.yml 1 KB
- references/binding-time.md 3 KB
- references/capabilities-fail-closed.md 1 KB
- references/core-plugins-registry.md 3 KB
- references/metapatterns-lens.md 2 KB
- references/wiring.md 2 KB
Wersje
W bazie nie ma innych skilli o nazwie microkernel-pattern-guide.
Migawka bazy z 13.11.2026 · wersja paczki 9db05fa1213d (skrót SHA-256 całej paczki)
Pobrania w ostatnich 30 dniach: 0 · ranking
Zgłoś problem z tym skillem: szkodliwa treść, błędny opis albo prośba autora o usunięcie.
Podobne skille
- 90architecture-paradigm-microkernel
Stosuje architekturę mikrojądra z minimalnym rdzeniem i wtyczkami, dla platform rozszerzanych przez firmy trzecie. - 95backend-plugin-architecture
Projektuje architekturę wtyczek w backendzie: punkty rozszerzeń, interfejsy SPI, ładowanie modułów i podłączanie w locie. - 98create-plugin-modules
Ładuje moduły ABP w czasie działania jako wtyczki przez PlugInSources, buduje moduł klasy bibliotecznej i podpina widoki MVC lub Razor. - 90d365-plugins
Pisze, sprawdza i debuguje wtyczki po stronie serwera w C# dla Dataverse i Dynamics 365, w tym Custom API i kroki rejestracji. - 90os-kernel-architecture
Wspiera decyzje architektoniczne o systemach operacyjnych i jądrach: monolit, mikrojądro, hybryda, unikernel, projekt schedulera, pamięć wirtualna, IPC, granice syscall i ABI oraz obsługa przerwań. - 100csharp-dotnet
Podaje wzorce C# i .NET: Clean Architecture, wstrzykiwanie zależności, async, wzorzec Result, Minimal API, zapytania EF Core i testy jednostkowe.