A spec-driven, strongly opinionated framework for building composable applications in Rust.
Zino is a spec-driven, strongly opinionated framework for building composable applications in Rust. It provides high-level abstractions and out-of-the-box features to accelerate development, with an emphasis on simplicity, extensibility, and productivity. The framework adopts an API-first approach and integrates seamlessly with popular Rust web ecosystems.
Rust developers building scalable web applications, APIs, or desktop applications who value a structured, opinionated framework with built-in productivity features.
Developers choose Zino for its comprehensive feature set, seamless integrations with frameworks like Actix-web and Axum, and its spec-driven approach that enforces best practices while maintaining flexibility and performance.
Spec-driven framework for composable applications in Rust.
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.
Zino provides out-of-the-box features that allow setting up a server with minimal code, as shown in the README where a simple `Cluster::boot().run()` boots an application.
It fully integrates with popular Rust web frameworks like Actix-web, Axum, and Dioxus, enabling developers to use Zino's features within their preferred ecosystem without reinventing the wheel.
The framework includes native support for tracing, metrics, and logging, eliminating the need for additional setup and libraries for monitoring and debugging.
Zino offers a cohesive ORM based on sqlx for multiple databases and unified access to storage services and data sources, simplifying data management across the application.
As a strongly opinionated framework, Zino enforces its own conventions and abstractions, which can limit flexibility and force developers to adapt to its way of doing things, even for simple tasks.
With a current version of 0.43, Zino is still in active development, meaning breaking changes are likely between releases and long-term stability isn't guaranteed.
The framework is split into numerous crates (e.g., zino-core, zino-auth), leading to a steep learning curve, dependency management challenges, and fragmented documentation.