Many enterprise frameworks suffer from a severe dichotomy in onboarding design: they either offer detached docker run commands that leave developers running a container without understanding the underlying runtime, or bury engineers in pages of abstract theory before writing a line of code.
BitzOrcas.Modern bridges this divide through an “architectural mental model first, progressive implementation” approach. This chapter equips software architects and developers with end-to-end command over the .NET 10 modular monolith: from foundational boundary governance and the 10-tier application pipeline to executing your first multi-tenant vertical slice.
Engineering Onboarding Roadmap
From cloning the repository to verifying multi-tenant isolation, the standard developer journey follows five distinct milestones:
Chapter Structure & Navigation
To ensure architectural constraints are consistently observed in team development, follow this structured reading path:
-
Understanding BitzOrcas.Modern
Understand why we chose a modular monolith and vertical slice architecture, examine the end-to-end request sequence across the 10-tier pipeline, and learn the five physical rules of cross-module collaboration. -
Development Environment & Prerequisites
Validate .NET 10 SDK, Node.js 22, Docker, and IDE tooling to ensure local compilation satisfies Native AOT constraints. -
Code Installation & Local Configuration
Clone the repository, bring up digest-pinned container infrastructure (SQL Server 2022, Redis 7, RabbitMQ) via Docker Compose, and run--init-schemafor out-of-the-box database seeding. -
5-Minute Quick Start
Launch the Minimal API host, retrieve RSA-OAEP public encryption keys, authenticate, and dispatch your first pipeline-governed command. -
Pre-Seeded Demo Accounts and the Password Injection Contract
Master the production “Fail-Closed Password Injection Contract”, inspect super admin and tenant demo account lifecycles, and verify anti-probing multi-tenant isolation (404 instead of 403). -
Troubleshooting Guide
Remediate common onboarding issues including port conflicts, developer HTTPS certificate trust, and Roslyn source generator cache anomalies.
Chapter Index
- 01/06
Understanding BitzOrcas.Modern: Design Philosophy, Architecture Topology, and Execution Pipeline
A deep dive into the BitzOrcas.Modern enterprise architecture: starting from the monolith-microservices trade-off, mastering vertical slices, the 10-tier application pipeline, dual ORM compile-time generation, and cross-module contract boundaries.
- 02/06
Development Environment & Prerequisites: Cross-Platform Toolchain Setup and Validation
Standardized cross-platform development environment setup: .NET 10 SDK, C# 14 and Native AOT toolchains, Node.js 22 LTS, Corepack (Yarn 4.17.0), Docker container engine, and IDE productivity suites.
- 03/06
Code Installation & Local Configuration: Container Infrastructure and Database Seeding
Master BitzOrcas.Modern local development onboarding: from spinning up digest-pinned Docker Compose infrastructure to zero-trust environment variable injection and idempotent --init-schema database provisioning.
- 04/06
5-Minute Quick Start: Aspire Orchestration, Data Persistence, and the First Authentication Request
Master BitzOrcas.Modern onboarding: spin up complete microservice topologies with .NET Aspire AppHost, configure volume persistence and controlled resets, and authenticate via RSA-OAEP encrypted endpoints.
- 05/06
Pre-Seeded Demo Accounts and the Password Injection Contract: Zero-Trust Seeding and Multi-Tenant Isolation
A deep dive into the BitzOrcas.Modern seeded account catalog: the Fail-Closed environment variable password injection contract, RSA-OAEP anti-replay transport encryption, and anti-probing 404 multi-tenant isolation.
- 06/06
Troubleshooting Guide: Environment, Ports, Compilation, and Runtime Diagnostics
Resolving common BitzOrcas.Modern onboarding failures: verified port matrices (6881, 6880, 6800, 1433), SQL Server connectivity, Roslyn source generator cache resets, and HTTPS developer certificate trust.