#di #dependency-injection #ioc #injection #spring


Dependency injection framework based on automatic component discovery and runtime autowiring

6 releases (1 stable)

1.0.0 Apr 26, 2023
0.3.2 Apr 20, 2023
0.2.1 Apr 7, 2023

#246 in Asynchronous

Download history 18/week @ 2023-06-04 6/week @ 2023-06-11 36/week @ 2023-06-18 15/week @ 2023-06-25 25/week @ 2023-07-02 64/week @ 2023-07-09 41/week @ 2023-07-16 20/week @ 2023-07-23 33/week @ 2023-07-30 28/week @ 2023-08-06 26/week @ 2023-08-13 7/week @ 2023-08-20 12/week @ 2023-08-27 15/week @ 2023-09-03 23/week @ 2023-09-10 101/week @ 2023-09-17

151 downloads per month
Used in 3 crates

MIT license

2.5K SLoC

Springtime Dependency Injection

crates.io version build status Maintenance

A dependency injection crate inspired by the Spring Framework in Java.

The philosophy of Springtime is to provide the means of easy dependency injection without unnecessary manual configuration, e.g. without the need to explicitly create dependencies and storing them in containers. The core concept is the Component - something that can be created, injected, and managed by the framework. As much work as possible is placed on compile-time metadata creation and automatic component discovery, thus allowing users to focus on the usage of components, rather than their creation and management. With an accent placed on attributes, dependency configuration becomes declarative (what I want to accomplish) leaving the gritty details the framework itself (how to accomplish what was requested).


  • Concrete and trait object injection
  • Automatic and manual registration support
  • Component filtering
  • Conditional component registration
  • Component priorities
  • Custom constructor functions
  • Per-field configurable initialization
  • Customizable instance scopes
  • Async + sync support (runtime agnostic)

Basic usage

Springtime is highly configurable, but the most basic usage example is quite simple and consists of using a few attributes to fully configure the dependency chain. For tutorial, advanced features, and patterns, please look at the examples, which form a step-by-step guide.

use springtime_di::factory::ComponentFactoryBuilder;
use springtime_di::instance_provider::{ComponentInstancePtr, TypedComponentInstanceProvider};
use springtime_di::{component_alias, injectable, Component};

// this is a trait we would like to use in our component
trait TestTrait {
    fn foo(&self);

// this is a dependency which implements the above trait and also is an injectable component
struct TestDependency;

// we're telling the framework to provide TestDependency when asked for dyn TestTrait
impl TestTrait for TestDependency {
    fn foo(&self) {
        println!("Hello world!");

// this is another component, but with a dependency
struct TestComponent {
    // the framework will know how to inject dyn TestTrait, when asked for TestComponent (Send + Sync are only needed
    // with the "threadsafe" feature)
    // more details are available in the documentation
    dependency: ComponentInstancePtr<dyn TestTrait + Send + Sync>,
    // alternatively, you can inject the concrete type
    // dependency: ComponentInstancePtr<TestDependency>,

impl TestComponent {
    fn call_foo(&self) {

// note: for the sake of simplicity, errors are unwrapped, rather than gracefully handled
fn main() {
    // components are created by a ComponentFactory
    // for convenience, ComponentFactoryBuilder can be used to create the factory with a reasonable
    // default configuration
    let mut component_factory = ComponentFactoryBuilder::new()
        .expect("error initializing ComponentFactoryBuilder")

    let component = component_factory
        .expect("error creating TestComponent");

    // prints "Hello world!"


~50K SLoC