Host-base (service envelope)
The host-base (service envelope) provides a standardized foundation for all services, ensuring core functionality like logging, serialization, health checks, and authentication. It follows a two-layer structure - the Platform Host-Base delivers shared platform-wide features, while the Project-Specific Host-Base (Extended) extends it to include project-specific customizations and adjustments. This approach ensures consistency, flexibility, and maintainability across services.
Service envelope
Each service uses host-base package to share (inherit) base project setup, configuration and behavior. This package (envelope) can be upgraded anytime.
Example Use Case
- A team needs to create a new microservice for processing customer orders.
- The service template provides a ready-to-use skeleton with predefined configurations and patterns, accelerating initial setup.
- The host-base ensures that the service adheres to platform standards, such as unified logging, health checks, and security practices.
- Later, when a new logging format is introduced, the host-base package is upgraded across all services without modifying individual service code.
Benefits
- Accelerated Development: Reduces boilerplate code and setup time for new services.
- Consistency: Ensures all services follow a unified structure and platform standards.
- Maintainability: Allows incremental upgrades and improvements to shared components.
- Scalability: Simplifies onboarding for new developers and supports rapid service growth.
Repositories
platform host-base
https://dev.azure.com/hci-iap/eit-white-label/_git/dotnet-ca-host-base?path=/src/Eit.Ca.HostBase
project host-base
https://dev.azure.com/hci-iap/eit-white-label/_git/dotnet-ca-host-base?path=/src/Eit.Ca.HostBase.Extended
There are example usages within those repositories ready for demo.