Laying the groundwork for an internal SDK
During the development of The Corporate Wars, we identified the need to organize our code and build processes to support a modular architecture.
This led us to create internal NuGet packages and a base framework that simplify installation, testing, and deployment across different environments.
The goal is to maintain a clear and sustainable structure that can eventually evolve into an SDK, while remaining private for now.
Key improvements
Cleaner build process
- Clear separation of components.
- Projects designed to minimize unnecessary dependencies.
Consistent deployment
- Automated processes for installation and updates.
- Ready for hybrid environments, both local and cloud-based.
Internal NuGet packages
- Controlled distribution of the system’s modules.
- Coherent versioning to maintain compatibility across components.
Benefits
- Predictable installation – Consistent, easy-to-configure environments.
- Simplified testing – Test doubles without relying on a live network.
- Future-ready – Solid foundation for evolving into a full SDK.
- Clear separation – Domain code stays decoupled from specific implementations.
This approach provides a stable, modular foundation that allows the project to scale and grow in a controlled, maintainable way over time.