Base Template — organizational overview¶
ConnectSoft.BaseTemplate is the shared Layer 2 kernel: the common microservice structure, pipelines, and optional infrastructure stacks that all major product templates reuse via a base-template/ Git submodule.
Why use this template¶
- One investment in security defaults, observability, health checks, and CI benefits every product line (Identity, Gateway, SaaS, workers, microservices).
- Faster time-to-market for new services: teams compose the kernel instead of copying and drifting boilerplate.
- Lower operational risk: fixes and hardening land in one place and roll forward through submodule updates.
- Predictable engineering: new hires and partners see the same layering, build logic, and ops hooks across repos.
Typical use cases¶
- Starting any Layer 3 ConnectSoft product (APIs, workers, gateways, identity stacks) that must stay aligned with the template program.
- Replacing ad-hoc “copy-paste” service skeletons with a maintained kernel so audits and upgrades are tractable.
- Platform programs that need a single place to tighten logging, health endpoints, or pipeline behavior once for many repositories.
Capabilities (what the kernel brings)¶
- Consistent solution shape (projects, layering, and cross-cutting concerns) so reviews focus on domain code, not structure debates.
- Shared build and packaging conventions that match how ConnectSoft templates are installed and updated (
dotnet new, CI, optional Docker assets). - Security and observability hooks (health checks, telemetry-friendly defaults, patterns for configuration) suited to regulated and multi-team environments.
- Optional stacks (where enabled) for infrastructure and operational patterns without forcing every product to adopt the same footprint on day one.
What leaders should expect¶
- Kernel vs product: Domain features and customer-specific logic live in Layer 3 repos. The kernel stays domain-agnostic.
- Release coupling: Product releases may need a submodule bump when the kernel ships important fixes—engineering owns that coordination.
Technical documentation (single hub)¶
Scaffolding, solution layout, architecture, parameters, configuration, authentication, resilience, testing, development guidance, detailed use cases, and runbooks are maintained only in ConnectSoft.Documentation under this template.